drm/amd/display: Clear GPINT after DMCUB has reset
[Why] Otherwise we can end up processing whatever was left in the register if the DMCUB was previously reset. If DMCUB gets force reset too early from another client then we might not have even acked the disable yet - causing DMCUB instantly shutdown if the command was 10020000. [How] Move the GPINT clear outside of the reset loop and do it unconditionally after the DMCUB has been properly reset. Reviewed-by: Roy Chan <roy.chan@amd.com> Reviewed-by: Eric Yang <Eric.Yang2@amd.com> Acked-by: Anson Jacob <Anson.Jacob@amd.com> Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
This commit is contained in:
parent
c71f260ad4
commit
19c618e613
|
@ -115,10 +115,6 @@ void dmub_dcn31_reset(struct dmub_srv *dmub)
|
|||
break;
|
||||
}
|
||||
|
||||
/* Clear the GPINT command manually so we don't reset again. */
|
||||
cmd.all = 0;
|
||||
dmub->hw_funcs.set_gpint(dmub, cmd);
|
||||
|
||||
/* Force reset in case we timed out, DMCUB is likely hung. */
|
||||
}
|
||||
|
||||
|
@ -130,6 +126,10 @@ void dmub_dcn31_reset(struct dmub_srv *dmub)
|
|||
REG_WRITE(DMCUB_OUTBOX1_RPTR, 0);
|
||||
REG_WRITE(DMCUB_OUTBOX1_WPTR, 0);
|
||||
REG_WRITE(DMCUB_SCRATCH0, 0);
|
||||
|
||||
/* Clear the GPINT command manually so we don't send anything during boot. */
|
||||
cmd.all = 0;
|
||||
dmub->hw_funcs.set_gpint(dmub, cmd);
|
||||
}
|
||||
|
||||
void dmub_dcn31_reset_release(struct dmub_srv *dmub)
|
||||
|
|
Loading…
Reference in New Issue