drm/msm/a6xx: fix frequency not always being restored on GMU resume
authorJonathan Marek <jonathan@marek.ca>
Thu, 13 Aug 2020 18:54:48 +0000 (14:54 -0400)
committerRob Clark <robdclark@chromium.org>
Sat, 22 Aug 2020 17:56:45 +0000 (10:56 -0700)
commit5e0c22d4a9ddae4e784a3e171b9d3d452b37aeb2
treebba535f466d67c9219daf5d0f2161fa387fd73db
parent6f7cd6e40b94d498049c1a8664c15bf5863ae578
drm/msm/a6xx: fix frequency not always being restored on GMU resume

The patch reorganizing the set_freq function made it so the gmu resume
doesn't always set the frequency, because a6xx_gmu_set_freq() exits early
when the frequency hasn't been changed. Note this always happens when
resuming GMU after recovering from a hang.

Use a simple workaround to prevent this from happening.

Fixes: 1f60d11423db ("drm: msm: a6xx: send opp instead of a frequency")
Signed-off-by: Jonathan Marek <jonathan@marek.ca>
Signed-off-by: Rob Clark <robdclark@chromium.org>
drivers/gpu/drm/msm/adreno/a6xx_gmu.c