From: Guenter Roeck <linux@roeck-us.net>
To: alexei.solcanu@pm.me
Cc: Cryolitia PukNgae <cryolitia@uniontech.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Antheas Kapenekakis <lkml@antheas.dev>
Subject: Re: [PATCH v2 2/2] hwmon: (gpd-fan) Register both fans on the GPD Win 5
Date: Mon, 28 Sep 2026 04:05:43 -0700 [thread overview]
Message-ID: <72ea804b-6d62-4f31-985d-4f3f0359b5be@roeck-us.net> (raw)
In-Reply-To: <20260926-gpd-fan-duo-auto-v2-2-0a2ea41ee3b5@pm.me>
On Sat, Sep 26, 2026 at 04:11:21PM -0400, Alexei Solcanu via B4 Relay wrote:
> From: Alexei Solcanu <alexei.solcanu@pm.me>
>
> The GPD Win 5 uses gpd_duo_drvdata, which exposes a single fan and pwm
> channel: pwm1 writes the same duty cycle to both fans, and fan1_input
> only reads the first fan's RPM.
>
> The two fans have independent registers. Fan 1 uses duty cycle 0x047A
> and RPM 0x0478/0x0479, fan 2 uses duty cycle 0x047B and RPM
> 0x0476/0x0477. A duty cycle of 0 returns that fan to EC control.
>
> Add separate board data for the Win 5 and register fan1/pwm1 and
> fan2/pwm2, one channel per fan. Boards with a single fan are unchanged.
>
> This changes behaviour on the Win 5: pwm1 and pwm1_enable now control
> only the first fan. The second fan stays under EC control unless pwm2
> and pwm2_enable are used.
>
> The GPD Duo keeps a single channel, since it is untested and its
> second fan's RPM register is unknown.
>
> Tested on a GPD Win 5 (G1618-05).
>
> Suggested-by: Guenter Roeck <linux@roeck-us.net>
> Assisted-by: LLM
> Signed-off-by: Alexei Solcanu <alexei.solcanu@pm.me>
Another patch new revision sent as reply of a previous one.
Where does that idea come from ? Can _someone_ please let me know ?
It seems like a contagious disease, but no one is willing to admit
where they caught it.
Guenter
next prev parent reply other threads:[~2026-09-28 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 20:11 [PATCH v2 0/2] hwmon: (gpd-fan) Fix the second fan on duo boards, split Win 5 fans Alexei Solcanu via B4 Relay
2026-09-26 20:11 ` [PATCH v2 1/2] hwmon: (gpd-fan) Reset both fans to automatic on duo boards Alexei Solcanu via B4 Relay
2026-09-26 20:22 ` Antheas Kapenekakis
2026-09-26 20:11 ` [PATCH v2 2/2] hwmon: (gpd-fan) Register both fans on the GPD Win 5 Alexei Solcanu via B4 Relay
2026-09-26 20:32 ` Antheas Kapenekakis
2026-09-26 21:36 ` Alexei Solcanu
2026-09-26 21:52 ` Antheas Kapenekakis
2026-09-26 22:15 ` Alexei Solcanu
2026-09-28 11:05 ` Guenter Roeck [this message]
2026-09-28 12:03 ` Antheas Kapenekakis
2026-09-28 14:30 ` Guenter Roeck
2026-09-28 13:32 ` Alexei Solcanu
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=72ea804b-6d62-4f31-985d-4f3f0359b5be@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alexei.solcanu@pm.me \
--cc=corbet@lwn.net \
--cc=cryolitia@uniontech.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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