diff options
author | Lyude Paul <[email protected]> | 2019-06-20 19:21:26 -0400 |
---|---|---|
committer | Alex Deucher <[email protected]> | 2019-07-01 09:15:00 -0500 |
commit | 688f3d1ebedffa310b6591bd1b63fa0770d945fe (patch) | |
tree | ad8d5a9664a6c057054e68166efb59492ae9cc40 /scripts/gen_compile_commands.py | |
parent | f78c581e22d4b33359ac3462e8d0504735df01f4 (diff) |
drm/amdgpu: Don't skip display settings in hwmgr_resume()
I'm not entirely sure why this is, but for some reason:
921935dc6404 ("drm/amd/powerplay: enforce display related settings only on needed")
Breaks runtime PM resume on the Radeon PRO WX 3100 (Lexa) in one the
pre-production laptops I have. The issue manifests as the following
messages in dmesg:
[drm] UVD and UVD ENC initialized successfully.
amdgpu 0000:3b:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring vce1 test failed (-110)
[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <vce_v3_0> failed -110
[drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
And happens after about 6-10 runtime PM suspend/resume cycles (sometimes
sooner, if you're lucky!). Unfortunately I can't seem to pin down
precisely which part in psm_adjust_power_state_dynamic that is causing
the issue, but not skipping the display setting setup seems to fix it.
Hopefully if there is a better fix for this, this patch will spark
discussion around it.
Fixes: 921935dc6404 ("drm/amd/powerplay: enforce display related settings only on needed")
Cc: Evan Quan <[email protected]>
Cc: Alex Deucher <[email protected]>
Cc: Huang Rui <[email protected]>
Cc: Rex Zhu <[email protected]>
Cc: Likun Gao <[email protected]>
Cc: <[email protected]> # v5.1+
Signed-off-by: Lyude Paul <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'scripts/gen_compile_commands.py')
0 files changed, 0 insertions, 0 deletions