Linux Power Management development
 help / color / mirror / Atom feed
From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Mario Limonciello <mario.limonciello@amd.com>,
	Huang Rui <ray.huang@amd.com>, Perry Yuan <perry.yuan@amd.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq/amd-pstate: Supply nominal/lowest freq for TRX40-based motherboards
Date: Wed, 7 Oct 2026 21:59:01 +0200	[thread overview]
Message-ID: <ed52d799-078c-4148-b7df-0413f2d65694@suse.cz> (raw)
In-Reply-To: <ab7921dd-1a28-4df4-a4a8-718e1489ec33@amd.com>

On Wed Oct 7, 2026 21:45, Mario Limonciello wrote:
> On 10/7/26 14:38, Giovanni Gherdovich wrote:
>> On Wed Oct 7, 2026 16:56, Mario Limonciello wrote:
>>> [...]
>>> I don't understand why core count matters though.
>>
>> My thinking was:
>>
>> 1. I want to make the "quirk" to match as many chips as possible, to
>>     make it more useful and worthwhile.
>> 2. The doc I have, "Power and Thermal Data Sheet" (publication #56736
>>     in the AMD doc library), is for family 0x17, models 0x30-0x3F
>>     processors.
>> 3. Problem: these have different nominal frequencies, depending on the
>>     core count. Specifically:
>>     24 cores: 3800 MHz (like the Ryzen 3090x I need)
>>     32 cores: 3700 Mhz
>>     64 cores: 2900 MHz
>> 4. Thus I decided to match for family 0x17, model 0x30-0x3f, 24 cores.
>>     Without the core count constraint, I couldn't tell which of the
>>     three nominal frequencies above should apply.
> 
> If there does need to be a quirk I guess I would actually say there
> should be 3 quirks then. One for each core count version.

Makes sense.

>> All that said, I've asked the openSUSE user to test the newer BIOS,
>> we'll see what that gives.
> 
> Thanks!  Based on the findings from the BIOS update everything in
> this thread should be enough to either make a v2 incorporating
> feedback (mostly making it clearer) or to drop the patch.

Yes I think so. Thanks a lot for your support so far.


Giovanni

  reply	other threads:[~2026-10-07 19:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 14:41 [PATCH] cpufreq/amd-pstate: Supply nominal/lowest freq for TRX40-based motherboards Giovanni Gherdovich
2026-10-07 14:56 ` Mario Limonciello
2026-10-07 15:04   ` Kyle Gospodnetich
2026-10-07 15:05     ` Mario Limonciello
2026-10-07 17:36       ` Kyle Gospodnetich
2026-10-07 17:43         ` Kyle Gospodnetich
2026-10-07 18:08           ` Mario Limonciello
2026-10-07 18:30             ` Kyle Gospodnetich
2026-10-07 18:32               ` Mario Limonciello
2026-10-07 18:49                 ` Giovanni Gherdovich
2026-10-07 19:38   ` Giovanni Gherdovich
2026-10-07 19:45     ` Mario Limonciello
2026-10-07 19:59       ` Giovanni Gherdovich [this message]
2026-10-08  7:18       ` Giovanni Gherdovich
2026-10-08 12:38         ` Mario Limonciello

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=ed52d799-078c-4148-b7df-0413f2d65694@suse.cz \
    --to=ggherdovich@suse.cz \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --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