From: Antheas Kapenekakis <lkml@antheas.dev>
To: Cryolitia PukNgae <cryolitia@uniontech.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Antheas Kapenekakis <lkml@antheas.dev>
Subject: [PATCH v1] hwmon: (gpd-fan) Add GPD Win 5
Date: Fri, 20 Feb 2026 17:16:01 +0100 [thread overview]
Message-ID: <20260220161601.2344291-1-lkml@antheas.dev> (raw)
The GPD Win 5 is a new device by GPD with an AMD AI MAX 385/395 chip.
It uses the same fan control registers as the GPD Win Duo. This
information was provided by GPD.
Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
---
The GPD Win 5 has dual fans, as noted in [1], there is potential that
they might be able to be controlled independently (duo writes on two
registers).
However, for my application I do not need independent controls so for
me this is good to merge.
If a follow-up patch separates the fans, I will not treat it as a
breaking ABI change and will just update my userspace, so it will be
fine to merge by me. Just, please cc when posting.
I verified the functionality of this patch.
[1] https://github.com/Cryolitia/gpd-fan-driver/pull/21
---
drivers/hwmon/gpd-fan.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/hwmon/gpd-fan.c b/drivers/hwmon/gpd-fan.c
index 237f496c4862..4c5e24b890c8 100644
--- a/drivers/hwmon/gpd-fan.c
+++ b/drivers/hwmon/gpd-fan.c
@@ -196,6 +196,14 @@ static const struct dmi_system_id dmi_table[] = {
},
.driver_data = &gpd_duo_drvdata,
},
+ {
+ // GPD Win 5 with AMD AI MAX 395
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "GPD"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "G1618-05"),
+ },
+ .driver_data = &gpd_duo_drvdata,
+ },
{
// GPD Pocket 4
.matches = {
base-commit: 598cf272195d27d2a45462baa051959dc53690e5
--
2.52.0
next reply other threads:[~2026-02-20 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 16:16 Antheas Kapenekakis [this message]
2026-02-20 20:28 ` [PATCH v1] hwmon: (gpd-fan) Add GPD Win 5 Guenter Roeck
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=20260220161601.2344291-1-lkml@antheas.dev \
--to=lkml@antheas.dev \
--cc=cryolitia@uniontech.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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