From: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>
To: patrick@stwcx.xyz
Cc: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH v4 0/3] hwmon: max31790: support to config PWM as TACH
Date: Thu, 2 Nov 2023 11:28:29 +0800 [thread overview]
Message-ID: <20231102032834.3827289-1-Delphine_CC_Chiu@wiwynn.com> (raw)
Support to config PWM as TACH in MAX31790 driver.
Add binding document for MAX31790 driver.
Add fanN_enable for all fans
---
Changelog:
v4 - Add fanN_enable for all fans.
v3 - Use 'sensor-type' in 'channel' node to config pwm as tach.
- Changed the status in MAINTAINERS to 'Maintained'.
v2 - Remove unnecessary parentheses.
- Add more error handling.
- Change the type of "pwm-as-tach" from u8 to u32 to match binding
document.
- Add dt-bindings for the MAXIM MAX31790.
v1 - Support to config PWM as TACH
Delphine CC Chiu (3):
hwmon: max31790: support to config PWM as TACH
dt-bindings: hwmon: add MAX31790
hwmon: max31790: add fanN_enable for all fans
.../bindings/hwmon/maxim,max31790.yaml | 89 +++++++++++
Documentation/hwmon/max31790.rst | 2 +-
MAINTAINERS | 6 +
drivers/hwmon/max31790.c | 140 ++++++++++++++----
4 files changed, 210 insertions(+), 27 deletions(-)
create mode 100644 Documentation/devicetree/bindings/hwmon/maxim,max31790.yaml
--
2.25.1
next reply other threads:[~2023-11-02 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 3:28 Delphine CC Chiu [this message]
2023-11-02 3:28 ` [PATCH v4 1/3] " Delphine CC Chiu
2023-11-02 3:28 ` [PATCH v4 2/3] dt-bindings: hwmon: add MAX31790 Delphine CC Chiu
2023-11-02 3:28 ` [PATCH v4 3/3] hwmon: max31790: add fanN_enable for all fans Delphine CC Chiu
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=20231102032834.3827289-1-Delphine_CC_Chiu@wiwynn.com \
--to=delphine_cc_chiu@wiwynn.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patrick@stwcx.xyz \
--cc=robh+dt@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®