public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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 v5 0/3] hwmon: (sht3x) Add support for GXCAS GXHT30
Date: Fri,  3 Apr 2026 18:14:53 +0800	[thread overview]
Message-ID: <1775211296-63722-1-git-send-email-zaixiang.xu.dev@gmail.com> (raw)

Hi all,

First, I sincerely apologize for the noise in v3 and v4. I unfortunately 
missed the crucial feedback provided in v1 by Krzysztof, Conor, 
and Guenter. 

In this v5, I have completely dropped the incorrect approaches from the 
previous versions and completely refactored the patchset to strictly 
follow the maintainers' guidelines:

1. Wildcards are entirely avoided. Explicit chip names are used.
2. The standalone YAML binding has been dropped. The devices are 
   now added to trivial-devices.yaml.
3. The redundant of_match_table addition in the driver is dropped.
   The driver now relies on the I2C core's fallback matching mechanism.

Patch 1 adds the vendor prefix for GXCAS (Carries Conor's Acked-by 
from v1).
Patch 2 adds the explicit SHT3x/STS3x and GXHT30 models to 
trivial-devices.yaml.
Patch 3 adds minimal I2C ID support to the sht3x driver.

---
Changelog:

v5:
  - Dropped the standalone YAML binding file.
  - Added explicit chip models (sht30, sht31, sht35, sht85, sts30, 
    sts31, gxht30) to trivial-devices.yaml to avoid wildcards.
  - Dropped the of_match_table addition in sht3x.c.
  - Wrapped all commit messages to 72 characters.
  - Added company website to the vendor prefix commit message.

v3 & v4:
  - (Incorrectly) Proceeded with the standalone YAML file.
  - (Incorrectly) Added of_match_table with wildcards to the driver.

v2:
  - Fix placeholder "Your Name" in MODULE_AUTHOR.

v1:
  - Initial submission.

Zaixiang Xu (3):
  dt-bindings: vendor-prefixes: Add GXCAS Technology
  dt-bindings: trivial-devices: add Sensirion SHT3x/STS3x and GXCAS
    GXHT30
  hwmon: (sht3x) Add support for GXCAS GXHT30 sensor

 Documentation/devicetree/bindings/trivial-devices.yaml | 9 +++++++++
 Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
 drivers/hwmon/sht3x.c                                  | 2 ++
 3 files changed, 13 insertions(+)

-- 
2.34.1


             reply	other threads:[~2026-04-03 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 10:14 Zaixiang Xu [this message]
2026-04-03 10:14 ` [PATCH v5 1/3] dt-bindings: vendor-prefixes: Add GXCAS Technology Zaixiang Xu
2026-04-03 10:14 ` [PATCH v5 2/3] dt-bindings: trivial-devices: add Sensirion SHT3x/STS3x and GXCAS GXHT30 Zaixiang Xu
2026-04-03 10:14 ` [PATCH v5 3/3] hwmon: (sht3x) Add support for GXCAS GXHT30 sensor 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=1775211296-63722-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