From: Zaixiang Xu <zaixiang.xu.dev@gmail.com>
To: linux@roeck-us.net
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, zaixiang.xu.dev@gmail.com
Subject: [PATCH v4 0/4] hwmon: (sht3x) Add support for GXCAS GXHT30
Date: Wed, 25 Mar 2026 17:08:06 +0800 [thread overview]
Message-ID: <1774429690-129139-1-git-send-email-zaixiang.xu.dev@gmail.com> (raw)
This series adds support for the GXCAS GXHT30 humidity and temperature
sensor. The GXHT30 is software compatible with the Sensirion SHT30 series.
This series also introduces the missing YAML binding schema for the
Sensirion SHT30 family, replacing wildcards with specific model names.
Changes in v4:
- Use match data (.data) to correctly distinguish between SHT (humidity/
temperature) and STS (temperature-only) sensors in the driver, fixing
a logic error where STS sensors would report bogus humidity
(suggested by Guenter Roeck and AI review).
- Update YAML bindings to use fallback compatibles for compatible chips
and add optional 'interrupts' and 'vdd-supply' properties
(suggested by Guenter Roeck and AI review).
- Simplified of_match_table to only include base models due to the
newly added fallback mechanism.
- Renamed binding file from sensirion,sht3x.yaml to sensirion,sht30.yaml.
- Include Conor's Acked-by for the vendor-prefix patch.
Changes in v3:
- Split driver changes into two patches: one for DT framework and one
for adding GXHT30 (suggested by Guenter Roeck).
- Fixed commit message line lengths (suggested by Guenter Roeck).
- Removed wildcards 'x' from compatibles and used specific model names
(suggested by Conor Dooley).
- Added manufacturer website to vendor-prefix patch (suggested by Conor Dooley).
- Fixed missing newline at end of YAML file (reported by kernel test robot).
Changes in v2:
- Fix placeholder "Your Name" in MODULE_AUTHOR.
Zaixiang Xu (4):
dt-bindings: vendor-prefixes: Add GXCAS Technology
dt-bindings: hwmon: Add Sensirion SHT30 series
hwmon: (sht3x) Add devicetree support
hwmon: (sht3x) Add support for GXCAS GXHT30
.../bindings/hwmon/sensirion,sht30.yaml | 50 +++++++++++++++++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
drivers/hwmon/sht3x.c | 16 +++++-
3 files changed, 67 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml
--
2.34.1
next reply other threads:[~2026-03-25 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:08 Zaixiang Xu [this message]
2026-03-25 9:08 ` [PATCH v4 1/4] dt-bindings: vendor-prefixes: Add GXCAS Technology Zaixiang Xu
2026-03-25 9:08 ` [PATCH v4 2/4] dt-bindings: hwmon: Add Sensirion SHT30 series Zaixiang Xu
2026-03-25 18:20 ` Conor Dooley
2026-03-26 1:05 ` Guenter Roeck
2026-03-26 17:42 ` Conor Dooley
2026-03-26 17:45 ` Conor Dooley
2026-03-26 23:55 ` Guenter Roeck
2026-03-27 0:03 ` Conor Dooley
2026-03-27 0:46 ` Roman Gushchin
2026-03-25 9:08 ` [PATCH v4 3/4] hwmon: (sht3x) Add devicetree support Zaixiang Xu
2026-03-25 9:08 ` [PATCH v4 4/4] hwmon: (sht3x) Add support for GXCAS GXHT30 Zaixiang Xu
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=1774429690-129139-1-git-send-email-zaixiang.xu.dev@gmail.com \
--to=zaixiang.xu.dev@gmail.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