[PATCH v3 0/3] Implement SMU message register protection

Matt Coffin mcoffin13 at gmail.com
Thu Feb 27 21:00:59 UTC 2020



On 2/27/20 1:49 PM, Alex Deucher wrote:

> BTW, I think you had another change to clean up some of the navi10
> code, care to send that one out too?
> 
> Alex

That was in there just since I was doing some debugging related to
https://gitlab.freedesktop.org/drm/amd/issues/1053 and voltage levels
being different on linux compared to Windows at the same overdrive
settings. It's not of any use (currently), so I just left it out. It's
not related to this patchset. I'll toss it in the series I come up with
that would fix that issue (If I ever get there... I'm pretty stumped at
this point).

Thanks for checking, though. On it's own, that change would have been
functionally moot, only required if the GetVoltageByDpmOverdrive SMU
message becomes useful in the future.

Not to piggy back on this, but if you have any results, negative or
positive on the voltage problem, or power limit firmware "problem"
(https://gitlab.freedesktop.org/drm/amd/issues/1043), I'd love to either
help reproduce, or work on a fix.

Thanks again for the snappy responses, glad I could help out some more!


More information about the amd-gfx mailing list