drm/vmwgfx: Fix F26 Wayland screen update issue
authorSinclair Yeh <syeh@vmware.com>
Tue, 29 Aug 2017 16:55:09 +0000 (18:55 +0200)
committerSinclair Yeh <syeh@vmware.com>
Tue, 29 Aug 2017 21:19:03 +0000 (23:19 +0200)
commit021aba761f2a6c12158afb9993524c300c01fae2
tree2e7145ed2d5055abbf3bdd18db273d49000445d4
parentcc4a41fe5541a73019a864883297bd5043aa6d98
drm/vmwgfx: Fix F26 Wayland screen update issue

vmwgfx currently cannot support non-blocking commit because when
vmw_*_crtc_page_flip is called, drm_atomic_nonblocking_commit()
schedules the update on a thread.  This means vmw_*_crtc_page_flip
cannot rely on the new surface being bound before the subsequent
dirty and flush operations happen.

Cc: <stable@vger.kernel.org> # 4.12.x
Signed-off-by: Sinclair Yeh <syeh@vmware.com>
Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Charmaine Lee <charmainel@vmware.com>
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c