drm/auth: Drop master_create/destroy hooks
authorDaniel Vetter <daniel.vetter@ffwll.ch>
Mon, 27 Jan 2020 10:02:03 +0000 (11:02 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Wed, 29 Jan 2020 08:14:11 +0000 (09:14 +0100)
commit86a9360be144c9c981c48f8e5b2214179cb53dc5
tree985ef79012cb91d86ed1cb0993f8142c468d2edd
parent3cb6d8e5cf9811a62e27f366fd1c05f90310a8fd
drm/auth: Drop master_create/destroy hooks

vmwgfx stopped using them.

With the drm device model that we've slowly evolved over the past few
years master status essentially controls access to display resources,
and nothing else. Since that's a pure access permission check drivers
should have no need at all to track additional state on a per file
basis.

Aside: For cleanup and restoring kernel-internal clients the grand
plan is to move everyone over to drm_client and
drm_master_internal_acquire/release, like the generic fbdev code
already does. That should get rid of most ->lastclose implementations,
and I think also subsumes any processing vmwgfx does in
master_set/drop.

Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
Cc: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200127100203.1299322-1-daniel.vetter@ffwll.ch
drivers/gpu/drm/drm_auth.c
include/drm/drm_drv.h