All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 217696] Looking for a way to enable power saving mode for Ryzen APUs, along with limiting the upper temperature and total power consumption
Date: Wed, 26 Jul 2023 14:24:15 +0000	[thread overview]
Message-ID: <bug-217696-215701-g7lYhSpxLM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217696-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217696

--- Comment #22 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> The patched driver outputs slightly different debug messages:

This looks correct to me now for what amd-pmf can support today.

> Originally I was looking for a way to control my APU TDP(TTP) and maximum
> temperature threshold *without* using ryzenadj because CPU control registers
> are locked in secure boot mode.

This isn't something AMD supports.  The APU coefficients are set by system
designers in their firmware as a result of the hardware design decisions.

That's why I'm fixating on getting the method of coefficient configuration
working.  Some OEMs do it entirely in their EC, some do it entirely in PMF,
some do a combination and some it with the involvement of code running in TEE.

We will need to wait until the other bits are supported by amd-pmf to revisit
this issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-07-26 14:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-217696-215701@https.bugzilla.kernel.org/>
2023-07-24 18:22 ` [Bug 217696] Looking for a way to enable power saving mode for Ryzen APUs, along with limiting the upper temperature and total power consumption bugzilla-daemon
2023-07-24 18:36 ` bugzilla-daemon
2023-07-24 18:39 ` bugzilla-daemon
2023-07-24 18:54 ` bugzilla-daemon
2023-07-24 19:51 ` bugzilla-daemon
2023-07-24 19:52 ` bugzilla-daemon
2023-07-26  9:36 ` bugzilla-daemon
2023-07-26 10:01 ` bugzilla-daemon
2023-07-26 10:03 ` bugzilla-daemon
2023-07-26 10:34 ` bugzilla-daemon
2023-07-26 12:53 ` bugzilla-daemon
2023-07-26 14:02 ` bugzilla-daemon
2023-07-26 14:15 ` bugzilla-daemon
2023-07-26 14:24 ` bugzilla-daemon [this message]
2023-07-26 14:35 ` bugzilla-daemon
2023-07-26 19:05 ` bugzilla-daemon
2023-07-26 19:12 ` bugzilla-daemon
2023-07-26 19:35 ` bugzilla-daemon
2023-07-26 19:55 ` bugzilla-daemon
2023-08-01 13:52 ` bugzilla-daemon

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=bug-217696-215701-g7lYhSpxLM@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.