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: Tue, 01 Aug 2023 13:52:40 +0000 [thread overview]
Message-ID: <bug-217696-215701-aMu1nNZj1D@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 #27 from Artem S. Tashkinov (aros@gmx.com) ---
Dear Mario Limonciello and Alex Deucher,
I've discovered multiple other HP laptops affected by the issue of AMD Phoenix
APUs never reaching their advertised boost speeds. It's not about Linux AMD PMF
driver, it's under Windows:
HP OMEN by HP Gaming Laptop 16-xd0xxx, 7840HS - 4619MHz limit
https://browser.geekbench.com/v6/cpu/1868206.gb6
HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC, 7840HS - 4500MHz limit
https://browser.geekbench.com/v6/cpu/2027018.gb6
HP Victus by HP Gaming Laptop 16-s0xxx, 7840HS - 4619MHz limit
https://browser.geekbench.com/v6/cpu/1638542.gb6
HP EliteBook 845 14 inch G10 Notebook PC, 7840HS - 4500MHz limit
https://browser.geekbench.com/v6/cpu/1946323.gb6
HP EliteBook 845 14 inch G10 Notebook PC, 7940HS - 4500MHz limit
https://browser.geekbench.com/v6/cpu/1958365.gb6
I know you know people in AMD who work with your partners - would be great if
they contacted HP and ask them to remove the artificial limit.
Thank you very much!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2023-08-01 13:52 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
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 [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=bug-217696-215701-aMu1nNZj1D@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.