>In addition to that, vega20_set_fclk= _to_highest_dpm_level is called several times before the card is initialize= d and even on 5.2.7 works. Something happens during or just before the init= ialization stage that stops smum_send_msg_to_smc_with_parameter accepting 1= 001 as a valid value, as it does until that point. Could be we've got a race condition between the powerplay setup and amdgpu handing off the card to drm_dev_register to advertise it for normal use. drm_dev_register is responsible for the "[drm] Initialized" messa= ge: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm= /drm_drv.c#L994 And it seems like amdgpu calls it here: https://github.com/torvalds/linux/blob/master/= drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c#L1054 Odd that it's doing this if powerplay still has more work to do. And that m= ight be why vega20_set_uclk_to_highest_dpm_level fails that last time.