linux_dsm_epyc7002/drivers/gpu/drm/amd/display
Rodrigo Siqueira 2f8be0e516 drm/amd/display: Avoid set zero in the requested clk
[Why]
Sometimes CRTCs can be disabled due to display unplugging or temporarily
transition in the userspace; in these circumstances, DCE tries to set
the minimum clock threshold. When we have this situation, the function
bw_calcs is invoked with number_of_displays set to zero, making DCE set
dispclk_khz and sclk_khz to zero. For these reasons, we have seen some
ATOM bios errors that look like:

[drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than
5secs aborting
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck
executing EA8A (len 761, WS 0, PS 0) @ 0xEABA

[How]
This error happens due to an attempt to optimize the bandwidth using the
sclk, and the dispclk clock set to zero. Technically we handle this in
the function dce112_set_clock, but we are not considering the case that
this value is set to zero. This commit fixes this issue by ensuring that
we never set a minimum value below the minimum clock threshold.

Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Acked-by: Eryk Brol <eryk.brol@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
2020-10-05 15:13:36 -04:00
..
amdgpu_dm drm/amd/display: fix return value check for hdcp_work 2020-09-25 16:53:32 -04:00
dc drm/amd/display: Avoid set zero in the requested clk 2020-10-05 15:13:36 -04:00
dmub drm/amd/display: [FW Promotion] Release 0.0.35 2020-09-29 16:11:04 -04:00
include drm/amd/display: get socBB from VBIOS 2020-09-15 17:52:42 -04:00
modules drm/amd/display: Don't log hdcp module warnings in dmesg 2020-09-17 17:56:47 -04:00
Kconfig drm/amd/display: add DCN support for aarch64 2020-08-10 17:26:53 -04:00
Makefile drm/amd/display: Drop CONFIG_DRM_AMD_DC_DMUB guards 2019-11-13 15:29:42 -05:00
TODO