forked from Minki/linux
drm/amd/display: Call ATOM_INIT instead of ATOM_ENABLE for DMCUB
[Why] DMCUB command table doesn't support ATOM_ENABLE/ATOM_DISABLE anymore so we never end up calling the DCN init path in DMCUB. [How] Map ATOM_ENABLE to ATOM_INIT only for DMCUB command table offloading. Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Reviewed-by: Tony Cheng <Tony.Cheng@amd.com> Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
This commit is contained in:
parent
0167da498d
commit
cc934031dc
@ -711,6 +711,10 @@ static void enable_disp_power_gating_dmcub(
|
||||
power_gating.header.sub_type = DMUB_CMD__VBIOS_ENABLE_DISP_POWER_GATING;
|
||||
power_gating.power_gating.pwr = *pwr;
|
||||
|
||||
/* ATOM_ENABLE is old API in DMUB */
|
||||
if (power_gating.power_gating.pwr.enable == ATOM_ENABLE)
|
||||
power_gating.power_gating.pwr.enable = ATOM_INIT;
|
||||
|
||||
dc_dmub_srv_cmd_queue(dmcub, &power_gating.header);
|
||||
dc_dmub_srv_cmd_execute(dmcub);
|
||||
dc_dmub_srv_wait_idle(dmcub);
|
||||
|
Loading…
Reference in New Issue
Block a user