diff options
| author | Daniel Vetter <[email protected]> | 2015-03-25 18:30:38 +0100 |
|---|---|---|
| committer | Jani Nikula <[email protected]> | 2015-03-26 13:39:04 +0200 |
| commit | 5f407751b0ca9bd876fe8f15ff28153661c6ba0a (patch) | |
| tree | 7fc4ca225d5bd570d2e21a4e0fab5d9851da7fa1 /lib/cpu-notifier-error-inject.c | |
| parent | 3164a803416832d61268b758112e8dfd7e35cdf7 (diff) | |
drm/i915: Fixup legacy plane->crtc link for initial fb config
This is a very similar bug in the load detect code fixed in
commit 9128b040eb774e04bc23777b005ace2b66ab2a85
Author: Daniel Vetter <[email protected]>
Date: Tue Mar 3 17:31:21 2015 +0100
drm/i915: Fix modeset state confusion in the load detect code
But this time around it was the initial fb code that forgot to update
the plane->crtc pointer. Otherwise it's the exact same bug, with the
exact same restrains (any set_config call/ioctl that doesn't disable
the pipe papers over the bug for free, so fairly hard to hit in normal
testing). So if you want the full explanation just go read that one
over there - it's rather long ...
Cc: Matt Roper <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Chris Wilson <[email protected]>
Cc: Josh Boyer <[email protected]>
Cc: Jani Nikula <[email protected]>
Reported-and-tested-by: Josh Boyer <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
[Jani: backported to drm-intel-fixes for v4.0-rc]
Reference: http://mid.gmane.org/CA+5PVA7ChbtJrknqws1qvZcbrg1CW2pQAFkSMURWWgyASRyGXg@mail.gmail.com
Signed-off-by: Jani Nikula <[email protected]>
Diffstat (limited to 'lib/cpu-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions