From: Mario Limonciello <mario.limonciello@amd.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Huang Rui <ray.huang@amd.com>,
gautham.shenoy@amd.com, Perry Yuan <perry.yuan@amd.com>,
rafael@kernel.org, viresh.kumar@linaro.org
Subject: Re: [PATCH 1/2] cpufreq: amd-pstate: Use CPUFREQ_POLICY_UNKNOWN
Date: Wed, 11 Dec 2024 10:37:43 -0600 [thread overview]
Message-ID: <08f23b24-75f4-4d5f-9d54-002e13bca1c9@amd.com> (raw)
In-Reply-To: <20241211122605.3048503-2-christian.loehle@arm.com>
On 12/11/2024 06:26, Christian Loehle wrote:
> epp_policy uses the same values as cpufreq_policy.policy and resets
> to CPUFREQ_POLICY_UNKNOWN during offlining. Be consistent about
> it and initialize to CPUFREQ_POLICY_UNKNOWN instead of 0, too.
>
> No functional change intended.
>
> Cc: Huang Rui <ray.huang@amd.com>
> Cc: <gautham.shenoy@amd.com>
> Cc: Mario Limonciello <mario.limonciello@amd.com>
> Cc: Perry Yuan <perry.yuan@amd.com>
> Signed-off-by: Christian Loehle <christian.loehle@arm.com>
> ---
> drivers/cpufreq/amd-pstate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index d7630bab2516..546e69cbdf76 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -1449,7 +1449,7 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)
> return -ENOMEM;
>
> cpudata->cpu = policy->cpu;
> - cpudata->epp_policy = 0;
> + cpudata->epp_policy = CPUFREQ_POLICY_UNKNOWN;
>
> ret = amd_pstate_init_perf(cpudata);
> if (ret)
Hi,
Thanks for the patch. In this case it's actually not needed though.
Some of the in-flight content for 6.14 drops that variable. This is on
the superm1/linux.git bleeding-edge branch (which content will promote
to superm1/linux.git linux-next branch soon and eventually come to
linux-pm).
https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/commit/?h=bleeding-edge&id=b8321230569dc17852a7f7adc7715ad07538cbeb
next prev parent reply other threads:[~2024-12-11 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 12:26 [PATCH 0/2] cpufreq: Init epp_policy as CPUFREQ_POLICY_UNKNOWN Christian Loehle
2024-12-11 12:26 ` [PATCH 1/2] cpufreq: amd-pstate: Use CPUFREQ_POLICY_UNKNOWN Christian Loehle
2024-12-11 16:37 ` Mario Limonciello [this message]
2024-12-11 12:26 ` [PATCH 2/2] cpufreq: intel_pstate: " Christian Loehle
2024-12-18 14:50 ` Rafael J. Wysocki
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=08f23b24-75f4-4d5f-9d54-002e13bca1c9@amd.com \
--to=mario.limonciello@amd.com \
--cc=christian.loehle@arm.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®