diff options
| author | Daniel Vetter <[email protected]> | 2013-01-24 16:20:34 +0000 |
|---|---|---|
| committer | Rob Clark <[email protected]> | 2013-02-16 23:13:26 +0000 |
| commit | dfe96ddcfa22b44100814b9435770f6ff1309d37 (patch) | |
| tree | 69459fab507e7a937abf3e40e888789e684a2c86 /drivers/gpu/drm/omapdrm/omap_fbdev.c | |
| parent | omapdrm: only take crtc->mutex in crtc callbacks (diff) | |
| download | kernel-dfe96ddcfa22b44100814b9435770f6ff1309d37.tar.gz kernel-dfe96ddcfa22b44100814b9435770f6ff1309d37.zip | |
omapdrm: simplify locking in the fb debugfs file
We don't need to hold onto mode_config.mutex any more to keep the fb
objects around. And locking dev->struct_mutex is also not required,
since omap_gem_describe only reads data anyway. And for a debug
interface it's better to grab fewer locks in case the driver is
deadlocked already ...
The only thing we need is to hold onto mode_config.fb_lock to ensure
the user-created fbs don't disappear. The fbcon fb doesn't need any
protection, since it lives as long as the driver (and so the debugfs
files) itself. And if the teardown/setup isn't following the right
sequence grabbing locks won't prevent a NULL deref on priv->fbdev if
the fb is not yet (or no longer) there.
Signed-off-by: Daniel Vetter <[email protected]>
Signed-off-by: Rob Clark <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/omapdrm/omap_fbdev.c')
0 files changed, 0 insertions, 0 deletions