Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Zaixiang Xu" <zaixiang.xu.dev@gmail.com>
Cc: linux-hwmon@vger.kernel.org, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 2/4] dt-bindings: hwmon: Add Sensirion SHT30 series
Date: Mon, 13 Jul 2026 07:55:12 +0000	[thread overview]
Message-ID: <20260713075512.A3BC21F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260713074559.12196-3-zaixiang.xu.dev@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Device tree nodes using the newly defined compatible strings will silently fail to probe because the existing `sht3x` driver lacks a corresponding `of_match_table`.
--

--- Patch [2]: [PATCH v7 2/4] dt-bindings: hwmon: Add Sensirion SHT30 series ---
commit a41d5511b126bf5d822219f86d5fe60736eb2e81
Author: Zaixiang Xu <zaixiang.xu.dev@gmail.com>

dt-bindings: hwmon: Add Sensirion SHT30 series

Add a YAML devicetree binding for the Sensirion SHT3x/STS3x sensor
family and the compatible GXCAS GXHT30, with the ALERT interrupt,
nRESET GPIO and VDD supply as optional properties.

> diff --git a/Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml b/Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml
> new file mode 100644
> index 0000000000000..dee0252941c29
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/sensirion,sht30.yaml
[ ... ]
> +maintainers:
> +  - Zaixiang Xu <zaixiang.xu.dev@gmail.com>
> +
> +properties:
> +  compatible:
> +    oneOf:
> +      - enum:
> +          - sensirion,sht30
> +          - sensirion,sts30

[Severity: Medium]
Will devices using these newly defined compatible strings silently fail to probe?

Looking at the existing driver in drivers/hwmon/sht3x.c, it lacks an
of_match_table and relies on this legacy ID table:

static const struct i2c_device_id sht3x_ids[] = {
        { .name = "sht3x", .driver_data = sht3x },
        { .name = "sts3x", .driver_data = sts3x },
        { .name = "sht85", .driver_data = sht3x },
        { }
};

Because it relies on the I2C core extracting the compatible string to use as the
legacy matching name, it will fail to match against strings like "sht30",
"sts30", or "gxht30" from this new binding.

Does the driver need to be updated with an of_match_table to prevent this
regression?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260713074559.12196-1-zaixiang.xu.dev@gmail.com?part=2

  reply	other threads:[~2026-07-13  7:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  7:45 [PATCH v7 0/4] hwmon: (sht3x) Add support for GXCAS GXHT30 Zaixiang Xu
2026-07-13  7:45 ` [PATCH v7 1/4] dt-bindings: vendor-prefixes: Add GXCAS Technology Zaixiang Xu
2026-07-13  7:47   ` sashiko-bot
2026-07-13  7:45 ` [PATCH v7 2/4] dt-bindings: hwmon: Add Sensirion SHT30 series Zaixiang Xu
2026-07-13  7:55   ` sashiko-bot [this message]
2026-07-13  8:27     ` Zaixiang Xu
2026-07-13  7:45 ` [PATCH v7 3/4] hwmon: (sht3x) Add devicetree support Zaixiang Xu
2026-07-13  8:01   ` sashiko-bot
2026-07-13  8:28     ` Zaixiang Xu
2026-07-13  7:45 ` [PATCH v7 4/4] hwmon: (sht3x) Document support for GXCAS GXHT30 Zaixiang Xu
2026-07-13  7:48   ` 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=20260713075512.A3BC21F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@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