diff options
| author | Daniel Stone <daniels@collabora.com> | 2017-04-17 13:11:13 +0100 |
|---|---|---|
| committer | Daniel Stone <daniels@collabora.com> | 2017-05-02 19:08:29 +0100 |
| commit | 497ab787e5ab56c630014a20b43bfab16e3b43aa (patch) | |
| tree | 3926e32647f09928fd79b91877a401fe2d120ed1 /common.c | |
| parent | c84b17c5761059f7c8490bf6a4e0a2beec74f9b1 (diff) | |
| download | kmscube-497ab787e5ab56c630014a20b43bfab16e3b43aa.tar.gz | |
atomic: Use CPU-side KMS fence synchronisation
Atomic does not let us have multiple requests in flight at once; if we
don't synchronise with the request completion on the CPU side, we can
get -EBUSY from the atomic commit.
We already have everything required to do this, namely the out-fence
from the last commit. Block on that with a CPU-side wait before we call
atomic commit, to make sure we'll never attempt to queue an atomic
commit before the previous one has completed.
Signed-off-by: Daniel Stone <daniels@collabora.com>
Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
Diffstat (limited to 'common.c')
| -rw-r--r-- | common.c | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -155,6 +155,7 @@ int init_egl(struct egl *egl, const struct gbm *gbm) get_proc_dpy(EGL_KHR_fence_sync, eglCreateSyncKHR); get_proc_dpy(EGL_KHR_fence_sync, eglDestroySyncKHR); get_proc_dpy(EGL_KHR_fence_sync, eglWaitSyncKHR); + get_proc_dpy(EGL_KHR_fence_sync, eglClientWaitSyncKHR); get_proc_dpy(EGL_ANDROID_native_fence_sync, eglDupNativeFenceFDANDROID); printf("Using display %p with EGL version %d.%d\n", |