From: sashiko-bot@kernel.org
To: "Colin Huang" <colin.huang2@amd.com>
Cc: linux-hwmon@vger.kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: hwmon: pmbus: Add Infineon tda38740 and tda38725
Date: Thu, 10 Sep 2026 12:41:33 +0000 [thread overview]
Message-ID: <20260910124134.1299D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910-add-tda38740-and-tda38725-v4-1-dbae7fabce09@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding omits standard properties for voltage regulators and PMBus alerts, preventing complete hardware description due to `additionalProperties: false`.
--
commit ad3970039034a68048f73bbed304c8a0650c3bdf
Author: Colin Huang <u8813345@gmail.com>
dt-bindings: hwmon: pmbus: Add Infineon tda38740 and tda38725
This commit adds device tree binding documentation for the Infineon
TDA38740 and TDA38725 PMBus synchronous buck regulators.
> diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/infineon,tda38740.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,tda38740.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,tda38740.yaml
[ ... ]
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
[Severity: Medium]
Because this is a voltage regulator with a PMBus interface, board device
trees might need to describe physical hardware connections like the SMBALERT#
interrupt pin or standard regulator supply nodes.
Will this strict constraint cause dt-schema validation failures if a board
node attempts to add standard properties like interrupts?
Should this schema include standard regulator and interrupt properties in
the definition, or perhaps use unevaluatedProperties with the relevant
$ref inclusions, to allow boards to completely describe their hardware
without validation errors?
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260910-add-tda38740-and-tda38725-v4-0-dbae7fabce09@gmail.com?part=1
next prev parent reply other threads:[~2026-09-10 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 12:35 [PATCH v4 0/2] Add driver for Infineon TDA38740/TDA38725 Colin Huang
2026-09-10 12:35 ` [PATCH v4 1/2] dt-bindings: hwmon: pmbus: Add Infineon tda38740 and tda38725 Colin Huang
2026-09-10 12:41 ` sashiko-bot [this message]
2026-09-11 8:49 ` Krzysztof Kozlowski
2026-09-10 12:35 ` [PATCH v4 2/2] hwmon: (pmbus/tda38740) Add driver for Infineon TDA38740/TDA38725 Colin Huang
2026-09-10 12:42 ` sashiko-bot
2026-09-10 15:19 ` Guenter Roeck
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=20260910124134.1299D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=colin.huang2@amd.com \
--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 \
/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