drm/msm/dpu: Fix error recovery after failing to enable clocks
authorJordan Crouse <jcrouse@codeaurora.org>
Tue, 7 May 2019 19:18:09 +0000 (13:18 -0600)
committerRob Clark <robdclark@chromium.org>
Tue, 18 Jun 2019 20:52:10 +0000 (13:52 -0700)
commit36415615adf4b55668a99ba4565bdd38733e5bff
treeb1bca5a77cec5f18d83c07c95047b1020277b6ed
parent295b22ae596c1d2dd8a4eb597d576f43acb4da6f
drm/msm/dpu: Fix error recovery after failing to enable clocks

If enabling clocks fails in msm_dss_enable_clk() the code to unwind the
settings starts at 'i' which is the clock that just failed. While this
isn't harmful it does result in a number of warnings from the clock
subsystem while trying to unpreare/disable the very clock that had
just failed to prepare/enable. Skip the current failed clock during
the unwind to to avoid the extra log spew.

Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Rob Clark <robdclark@chromium.org>
drivers/gpu/drm/msm/disp/dpu1/dpu_io_util.c