mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Vishal Badole <Vishal.Badole@amd.com>
Cc: ray.huang@amd.com, rafael@kernel.org, viresh.kumar@linaro.org,
	perry.yuan@amd.com, kprateek.nayak@amd.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: amd-pstate: Update Zen6 client EPP tuning values
Date: Mon, 28 Sep 2026 15:59:04 -0500	[thread overview]
Message-ID: <83294b60-a371-43b8-be01-2ff122df2b5f@amd.com> (raw)
In-Reply-To: <20260928203523.1290623-1-Vishal.Badole@amd.com>



On 9/28/26 15:35, Vishal Badole wrote:
> The per-CPU-type EPP values for the Zen6 client platform are further
> tuned based on platform characterization. Adjust the performance and
> low-power core entries so each core type uses its intended EPP settings.
> 
> Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
> Signed-off-by: Vishal Badole <Vishal.Badole@amd.com>
> ---
> This patch is based on Mario Limonciello's:
>    "cpufreq/amd-pstate: Add EPP tunings for Zen6 client platforms"
>    https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/commit/?id=114a157e8d30601d024b53564a0fe54202f6567f
> 

Appreciated.

Applied to superm1/linux.git bleeding-edge.

I'll include this in my last PR for 7.4.

>   drivers/cpufreq/amd-pstate.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index 83960a6336b9..2529cee9a6cc 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -211,7 +211,7 @@ static const struct amd_pstate_epp_soc epp_soc_zen6_client __initconst = {
>   		.performance		= 25,
>   		.balance_performance	= 51,
>   		.balance_power		= 64,
> -		.power			= 64,
> +		.power			= 115,
>   	},
>   	.efficiency_core = {
>   		.performance		= 25,
> @@ -221,9 +221,9 @@ static const struct amd_pstate_epp_soc epp_soc_zen6_client __initconst = {
>   	},
>   	.low_power_core = {
>   		.performance		= 25,
> -		.balance_performance	= 51,
> +		.balance_performance	= 64,
>   		.balance_power		= 64,
> -		.power			= 115,
> +		.power			= 64,
>   	},
>   };
>   


      reply	other threads:[~2026-09-28 20:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 20:35 Vishal Badole
2026-09-28 20:59 ` 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=83294b60-a371-43b8-be01-2ff122df2b5f@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Vishal.Badole@amd.com \
    --cc=kprateek.nayak@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®