diff options
author | Dave Airlie <airlied@redhat.com> | 2017-08-25 10:52:22 -0700 |
---|---|---|
committer | Dave Airlie <airlied@redhat.com> | 2017-08-29 06:26:32 +1000 |
commit | 5e60a10eaebab93f823295cd7ec3848ba3b6e553 (patch) | |
tree | e6ab7ff3bbb3f4c314f7a3687e34aebfee2a80f2 /include/drm | |
parent | afca4216b8b1085f3a53a27b732d95be257ecffb (diff) | |
download | linux-5e60a10eaebab93f823295cd7ec3848ba3b6e553.tar.gz linux-5e60a10eaebab93f823295cd7ec3848ba3b6e553.tar.bz2 linux-5e60a10eaebab93f823295cd7ec3848ba3b6e553.zip |
drm/syncobj: add sync obj wait interface. (v8)
This interface will allow sync object to be used to back
Vulkan fences. This API is pretty much the vulkan fence waiting
API, and I've ported the code from amdgpu.
v2: accept relative timeout, pass remaining time back
to userspace.
v3: return to absolute timeouts.
v4: absolute zero = poll,
rewrite any/all code to have same operation for arrays
return -EINVAL for 0 fences.
v4.1: fixup fences allocation check, use u64_to_user_ptr
v5: move to sec/nsec, and use timespec64 for calcs.
v6: use -ETIME and drop the out status flag. (-ETIME
is suggested by ickle, I can feel a shed painting)
v7: talked to Daniel/Arnd, use ktime and ns everywhere.
v8: be more careful in the timeout calculations
use uint32_t for counter variables so we don't overflow
graciously handle -ENOINT being returned from dma_fence_wait_timeout
Signed-off-by: Dave Airlie <airlied@redhat.com>
Reviewed-by: Jason Ekstrand <jason@jlekstrand.net>
Acked-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'include/drm')
0 files changed, 0 insertions, 0 deletions