omapdrm: use modeset_lock_all
authorDaniel Vetter <daniel.vetter@ffwll.ch>
Sun, 20 Jan 2013 14:50:41 +0000 (15:50 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Sun, 20 Jan 2013 21:16:53 +0000 (22:16 +0100)
commitd5d2636ed7990b93c7216f6a4d323f6b0eee08af
tree497dec3a9bc20613069422e40aa8f8b40e389621
parentbbe4b99ff2443e305598768ae8eac6bc3516b7c9
omapdrm: use modeset_lock_all

I've left the locking in the debugfs code as-is, it's essentially just
used to keep the framebuffer object alive (which won't be necessary
any more later on). We don't need fb refcounting either, since the new
mode_config.fb_lock ensures that the framebuffers can't disappear
(once mode_config.mutex doesn't guarantee this any more later on in
the series).

The fbcon restore needs all modeset locks. The crtc callbacks seem to
only need the crtc locks, but I've quickly discussed things with Rob
Clark and he's fine with just using modeset_lock_all for those, too.
He'll look into converting things over later.

Reviewed-by: Rob Clark <rob@ti.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/staging/omapdrm/omap_crtc.c
drivers/staging/omapdrm/omap_drv.c