mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: W_Armin@gmx.de, sashal@kernel.org, Shyam-Sundar.S-k@amd.com,
	derekjohn.clark@gmail.com, denis.benato@linux.dev, i@rong.moe,
	linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: [RFC v4 2/4] platform/x86/amd: dptc: Add AMD DPTCi driver
Date: Thu, 12 Mar 2026 11:05:57 -0500	[thread overview]
Message-ID: <9843a54e-fafc-48cd-b92f-66cff9091848@amd.com> (raw)
In-Reply-To: <CAGwozwGUPuY9_wH6Bi+eSVm2o=F4Vgdv+URo9aTQ366vwptBOQ@mail.gmail.com>


>>
>> So please; do not make assumptions based on a lack of hard data.
>> If you don't have data for multiple years of a system or multiple chips
>> in the system, leave it off your quirk list.  They can always be added
>> later when the data is available.
> 
> Specifically for GPD, the userspace implementation has been tested on
> all generations. It is fine to choose a (lower) limit that works on
> all of them. The thermals did not change between generations.
> Saturation above 20W means that there is little difference between
> 22W, 25W, 28W, 30W, etc. If there is doubt, going lower is fine. Even
> if one device can do 5W more it does not matter (but the chassis,
> battery, and cooler are exactly the same; only the board was revised
> for the new SoC).
> 
> 8-20W is the sweet spot for these APUs. 8W and 15W are sane for
> low-power/balanced. The only question is how close to 30W should be
> the maximum and where performance should point to. This version does
> 25W for performance. 20W might be better for daily use until AC/DC
> detection.
> 
> We do not need to complicate things. All this driver needs to do is
> expose a slider from 4-30W. This covers 6800-HX370 for all vendors and
> matches user expectation. AI Max will need further research as I do
> not have a lot of data on its performance curve. Ayaneo had some drops
> between 2022-2023 that had lower TDP limits, but there is less than 1k
> units in existence.

User expectation and reality aren't necessarily the same.

Performance is tied to a thermal design.  A user might want to run a 
handheld at the max performance, but max performance is not purely a 
function of the APU.

It's a function of the APU + cooling solution + power distribution.

That's why I have been saying there need to be different values for 
different parts, and you can't make assumptions year to year.

Even if the external chassis plastics are identical, a different fan or 
heatpipe might be used and those are non-trivial impacts.

The values used should be calculated by performance measurements of the 
entire solution in a thermal chamber.

I know you're not going to be able to do that, but that's what 
manufacturers /should/ be doing.

  reply	other threads:[~2026-03-12 16:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 20:51 [RFC v4 0/4] platform/x86/amd: Add AMD DPTCi driver for TDP control in devices without vendor-specific controls Antheas Kapenekakis
2026-03-09 20:51 ` [RFC v4 1/4] Documentation: firmware-attributes: generalize save_settings entry Antheas Kapenekakis
2026-03-09 20:51 ` [RFC v4 2/4] platform/x86/amd: dptc: Add AMD DPTCi driver Antheas Kapenekakis
2026-03-10  4:01   ` Mario Limonciello
2026-03-10  8:02     ` Antheas Kapenekakis
2026-03-10 16:26       ` Mario Limonciello
2026-03-11 19:09         ` Antheas Kapenekakis
2026-03-12 13:24           ` Mario Limonciello
2026-03-12 13:47             ` Antheas Kapenekakis
2026-03-12 16:05               ` Mario Limonciello [this message]
2026-03-12 16:19                 ` Antheas Kapenekakis
2026-03-09 20:51 ` [RFC v4 3/4] platform/x86/amd: dptc: Add platform profile support Antheas Kapenekakis
2026-03-10  4:07   ` Mario Limonciello
2026-03-09 20:51 ` [RFC v4 4/4] platform/x86/amd: dptc: Add device entries for handheld PCs Antheas Kapenekakis
2026-03-10  4:11   ` Mario Limonciello
2026-03-10  8:13     ` Antheas Kapenekakis
2026-03-10 16:35       ` Mario Limonciello
2026-03-11 19:13         ` Antheas Kapenekakis
2026-03-12 13:26           ` Mario Limonciello
2026-03-10  2:43 ` [RFC v4 0/4] platform/x86/amd: Add AMD DPTCi driver for TDP control in devices without vendor-specific controls Mario Limonciello
2026-03-10  7:59   ` Antheas Kapenekakis
2026-10-15  9:35     ` Antheas Kapenekakis
2026-10-15 14:37       ` Mario Limonciello
2026-10-15 14:55         ` Antheas Kapenekakis
2026-10-15 15:03           ` Mario Limonciello
2026-10-15 15:13             ` Antheas Kapenekakis

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=9843a54e-fafc-48cd-b92f-66cff9091848@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Shyam-Sundar.S-k@amd.com \
    --cc=W_Armin@gmx.de \
    --cc=denis.benato@linux.dev \
    --cc=derekjohn.clark@gmail.com \
    --cc=i@rong.moe \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sashal@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®