drm/amd/display: Red screen observed on startup
[Why] We try to to change new_clocks->dppclk_khz to 100000 when new_clocks->dppclk_khz is 0 [How] Don't change new_clocks->dppclk_khz value when new_clocks->dppclk_khz is 0 Signed-off-by: Peikang Zhang <peikang.zhang@amd.com> Reviewed-by: Yongqiang Sun <yongqiang.sun@amd.com> Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
This commit is contained in:
parent
5e90801298
commit
3c08d625d6
|
@ -153,8 +153,9 @@ void rn_update_clocks(struct clk_mgr *clk_mgr_base,
|
|||
}
|
||||
|
||||
// workaround: Limit dppclk to 100Mhz to avoid lower eDP panel switch to plus 4K monitor underflow.
|
||||
// Do not adjust dppclk if dppclk is 0 to avoid unexpected result
|
||||
if (!IS_DIAG_DC(dc->ctx->dce_environment)) {
|
||||
if (new_clocks->dppclk_khz < 100000)
|
||||
if (new_clocks->dppclk_khz < 100000 && new_clocks->dppclk_khz > 0)
|
||||
new_clocks->dppclk_khz = 100000;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue