From: Mario Limonciello <mario.limonciello@amd.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Perry Yuan <perry.yuan@amd.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:CPU FREQUENCY SCALING FRAMEWORK"
<linux-pm@vger.kernel.org>,
Mario Limonciello <superm1@kernel.org>
Subject: Re: [PATCH v3 0/3] Add support for Zen 6 client EPP tunings
Date: Thu, 10 Sep 2026 15:59:38 -0500 [thread overview]
Message-ID: <9324cce8-aac9-4081-ba6c-65da18b80bc2@amd.com> (raw)
In-Reply-To: <15beffa4-aa61-4e9c-86b8-764fd43989b7@amd.com>
On 9/10/26 02:32, K Prateek Nayak wrote:
> Hello Mario,
>
> On 9/9/2026 9:06 AM, Mario Limonciello wrote:
>> Zen6 client platform firmware uses EPP values differently than previous
>> platforms. To optimize performance and power consumption tunings are
>> applied that match platform characteristics.
>>
>> v3:
>> * Enhancements suggested by Prateek to patch 1
>
> I took it for a spin yesterday while debugging another issue and
> everything ran fine. Feel free to include:
>
> Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
> Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
>
Thanks! I'll bring it to my bleeding edge testing tree.
prev parent reply other threads:[~2026-09-10 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 3:36 Mario Limonciello
2026-09-09 3:36 ` [PATCH v3 1/3] cpufreq/amd-pstate: Add per SoC and per core type EPP tuning values Mario Limonciello
2026-09-09 3:36 ` [PATCH v3 2/3] cpufreq/amd-pstate: Add EPP tunings for Zen6 client platforms Mario Limonciello
2026-09-09 3:36 ` [PATCH v3 3/3] cpufreq/amd-pstate: Show a warning if missing EPP tunings Mario Limonciello
2026-09-10 7:32 ` [PATCH v3 0/3] Add support for Zen 6 client " K Prateek Nayak
2026-09-10 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=9324cce8-aac9-4081-ba6c-65da18b80bc2@amd.com \
--to=mario.limonciello@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=superm1@kernel.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®