From: sashiko-bot@kernel.org
To: "ASHISH YADAV" <ashishyadav78@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon/pmbus: Add Infineon XDP730
Date: Tue, 19 May 2026 08:09:40 +0000 [thread overview]
Message-ID: <20260519080941.7E303C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519075558.91466-2-Ashish.Yadav@infineon.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The device tree example node is named `hwmon@11`, which uses a Linux-specific subsystem name instead of a generic hardware function name.
- [Low] The new device tree binding `infineon,xdp730.yaml` unnecessarily duplicates the schema of the existing `infineon,xdp720.yaml`.
--
commit e021e1d189da7e8470a3c273fdd6ec12f7ed6280
Author: Ashish Yadav <ashish.yadav@infineon.com>
dt-bindings: hwmon/pmbus: Add Infineon XDP730
Add documentation for the device tree binding of the XDP730 eFuse.
> diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
> new file mode 100644
> index 0000000000000..a7361a07891c2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/pmbus/infineon,xdp730.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +
> +$id: http://devicetree.org/schemas/hwmon/pmbus/infineon,xdp730.yaml#
Does this file needlessly duplicate the existing infineon,xdp720.yaml schema?
The properties, required fields, and constraints here appear identical
to infineon,xdp720.yaml. Creating duplicate YAML schema files for
devices in the same hardware family with identical constraints can
fragment the schemas.
Could the infineon,xdp730 compatible string be added to the enum in the
existing schema file instead?
[ ... ]
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + hwmon@11 {
This isn't a bug, but does this node name follow the Devicetree
specification for generic names?
The spec requires node names to reflect the hardware function
(like efuse@11 or sensor@11), rather than pointing to a specific
OS subsystem like hwmon.
> + compatible = "infineon,xdp730";
> + reg = <0x11>;
> + vdd-vin-supply = <&vdd_vin>;
> + infineon,rimon-micro-ohms = <1098000000>; /* 1.098k ohm */
> + };
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260519075558.91466-1-Ashish.Yadav@infineon.com?part=1
next prev parent reply other threads:[~2026-05-19 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:55 [PATCH 0/2] Add support for Infineon Digital eFuse XDP730 ASHISH YADAV
2026-05-19 7:55 ` [PATCH 1/2] dt-bindings: hwmon/pmbus: Add Infineon XDP730 ASHISH YADAV
2026-05-19 8:09 ` sashiko-bot [this message]
2026-05-19 7:55 ` [PATCH 2/2] hwmon:(pmbus/xdp730) Add support for efuse xdp730 ASHISH YADAV
2026-05-19 8:31 ` sashiko-bot
2026-05-19 15:29 ` [PATCH 0/2] Add support for Infineon Digital eFuse XDP730 Guenter Roeck
2026-05-20 6:40 ` ashish yadav
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=20260519080941.7E303C2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ashishyadav78@gmail.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