diff options
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2014-03-21 23:22:35 +0100 |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2014-03-24 07:54:29 +1000 |
| commit | 060c877848b8a0a44d7ba32ff3a53982a6e907f7 (patch) | |
| tree | fad5909f79fe2609d1b2d5bb5557e9d21ced537d /drivers/gpu/drm/gma500 | |
| parent | 3ea8785503a05a92601ffa209ef7d560d271fa33 (diff) | |
| download | blackbird-op-linux-060c877848b8a0a44d7ba32ff3a53982a6e907f7.tar.gz blackbird-op-linux-060c877848b8a0a44d7ba32ff3a53982a6e907f7.zip | |
drm/i915: add locking to fixed panel edid probing
With the recent addition of locking checks in
commit 62ff94a5492175759546f8bc61383189d6b49122
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Thu Jan 23 22:18:47 2014 +0100
drm/crtc-helper: remove LOCKING from kerneldoc
drm_add_edid_modes started to WARN about the mode_config.mutex not
being held in the lvds and dp initialization code.
Now since this is init code locking is fairly redudant if it wouldn't
be for the drm core registering sysfs files a bit early. And the
locking WARNINGs nicely enforce that indeed all access to the mode
lists are properly protected. And a full audit shows that only i915
and gma500 touch the modes lists at init time.
Hence I've opted to wrap up this entire mode detection sequence for
fixed panels with the mode_config mutex for both lvds and edp outputs.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/gma500')
0 files changed, 0 insertions, 0 deletions
