From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org,
Changhuang Liang <changhuang.liang@starfivetech.com>
Subject: [PATCH v3 0/2] Add JHB100 Fan-Tach support
Date: Sun, 23 Aug 2026 20:02:32 -0700 [thread overview]
Message-ID: <20260824030234.9321-1-changhuang.liang@starfivetech.com> (raw)
StarFive Fan-Tach controller can support up to 16 fan tach input.
The series has been tested on the EVB1 board.
Change since v2:
PATCH 2:
- Fix typo in commit message: than ==> then
- Remove struct device *dev and struct mutex lock from struct starfive_fan_tach_data.
- Change return type of starfive_fan_tach_get_ch_en() to bool.
- Simplify the condition check in starfive_fan_read() by removing the unnecessary
intermediate ret variable assignment when checking the tachometer channel enable
status.
- Return an error when tach_ch >= STARFIVE_FAN_TACH_CH.
- Add a description that accessing the fan status can be time-consuming in certain
scenarios in starfive-fan-tach.rst.
v2: https://lore.kernel.org/all/20260819091601.41077-1-changhuang.liang@starfivetech.com/
v1: https://lore.kernel.org/all/20260428082337.743546-1-changhuang.liang@starfivetech.com/
Changhuang Liang (2):
dt-bindings: hwmon: Add starfive,jhb100-fan-tach
hwmon: (starfive-fan-tach) Add fan tach driver for StarFive JHB100
.../hwmon/starfive,jhb100-fan-tach.yaml | 93 +++
Documentation/hwmon/index.rst | 1 +
Documentation/hwmon/starfive-fan-tach.rst | 38 ++
MAINTAINERS | 8 +
drivers/hwmon/Kconfig | 14 +
drivers/hwmon/Makefile | 1 +
drivers/hwmon/starfive-fan-tach.c | 540 ++++++++++++++++++
7 files changed, 695 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/starfive,jhb100-fan-tach.yaml
create mode 100644 Documentation/hwmon/starfive-fan-tach.rst
create mode 100644 drivers/hwmon/starfive-fan-tach.c
--
2.25.1
next reply other threads:[~2026-08-24 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 3:02 Changhuang Liang [this message]
2026-08-24 3:02 ` [PATCH v3 1/2] dt-bindings: hwmon: Add starfive,jhb100-fan-tach Changhuang Liang
2026-08-24 3:25 ` sashiko-bot
2026-08-24 3:02 ` [PATCH v3 2/2] hwmon: (starfive-fan-tach) Add fan tach driver for StarFive JHB100 Changhuang Liang
2026-08-24 3:27 ` sashiko-bot
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=20260824030234.9321-1-changhuang.liang@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@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