From: Vyacheslav Vankevich <crazycoder@yandex.ru>
To: platform-driver-x86@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Vyacheslav Vankevich <crazycoder@yandex.ru>
Subject: [PATCH] platform/x86: asus-armoury: add power limits quirk for FX707ZC4
Date: Thu, 19 Nov 2026 22:12:24 +0300 [thread overview]
Message-ID: <20261119191224.15755-1-crazycoder@yandex.ru> (raw)
Add PPT power limits for the ASUS TUF Gaming F17 FX707ZC4
(Intel Core i5-12500H, NVIDIA GeForce RTX 3050 Laptop).
The EC starts with a 5 W package limit, which clamps the CPU to 400 MHz
until userspace writes working limits. The firmware ignores PPT writes
unless a custom fan curve is active, so mark the quirk with
requires_fan_curve.
Limits validated on the hardware (BIOS FX707ZC4.311, 2024-10-18):
- AC: PL1 25-90 W (default 45), PL2 35-115 W (default 90)
- DC: PL1 25-45 W (default 35), PL2 35-60 W (default 60)
Signed-off-by: Vyacheslav Vankevich <crazycoder@yandex.ru>
---
drivers/platform/x86/asus-armoury.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
--- a/drivers/platform/x86/asus-armoury.h
+++ b/drivers/platform/x86/asus-armoury.h
@@ -1229,6 +1229,30 @@
},
{
.matches = {
+ DMI_MATCH(DMI_BOARD_NAME, "FX707ZC4"),
+ },
+ .driver_data = &(struct power_data) {
+ .ac_data = &(struct power_limits) {
+ .ppt_pl1_spl_min = 25,
+ .ppt_pl1_spl_def = 45,
+ .ppt_pl1_spl_max = 90,
+ .ppt_pl2_sppt_min = 35,
+ .ppt_pl2_sppt_def = 90,
+ .ppt_pl2_sppt_max = 115,
+ },
+ .dc_data = &(struct power_limits) {
+ .ppt_pl1_spl_min = 25,
+ .ppt_pl1_spl_def = 35,
+ .ppt_pl1_spl_max = 45,
+ .ppt_pl2_sppt_min = 35,
+ .ppt_pl2_sppt_def = 60,
+ .ppt_pl2_sppt_max = 60,
+ },
+ .requires_fan_curve = true,
+ },
+ },
+ {
+ .matches = {
DMI_MATCH(DMI_BOARD_NAME, "G533QS"),
},
.driver_data = &(struct power_data) {
reply other threads:[~2026-11-19 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261119191224.15755-1-crazycoder@yandex.ru \
--to=crazycoder@yandex.ru \
--cc=linux-kernel@vger.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 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®