From: "Derek J. Clark" <derekjohn.clark@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Cryolita PukNgae <cryolitia@gmail.com>,
"Derek J . Clark" <derekjohn.clark@gmail.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC] hwmon: pwm_enable clarification
Date: Sun, 27 Oct 2024 10:48:14 -0700 [thread overview]
Message-ID: <20241027174836.8588-1-derekjohn.clark@gmail.com> (raw)
Greetings all,
I am working with Cryolita to fix up the GPD driver she submitted recently:
https://lore.kernel.org/all/20240718-gpd_fan-v4-0-116e5431a9fe@gmail.com/
We are currently having a discussion about the meaning of this part of the
documentation and are seeking some guidance from upstream.
> pwm[1-*]_enable
> Fan speed control method:
> 0: no fan speed control (i.e. fan at full speed)
> 1: manual fan speed control enabled (using pwm[1-*])
> 2+: automatic fan speed control enabled
> Check individual chip documentation files for automatic mode
> details.
> RW
In oxp-sensors we took 0 to mean "no kernel control" so a setting of 0 is
technically "automatic" but fully controlled by the hardware with no
interaction from the driver. In her original driver draft she had taken this
literally to have the driver set the fan speed to 100% on this setting rather
then give back control to the hardware. My question is simply what is the
correct interpretation here? Ideally I would like to see this interface match
as existing userspace software is expecting 0 as hardware controlled and 1 as
manually controlled, but we also want to ensure this is correct before we
submit a v5.
Thank you for your time,
Derek
next reply other threads:[~2024-10-27 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 17:48 Derek J. Clark [this message]
2024-10-27 18:16 ` [RFC] hwmon: pwm_enable clarification Guenter Roeck
2024-10-27 18:29 ` Derek John Clark
2024-10-27 18:59 ` Guenter Roeck
2024-10-27 19:10 ` Derek John Clark
2024-10-27 20:05 ` 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=20241027174836.8588-1-derekjohn.clark@gmail.com \
--to=derekjohn.clark@gmail.com \
--cc=corbet@lwn.net \
--cc=cryolitia@gmail.com \
--cc=jdelvare@suse.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 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.