From: Armin Wolf <W_Armin@gmx.de>
To: Derek John Clark <derekjohn.clark@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
"Jean Delvare" <jdelvare@suse.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Alok Tiwari" <alok.a.tiwari@oracle.com>,
"David Box" <david.e.box@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 1/4] platform/x86: (ayn-ec) Add PWM Fan HWMON Interface
Date: Mon, 11 Aug 2025 10:38:37 +0200 [thread overview]
Message-ID: <5531e051-ad62-4cfd-a733-21f04385e1bb@gmx.de> (raw)
In-Reply-To: <CAFqHKTnO2NQ+_q_FOwT74Ukg7tx2k3B_sksEhNBzuCeZEWe3FQ@mail.gmail.com>
Am 11.08.25 um 00:27 schrieb Derek John Clark:
> On Mon, Jul 28, 2025 at 9:10 PM Armin Wolf <W_Armin@gmx.de> wrote:
>> Am 29.07.25 um 04:58 schrieb Derek John Clark:
>>
>>> On Sat, Jul 26, 2025 at 4:32 PM Armin Wolf <W_Armin@gmx.de> wrote:
>>>> Am 26.07.25 um 22:40 schrieb Derek J. Clark:
>>>>
>>>>> Adds platform driver for AYN Loki and Tectoy Zeenix lines of handheld
>>>>> devices. This patch implements a hwmon interface for EC provided manual
>>>>> PWM fan control and user defined fan curves. A global ACPI lock is used
>>>>> when reading or writing from the EC.
>>>>>
>>>>> There are 4 fan modes implemented in this patch. Modes 0-3 act in
>>>>> accordance with the standard hwmon logic where 0 is 100% fan speed, 1 is
>>>>> manual control, and 2 is automatic control. As the EC only provides 3
>>>>> modes by default, mode 0 is implemented by setting the device to manual
>>>>> and then setting fan speed to 100% directly. In mode 1 the PWM duty cycle
>>>>> is set in sysfs with values [0-255], which are then scaled to the EC max
>>>>> of 128. Mode 4 is an automatic mode where the fan curve is user defined.
>>>>> There are 5 total set points and each set point takes a temperature in
>>>>> Celsius [0-100] and a PWM duty cycle [0-255]. When the CPU temperature
>>>>> reaches a given set point, the corresponding duty cycle is automatically
>>>>> set by the EC.
>>>>>
>>>>> Signed-off-by: Derek J. Clark <derekjohn.clark@gmail.com>
>>>>>
>>>>> space
>>>> Interesting, do you have access to such a device? If yes then i would be very interested
>>>> in looking at the ACPI tables shipped with said device.
>>> Hi Armin,
>>>
>>> I have a Loki Max, and know someone with a Loki Zero. Do you want
>>> plain text acpidump or a decoded DSDT.dat attached?
>> I would prefer the plain text acpidump, as the SSDT tables often contain important data.
>>
> Attached is the plain text acpidump, sorry for the delay. I'll also
> note that Ayn provided me with documentation of the EC commands for
> this driver.
>
> Cheers,
> - Derek
Nice :)
I also noticed that the ACPI code itself uses EC register 0xB0 to control the battery thermal limit. This would
conflict with your usage of register 0xB0 as the RED RGB value. Does the documentation mention this register?
Thanks,
Armin Wolf
next prev parent reply other threads:[~2025-08-11 8:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 20:40 [PATCH v3 0/4] Add AYN EC Platform Driver Derek J. Clark
2025-07-26 20:40 ` [PATCH v3 1/4] platform/x86: (ayn-ec) Add PWM Fan HWMON Interface Derek J. Clark
2025-07-26 23:32 ` Armin Wolf
2025-07-29 2:58 ` Derek John Clark
2025-07-29 4:09 ` Armin Wolf
2025-08-10 22:27 ` Derek John Clark
2025-08-11 8:38 ` Armin Wolf [this message]
2025-07-28 16:31 ` kernel test robot
2025-07-29 3:39 ` Randy Dunlap
2025-07-28 21:34 ` kernel test robot
2025-07-26 20:40 ` [PATCH v3 2/4] platform/x86: (ayn-ec) Add Temperature Sensors Derek J. Clark
2025-07-26 23:37 ` Armin Wolf
2025-07-29 3:02 ` Derek John Clark
2025-07-26 20:40 ` [PATCH v3 3/4] platform/x86: (ayn-ec) Add RGB Interface Derek J. Clark
2025-07-26 23:58 ` Armin Wolf
2025-07-29 3:25 ` Derek John Clark
2025-07-29 4:18 ` Armin Wolf
2025-07-28 23:36 ` kernel test robot
2025-07-26 20:40 ` [PATCH v3 4/4] platform/x86: (ayn-ec) Add AYN EC Platform Documentation Derek J. Clark
2025-07-27 0:03 ` Armin Wolf
2025-07-29 3:26 ` Derek John Clark
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=5531e051-ad62-4cfd-a733-21f04385e1bb@gmx.de \
--to=w_armin@gmx.de \
--cc=alok.a.tiwari@oracle.com \
--cc=david.e.box@linux.intel.com \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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®