diff options
| author | Stephan Gerhold <[email protected]> | 2019-11-06 17:58:34 +0100 |
|---|---|---|
| committer | Linus Walleij <[email protected]> | 2019-11-09 22:19:09 +0100 |
| commit | 3c5824bdc49046d187d49207730d5074ba59ca20 (patch) | |
| tree | 027ca889dd2a28c95bfe072eef3623aeab027bdb /tools/perf/scripts/python | |
| parent | 1f79c60e1028144ec1f3f120f734f7cb16c1c924 (diff) | |
drm/mcde: dsi: Enable clocks in pre_enable() instead of mode_set()
The DSI initialization sequence incorrectly assumes that the mode_set()
function of the DRM bridge is always called when (re-)enabling the display.
This is not necessarily the case.
Keeping the device idle in the framebuffer console for a while results
in the display being turned off using the disable() function. However,
as soon as any key is pressed only (pre_)enable() are called.
mode_set() is skipped because the mode has not been changed.
In this case, the DSI HS/LP clocks are never turned back on,
preventing the display from working.
Fix this by moving a part of the initialization sequence from
mode_set() to pre_enable(). Keep most of the video mode setup in
mode_set() since most of the registers are only dependent on the mode
that is set for the panel - there is no need to write them again each
time we re-enable the display.
Signed-off-by: Stephan Gerhold <[email protected]>
Tested-by: Linus Walleij <[email protected]>
Reviewed-by: Linus Walleij <[email protected]>
Signed-off-by: Linus Walleij <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions