Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zaixiang Xu" <zaixiang.xu.dev@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v6 4/4] hwmon: (sht3x) Add support for GXCAS GXHT30
Date: Tue, 28 Apr 2026 22:16:27 +0000	[thread overview]
Message-ID: <20260428221628.B8E7DC2BCAF@smtp.kernel.org> (raw)
In-Reply-To: <1777374569-59233-5-git-send-email-zaixiang.xu.dev@gmail.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] Redundant compatible string in the OF match table.
- [Low] Missing update to subsystem documentation (`Documentation/hwmon/sht3x.rst`).
- [Low] Missing Kconfig help text update.
--

commit 907d39a1530eacc8aee2b5e489cdd9c94b10ce78
Author: Zaixiang Xu <zaixiang.xu.dev@gmail.com>

hwmon: (sht3x) Add support for GXCAS GXHT30

This commit adds support for the GXCAS GXHT30 humidity and temperature sensor.
The GXHT30 is described as being software compatible with the Sensirion SHT30.

> diff --git a/drivers/hwmon/sht3x.c b/drivers/hwmon/sht3x.c
> index 6437568aaf73..f52114c13edb 100644
> --- a/drivers/hwmon/sht3x.c
> +++ b/drivers/hwmon/sht3x.c
[ ... ]
> @@ -948,6 +949,7 @@ static const struct of_device_id sht3x_of_match[] = {
>  	{ .compatible = "sensirion,sts31", .data = (void *)(uintptr_t)sts3x },
>  	{ .compatible = "sensirion,sts32", .data = (void *)(uintptr_t)sts3x },
>  	{ .compatible = "sensirion,sts35", .data = (void *)(uintptr_t)sts3x },
> +	{ .compatible = "gxcas,gxht30", .data = (void *)(uintptr_t)sht3x },

Is this explicit compatible string entry necessary in the driver?

The device tree binding for the GXHT30 enforces using sensirion,sht30 as a
fallback compatible string. Since the device tree node will provide
sensirion,sht30 in its compatible list, and the driver already matches
sensirion,sht30 using the same sht3x driver data, the fallback should handle
the matching automatically without needing an explicit entry here.

This isn't a bug, but should the documentation and Kconfig be updated for the
new chip?

The patch adds a new hardware chip but doesn't update the supported chips
section in Documentation/hwmon/sht3x.rst, or the help text for
CONFIG_SENSORS_SHT3x in drivers/hwmon/Kconfig. Updating these is expected
when adding support for a new device to the hardware monitoring subsystem.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/1777374569-59233-1-git-send-email-zaixiang.xu.dev@gmail.com?part=4

  reply	other threads:[~2026-04-28 22:16 UTC|newest]

Thread overview: 11+ 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 ` [PATCH v6 2/4] dt-bindings: hwmon: Add Sensirion SHT30 series Zaixiang Xu
2026-04-28 21:52   ` sashiko-bot
2026-04-29  6:27   ` Krzysztof Kozlowski
2026-04-29  6:28   ` Krzysztof Kozlowski
2026-04-28 11:09 ` [PATCH v6 3/4] hwmon: (sht3x) Add devicetree support Zaixiang Xu
2026-04-28 22:09   ` sashiko-bot
2026-04-28 11:09 ` [PATCH v6 4/4] hwmon: (sht3x) Add support for GXCAS GXHT30 Zaixiang Xu
2026-04-28 22:16   ` sashiko-bot [this message]
2026-04-29  6:29   ` Krzysztof Kozlowski

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=20260428221628.B8E7DC2BCAF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko@lists.linux.dev \
    --cc=zaixiang.xu.dev@gmail.com \
    /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