aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2013-12-02 04:08:06 -0500
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-12-03 17:14:26 -0500
commit027476642811f8559cbe00ef6cc54db230e48a20 (patch)
tree17e408db9b226d0098cc2c242d95198e54a4a11c /drivers/gpu/drm/i915
parent993fc6ebaf4af6fdfde08cc8649c386e483a5908 (diff)
drm/i915: Take modeset locks around intel_modeset_setup_hw_state()
Some lower level things get angry if we don't have modeset locks during intel_modeset_setup_hw_state(). Actually the resume and lid_notify codepaths alreday hold the locks, but the init codepath doesn't, so fix that. Note: This slipped through since we only disable pipes if the plane/pipe linking doesn't match. Which is only relevant on older gen3 mobile machines, if the BIOS fails to set up our preferred linking. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: stable@vger.kernel.org Tested-and-reported-by: Paul Bolle <pebolle@tiscali.nl> [danvet: Add note now that I could confirm my theory with the log files Paul Bolle provided.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915')
-rw-r--r--drivers/gpu/drm/i915/intel_display.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 080f6fd4e839..114db51996bd 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -11046,7 +11046,9 @@ void intel_modeset_gem_init(struct drm_device *dev)
11046 11046
11047 intel_setup_overlay(dev); 11047 intel_setup_overlay(dev);
11048 11048
11049 drm_modeset_lock_all(dev);
11049 intel_modeset_setup_hw_state(dev, false); 11050 intel_modeset_setup_hw_state(dev, false);
11051 drm_modeset_unlock_all(dev);
11050} 11052}
11051 11053
11052void intel_modeset_cleanup(struct drm_device *dev) 11054void intel_modeset_cleanup(struct drm_device *dev)