Re: [PATCH 0/2] cpufreq/amd-pstate register write fixes

[Mario Limonciello <superm1@kernel.org>]

On 10/29/26 07:19, Christian Loehle wrote:
> Two issues that popped up when trying to integrate an AMD machine into
> my testing for acpi-cppc, in particular for this (otherwise
> unrelated) patch:
> https://lore.kernel.org/lkml/20261020121846.691218-2-sumitg@nvidia.com/
> 
> The first is rather straightforward, I think the case was just not
> considered during the refactor of the Fixes commit.
> The second is part of the resume handling and was introduced when
> that restored the register values (DESIRED derived from policy->cur).
> My platform seems to handle it well, but it's still strange
> behaviour, so why not fix it.
> (Also of course the resume value will generally be overwritten and
> therefore 'fixed' anyway.)
> 
> Christian Loehle (2):
>    cpufreq/amd-pstate: Keep minimum requests within policy limits
>    cpufreq/amd-pstate: Clamp desired perf on resume
> 
>   drivers/cpufreq/amd-pstate.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> 
> base-commit: c339f4010dea8b0d754f84ace70cd1b089878ef8

Thanks for the fixes.  I'll pick them up for 7.4-rc2.

Acked-by: Mario Limociello (AMD) <superm1@kernel.org>