From: sashiko-bot@kernel.org
To: "Vincent Jardin" <vjardin@free.fr>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH] dt-bindings: hwmon: ti,tmp401: add vcc-supply and #thermal-sensor-cells
Date: Mon, 24 Aug 2026 15:57:58 +0000 [thread overview]
Message-ID: <20260824155758.CD2F11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260824-for-upstream-dt-tmp401-vcc-tsc-v1-1-ecb5ef7898bd@free.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message contains a major factual error: it justifies adding the `vcc-supply` property by claiming it is fetched by `lm90_probe()` in `drivers/hwmon/lm90.c`, but the `ti,tmp401` and `ti,tmp411` devices are actually backed by `drivers/hwmon/tmp401.c`, which completely lacks regulator support.
--
--- Patch [1]: [PATCH] dt-bindings: hwmon: ti,tmp401: add vcc-supply and #thermal-sensor-cells ---
commit bb8183d96c519f5d3050a2f78596d89eca815884
Author: Vincent Jardin <vjardin@free.fr>
dt-bindings: hwmon: ti,tmp401: add vcc-supply and #thermal-sensor-cells
This commit updates the ti,tmp401 device tree binding to include the
vcc-supply and #thermal-sensor-cells properties. It aims to fix
dtbs_check warnings for boards that describe these features.
> vcc-supply is fetched in lm90_probe():
>
> drivers/hwmon/lm90.c:2777
> err = devm_regulator_get_enable(dev, "vcc");
>
> so a board with the sensor behind a switched rail has no other way to
> describe it, and omitting it means the chip is probed with its supply
> possibly off.
[Severity: Medium]
Is this justification accurate for the ti,tmp401 binding?
The ti,tmp401 and ti,tmp411 devices appear to be backed by the driver
in drivers/hwmon/tmp401.c, rather than lm90.c.
Looking at tmp401_probe(), it currently lacks regulator support and does
not call devm_regulator_get_enable(). Does this mean boards using the
tmp401 sensor with a switched rail will still fail to power up the chip
since the driver ignores the property?
> diff --git a/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml b/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
> index 0e8ddf0ad7890..69f77aec01a33 100644
> --- a/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
[ ... ]
> @@ -50,6 +50,11 @@ properties:
> minimum: 0
> maximum: 15
>
> + vcc-supply: true
[Severity: Medium]
While adding this property correctly describes the hardware and silences the
dtbs_check warnings, should the drivers/hwmon/tmp401.c driver also be
updated in a companion patch so it actually parses and enables this supply?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260824-for-upstream-dt-tmp401-vcc-tsc-v1-1-ecb5ef7898bd@free.fr?part=1
next prev parent reply other threads:[~2026-08-24 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 15:46 [PATCH] dt-bindings: hwmon: ti,tmp401: add vcc-supply and #thermal-sensor-cells Vincent Jardin via B4 Relay
2026-08-24 15:46 ` Vincent Jardin
2026-08-24 15:57 ` sashiko-bot [this message]
2026-08-24 22:09 ` Vincent Jardin
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=20260824155758.CD2F11F000E9@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=vjardin@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.