summaryrefslogtreecommitdiff
path: root/include/uapi/drm
diff options
context:
space:
mode:
authorLaura Nao <laura.nao@collabora.com>2026-04-21 10:47:01 +0200
committerBoris Brezillon <boris.brezillon@collabora.com>2026-05-29 19:03:10 +0200
commit21fcb222f0d1e1c9f5b04c09e9fb3408e13a0264 (patch)
tree9345185fe803093105e7b6c3244db9c65cd3b9ab /include/uapi/drm
parent351af554edd994898db12217c3be39979e168d35 (diff)
downloadlinux-next-21fcb222f0d1e1c9f5b04c09e9fb3408e13a0264.tar.gz
linux-next-21fcb222f0d1e1c9f5b04c09e9fb3408e13a0264.zip
drm: Remove DRIVER_GEM_GPUVA feature flag
The DRIVER_GEM_GPUVA feature flag is currently only used to control two behaviors within the DRM core: - calling drm_gem_gpuva_init() during GEM object initialization - creating the "gpuvas" debugfs entry drm_gem_gpuva_init() is a plain INIT_LIST_HEAD() and therefore is cheap to run for every GEM object. The DRM_DEBUGFS_GPUVA_INFO macro is only referenced by GPU-VA capable drivers, so clearing the feature bit does not cause any unrelated drivers to get the "gpuvas" debugfs node. The flag doesn't have any relevant purpose (e.g. gating ioctl handlers or MM logic) and doesn't provide any practical benefit. Remove the flag definition and drop it from all drivers that use it, call drm_gem_gpuva_init() unconditionally and clear the driver features bit in DRM_DEBUGFS_GPUVA_INFO. Signed-off-by: Laura Nao <laura.nao@collabora.com> Acked-by: Rob Clark <rob.clark@oss.qualcomm.com> Acked-by: Liviu Dudau <liviu.dudau@arm.com> Acked-by: Thomas Hellström <thomas.hellstrom@linux.intel.com> Link: https://patch.msgid.link/20260421084701.24227-1-laura.nao@collabora.com Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
Diffstat (limited to 'include/uapi/drm')
0 files changed, 0 insertions, 0 deletions