aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/drm_framebuffer.c
diff options
context:
space:
mode:
authorDaniel Vetter <[email protected]>2018-05-03 14:25:51 +0000
committerDaniel Vetter <[email protected]>2018-07-02 08:20:53 +0000
commit796422f227eef662256dcf74f609abd48cfd1cc9 (patch)
tree8cb0876de40a565ea0d78372005d3319148daf34 /drivers/gpu/drm/drm_framebuffer.c
parentdma-fence: Make ->enable_signaling optional (diff)
downloadkernel-796422f227eef662256dcf74f609abd48cfd1cc9.tar.gz
kernel-796422f227eef662256dcf74f609abd48cfd1cc9.zip
dma-fence: Allow wait_any_timeout for all fences
When this was introduced in commit a519435a96597d8cd96123246fea4ae5a6c90b02 Author: Christian König <[email protected]> Date: Tue Oct 20 16:34:16 2015 +0200 dma-buf/fence: add fence_wait_any_timeout function v2 there was a restriction added that this only works if the dma-fence uses the dma_fence_default_wait hook. Which works for amdgpu, which is the only caller. Well, until you share some buffers with e.g. i915, then you get an -EINVAL. But there's really no reason for this, because all drivers must support callbacks. The special ->wait hook is only as an optimization; if the driver needs to create a worker thread for an active callback, then it can avoid to do that if it knows that there's a process context available already. So ->wait is just an optimization, just using the logic in dma_fence_default_wait() should work for all drivers. Let's remove this restriction. Reviewed-by: Christian König <[email protected]> Signed-off-by: Daniel Vetter <[email protected]> Cc: Sumit Semwal <[email protected]> Cc: Gustavo Padovan <[email protected]> Cc: [email protected] Cc: [email protected] Cc: Christian König <[email protected]> Cc: Alex Deucher <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/drm_framebuffer.c')
0 files changed, 0 insertions, 0 deletions