summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2021-09-28 14:35:50 -0700
committerHeiko Stuebner <heiko@sntech.de>2021-10-17 23:47:19 +0200
commite584cdc1549932f87a2707b56bc588cfac5d89e0 (patch)
treead044b561b36c318ad6efd49858d153c3b2b3bd1 /tools/perf/scripts/python
parent514db871922f103886ad4d221cf406b4fcc5e74a (diff)
downloadlinux-e584cdc1549932f87a2707b56bc588cfac5d89e0.tar.gz
linux-e584cdc1549932f87a2707b56bc588cfac5d89e0.zip
drm/rockchip: dsi: Reconfigure hardware on resume()
Since commit 43c2de1002d2 ("drm/rockchip: dsi: move all lane config except LCDC mux to bind()"), we perform most HW configuration in the bind() function. This configuration may be lost on suspend/resume, so we need to call it again. That may lead to errors like this after system suspend/resume: dw-mipi-dsi-rockchip ff968000.mipi: failed to write command FIFO panel-kingdisplay-kd097d04 ff960000.mipi.0: failed write init cmds: -110 Tested on Acer Chromebook Tab 10 (RK3399 Gru-Scarlet). Note that early mailing list versions of this driver borrowed Rockchip's downstream/BSP solution, to do HW configuration in mode_set() (which *is* called at the appropriate pre-enable() times), but that was discarded along the way. I've avoided that still, because mode_set() documentation doesn't suggest this kind of purpose as far as I can tell. Fixes: 43c2de1002d2 ("drm/rockchip: dsi: move all lane config except LCDC mux to bind()") Cc: <stable@vger.kernel.org> Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Chen-Yu Tsai <wenst@chromium.org> Tested-by: NĂ­colas F. R. A. Prado <nfraprado@collabora.com> Signed-off-by: Heiko Stuebner <heiko@sntech.de> Link: https://patchwork.freedesktop.org/patch/msgid/20210928143413.v3.2.I4e9d93aadb00b1ffc7d506e3186a25492bf0b732@changeid
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions