summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
diff options
context:
space:
mode:
authorMaarten Lankhorst <maarten.lankhorst@linux.intel.com>2021-10-21 12:35:40 +0200
committerMaarten Lankhorst <maarten.lankhorst@linux.intel.com>2021-11-25 14:33:26 +0100
commit5c2625c4a08cf9b19cd070c1b30c75c9e5317853 (patch)
tree8b80cb957daeee996d867d7914fe2a2baf9c4f40 /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
parent16d69a891970a8f97f0aac4e7ed0ccbf167a936b (diff)
drm/i915: Remove dma_resv_prune
The signaled bit is already used for quick testing if a fence is signaled. On top of that, it's a terrible abuse of dma-fence api, and in the common case where the object is already locked by the caller, the trylock will fail. If it were useful, the core dma-api would have exposed the same functionality. The fact that i915 has a dma_resv_utils.c file should be a warning that the functionality either belongs in core, or is not very useful at all. In this case the latter. Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> [mlankhorst: Improve commit message] Acked-by: Christian König <christian.koenig@amd.com> Link: https://patchwork.freedesktop.org/patch/msgid/20211021103605.735002-3-maarten.lankhorst@linux.intel.com Reviewed-by: Matthew Auld <matthew.auld@intel.com> #irc
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions