Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Colin Huang" <colin.huang2@amd.com>
Cc: linux-hwmon@vger.kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: pmbus: Add Infineon tda38740 and tda38725
Date: Mon, 07 Sep 2026 03:33:09 +0000	[thread overview]
Message-ID: <20260907033309.BA1D31F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907-add-tda38740-and-tda38725-v1-1-e2db1b2566b1@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The `$id` and `$schema` properties use the `https://` protocol instead of the required `http://` prefix.
- [Low] The mandatory `maintainers` property is missing from the top-level schema.
--

commit 394e1f6fb8099cdca94075856e1923221cb81dae
Author: Colin Huang <u8813345@gmail.com>

dt-bindings: hwmon: pmbus: Add Infineon tda38740 and tda38725

This commit adds devicetree bindings for the Infineon TDA38740 and
TDA38725 synchronous buck regulators. The hardware uses a PMBus interface
and the binding documents custom properties such as vout scaling.

> diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/infineon,tda38740.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,tda38740.yaml
> new file mode 100644
> index 0000000000000..02380c09c5f55
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,tda38740.yaml
> @@ -0,0 +1,79 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +
> +$id: https://devicetree.org/schemas/hwmon/pmbus/infineon,tda38740.yaml#
> +$schema: https://devicetree.org/meta-schemas/core.yaml#

[Severity: Medium]
Does using the https:// protocol instead of http:// for the $id and $schema
fields break the schema cross-reference system? Modern dt-schema validation
tools rely on exact string matches for these URIs, and an incorrect prefix
might cause dt_binding_check to report misleading errors or silently skip
validation.

> +
> +title: Infineon TDA38740 and TDA38725 PMBus Synchronous Buck Regulator

[Severity: Low]
Is the mandatory maintainers property missing from the top-level schema?
Device tree schema files validated against core.yaml are required to specify
a maintainers array (typically right after the title or description), and
omitting it will likely cause dt_binding_check to report a validation
failure.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260907-add-tda38740-and-tda38725-v1-0-e2db1b2566b1@gmail.com?part=1

  reply	other threads:[~2026-09-07  3:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  3:28 [PATCH 0/2] Add driver for Infineon TDA38740/TDA38725 Colin Huang
2026-09-07  3:28 ` [PATCH 1/2] dt-bindings: hwmon: pmbus: Add Infineon tda38740 and tda38725 Colin Huang
2026-09-07  3:33   ` sashiko-bot [this message]
2026-09-07  3:28 ` [PATCH 2/2] hwmon: (pmbus/tda38740) Add driver for Infineon TDA38740/TDA38725 Colin Huang
2026-09-07  3:34   ` 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=20260907033309.BA1D31F00A3A@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