diff options
author | Rob Clark <robdclark@gmail.com> | 2014-10-30 20:39:04 +0300 |
---|---|---|
committer | Thomas Hellstrom <thellstrom@vmware.com> | 2014-10-31 11:44:35 +0300 |
commit | 21e88620aa21b48d4f62d29275e3e2944a5ea2b5 (patch) | |
tree | 4ea16fa234bc54398da1518c16028189176d4995 /drivers/misc | |
parent | d34d4d8af8d24afe4e16128e4e7f5c5967c89027 (diff) | |
download | linux-21e88620aa21b48d4f62d29275e3e2944a5ea2b5.tar.xz |
drm/vmwgfx: fix lock breakage
After:
commit d059f652e73c35678d28d4cd09ab2cec89696af9
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Fri Jul 25 18:07:40 2014 +0200
drm: Handle legacy per-crtc locking with full acquire ctx
drm_mode_cursor_common() was switched to use drm_modeset_(un)lock_crtc()
which uses full aquire ctx. So dropping/reaquiring the lock via
drm_modeset_(un)lock() directly isn't the right thing to do, as lockdep
kindly points out.
The 'FIXME's about sorting out whether vmwgfx *really* needs to lock-all
for cursor updates still apply.
Signed-off-by: Rob Clark <robdclark@gmail.com>
Reviewed-by: Jakob Bornecrantz <jakob@vmware.com>
Tested-by: Thomas Hellstrom <thellstrom@vmware.com>
Diffstat (limited to 'drivers/misc')
0 files changed, 0 insertions, 0 deletions