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 v6 2/4] dt-bindings: hwmon: Add Sensirion SHT30 series
Date: Tue, 28 Apr 2026 19:09:27 +0800 [thread overview]
Message-ID: <1777374569-59233-3-git-send-email-zaixiang.xu.dev@gmail.com> (raw)
In-Reply-To: <1777374569-59233-1-git-send-email-zaixiang.xu.dev@gmail.com>
Add YAML devicetree binding schema for Sensirion SHT30 series and the
compatible GXCAS GXHT30 sensors.
Use fallback compatibles for compatible chips and add optional
interrupts and vdd-supply properties.
Signed-off-by: Zaixiang Xu <zaixiang.xu.dev@gmail.com>
---
.../bindings/hwmon/sensirion,sht30.yaml | 67 +++++++++++++++++++
1 file changed, 67 insertions(+)
create mode 100644 Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml
diff --git a/Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml b/Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml
new file mode 100644
index 000000000000..9b120f8d303c
--- /dev/null
+++ b/Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml
@@ -0,0 +1,67 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/hwmon/sensirion,sht30.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Sensirion SHT3x and GXCAS GXHT30 humidity and temperature sensors
+
+maintainers:
+ - Zaixiang Xu <zaixiang.xu.dev@gmail.com>
+
+properties:
+ compatible:
+ oneOf:
+ - enum:
+ - sensirion,sht30
+ - sensirion,sht31
+ - sensirion,sht35
+ - sensirion,sht85
+ - sensirion,sts30
+ - sensirion,sts31
+ - sensirion,sts32
+ - sensirion,sts35
+ - items:
+ - const: gxcas,gxht30
+ - const: sensirion,sht30
+
+ reg:
+ maxItems: 1
+
+ vdd-supply:
+ description: Regulator that provides power to the VDD pin.
+
+ reset-gpios:
+ maxItems: 1
+ description:
+ GPIO connected to the nRESET pin. Active low.
+
+ interrupts:
+ maxItems: 1
+ description:
+ Interrupt connected to the ALERT pin.
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ humidity-sensor@44 {
+ compatible = "gxcas,gxht30", "sensirion,sht30";
+ reg = <0x44>;
+ vdd-supply = <&vcc_3v3_reg>;
+ reset-gpios = <&gpio1 15 GPIO_ACTIVE_LOW>;
+ interrupt-parent = <&gpio1>;
+ interrupts = <16 IRQ_TYPE_LEVEL_HIGH>;
+ };
+ };
--
2.34.1
next prev parent reply other threads:[~2026-04-28 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 11:09 [PATCH v6 0/4] hwmon: (sht3x) Add support for GXCAS GXHT30 Zaixiang Xu
2026-04-28 11:09 ` [PATCH v6 1/4] dt-bindings: vendor-prefixes: Add GXCAS Technology Zaixiang Xu
2026-04-28 11:09 ` Zaixiang Xu [this message]
2026-04-28 11:09 ` [PATCH v6 3/4] hwmon: (sht3x) Add devicetree support Zaixiang Xu
2026-04-28 11:09 ` [PATCH v6 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=1777374569-59233-3-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