From: Marco Scardovi <scardracs@disroot.org>
To: ilpo.jarvinen@linux.intel.com
Cc: scardracs@disroot.org, corentin.chary@gmail.com,
denis.benato@linux.dev, hansg@kernel.org,
linux-kernel@vger.kernel.org, luke@ljones.dev,
platform-driver-x86@vger.kernel.org
Subject: [PATCH v2 0/1] platform/x86: asus-armoury: add power limits quirk for G614FM
Date: Sat, 19 Sep 2026 07:16:16 +0200 [thread overview]
Message-ID: <cover.1789794282.git.scardracs@disroot.org> (raw)
In-Reply-To: <2ac49a94-be85-1a2f-a43a-a376d2545a01@linux.intel.com>
Hi Ilpo,
thanks for the review.
While working on some other models it gets tangled with the EXACT_MATCH
in this one too and did not notice. Some models contains both the "base"
version (like G614FM) and a minor upgraded version (like G614FM2 or
G614FM4: it's not that the case but we'll use it as reference): these
models have, sometimes, different Wattages on CPU/GPU so we can't use
the DMI_MATCH for these, as the 2/4 models would end up inside the
base model incorrectly.
Changes since v1:
- Use DMI_MATCH() instead of DMI_EXACT_MATCH()
- Place the entry with the other G614 models
- Fix indentation and field order to match neighbouring entries
- Set requires_fan_curve, as on the other G614 quirks
Link for v1:
https://lore.kernel.org/all/20260828065904.11355-1-scardracs@disroot.org/
Marco Scardovi (1):
platform/x86: asus-armoury: add power limits quirk for G614FM
drivers/platform/x86/asus-armoury.h | 32 +++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
--
2.55.0
next prev parent reply other threads:[~2026-09-19 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 6:59 [PATCH] platform/x86: asus-armoury: add power limits quirk for G614FM Marco Scardovi
2026-09-18 17:06 ` Ilpo Järvinen
2026-09-19 5:16 ` Marco Scardovi [this message]
2026-09-19 5:16 ` [PATCH v2 1/1] " Marco Scardovi
2026-10-05 17:45 ` [PATCH v2 0/1] " Ilpo Järvinen
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=cover.1789794282.git.scardracs@disroot.org \
--to=scardracs@disroot.org \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--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.