diff options
author | Joshua Aberback <joshua.aberback@amd.com> | 2020-04-29 19:01:14 -0400 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2020-10-05 15:16:30 -0400 |
commit | 3e19095534caec6be8f8c1a7d8fd4879e23637ed (patch) | |
tree | e586f46680328f59140ead02872b3f8d9a75fce8 /drivers/gpu/drm/amd/display/modules/freesync/freesync.c | |
parent | fe984cb3dd325c4c5c7c360e43d93608d4d8870a (diff) | |
download | linux-3e19095534caec6be8f8c1a7d8fd4879e23637ed.tar.gz linux-3e19095534caec6be8f8c1a7d8fd4879e23637ed.tar.bz2 linux-3e19095534caec6be8f8c1a7d8fd4879e23637ed.zip |
drm/amd/display: Force enable pstate on driver unload
[Why]
During driver unload, it is expected that p-state switching is supported.
If it's not supported, PMFW will hang due to a forced p-state switch. Even
if the current timing does not support p-state normally, we still want to
force allow because the worst that can happen is underflow. This will
match Navi10 behaviour.
[How]
- new hubbub func to control the force pstate register
- force allow when releasing display ownership
- registers are inaccessible after due to m_cgs.hwNotAvailable
- explicitly disable force signal during hw_init
- if driver is disabled and re-enabled, register not cleared otherwise
Also, remove DCN3 part of dcn10_init_hw, we will not be going back to it.
Signed-off-by: Joshua Aberback <joshua.aberback@amd.com>
Reviewed-by: Jun Lei <Jun.Lei@amd.com>
Acked-by: Eryk Brol <eryk.brol@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/display/modules/freesync/freesync.c')
0 files changed, 0 insertions, 0 deletions