mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	gautham.shenoy@amd.com, perry.yuan@amd.com, ray.huang@amd.com,
	rafael@kernel.org, viresh.kumar@linaro.org
Subject: Re: [PATCH] cpufreq/amd-pstate: Fix amd_pstate mode switch on shared memory systems
Date: Mon, 7 Oct 2024 11:31:45 -0500	[thread overview]
Message-ID: <ab486635-1827-49b5-9e5f-73f62b86c82a@amd.com> (raw)
In-Reply-To: <20241004122303.94283-1-Dhananjay.Ugwekar@amd.com>

On 10/4/2024 07:23, Dhananjay Ugwekar wrote:
> While switching the driver mode between active and passive, Collaborative
> Processor Performance Control (CPPC) is disabled in
> amd_pstate_unregister_driver(). But, it is not enabled back while registering
> the new driver (passive or active). This leads to the new driver mode not
> working correctly, so enable it back in amd_pstate_register_driver().
> 
> Fixes: 3ca7bc818d8c ("cpufreq: amd-pstate: Add guided mode control support via sysfs")
> Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>

Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>

I think as a minimally risky fix to go to 6.12-rcX this makes sense, but 
looking at all this code there is a bit of duplication that exists that 
we should do a more general cleanup for 6.13.

So I'll queue this up in my -fixes branch for 6.12-rcX. but please do 
the bigger cleanup as a follow up that we can land for 6.13.

> ---
>   drivers/cpufreq/amd-pstate.c | 10 ++++++++++
>   1 file changed, 10 insertions(+)
> 
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index cdc08d2ddd52..4acf5fbeb116 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -1191,11 +1191,21 @@ static int amd_pstate_register_driver(int mode)
>   		return -EINVAL;
>   
>   	cppc_state = mode;
> +
> +	ret = amd_pstate_enable(true);
> +	if (ret) {
> +		pr_err("failed to enable cppc during amd-pstate driver registration, return %d\n",
> +		       ret);
> +		amd_pstate_driver_cleanup();
> +		return ret;
> +	}
> +
>   	ret = cpufreq_register_driver(current_pstate_driver);
>   	if (ret) {
>   		amd_pstate_driver_cleanup();
>   		return ret;
>   	}
> +
>   	return 0;
>   }
>   


      reply	other threads:[~2024-10-07 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 12:23 Dhananjay Ugwekar
2024-10-07 16:31 ` Mario Limonciello [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ab486635-1827-49b5-9e5f-73f62b86c82a@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Dhananjay.Ugwekar@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=perry.yuan@amd.com \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®