summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/drm_edid.c
diff options
context:
space:
mode:
authorRob Clark <robdclark@gmail.com>2014-11-26 18:58:04 -0500
committerDaniel Vetter <daniel.vetter@ffwll.ch>2014-11-27 15:39:11 +0100
commite5b5341c28c66a122982d3d8822a4f9a0938f923 (patch)
tree5bc62458e106e8e1acd5ce83864b13506267de8a /drivers/gpu/drm/drm_edid.c
parentabd69c55dd8f1f71b33b8c6165217f4329db8f25 (diff)
downloadblackbird-op-linux-e5b5341c28c66a122982d3d8822a4f9a0938f923.tar.gz
blackbird-op-linux-e5b5341c28c66a122982d3d8822a4f9a0938f923.zip
drm/atomic: clear plane's CRTC and FB when shutting down
Otherwise we'd still end up w/ the plane attached to the CRTC, and seemingly active, but without an FB. Which ends up going *boom* in the drivers. Slightly modified version of Daniel's irc suggestion. Note that the big problem isn't drivers going *boom* here (since we already have the situation of planes being left enabled when the crtc goes down). The real issue is that the core assumes the primary plane always goes down when calling ->set_config with a NULL mode. Ignoring that assumption leads to the legacy state pointers plane->fb/crtc getting out of sync with atomic, and that then leads to the subsequent *boom* all over the place. CC: Daniel Vetter <daniel@ffwll.ch> Signed-off-by: Rob Clark <robdclark@gmail.com> [danvet: Drop my opinion of what's going sidewides here into the commit message as a note.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/drm_edid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud