drm/amd/powerplay: bug fix for memory clock request from display
In some cases, display fixes memory clock frequency to a high value rather than the natural memory clock switching. When we comes back from s3 resume, the request from display is not reset, this causes the bug which makes the memory clock goes into a low value. Then due to the insuffcient memory clock, the screen flicks. Signed-off-by: Kenneth Feng <kenneth.feng@amd.com> Reviewed-by: Jack Xiao <Jack.Xiao@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
This commit is contained in:
parent
f839110157
commit
5441dd0e2c
@ -1354,6 +1354,8 @@ static int smu_resume(void *handle)
|
||||
if (smu->is_apu)
|
||||
smu_set_gfx_cgpg(&adev->smu, true);
|
||||
|
||||
smu->disable_uclk_switch = 0;
|
||||
|
||||
mutex_unlock(&smu->mutex);
|
||||
|
||||
pr_info("SMU is resumed successfully!\n");
|
||||
|
Loading…
Reference in New Issue
Block a user