From: sashiko-bot@kernel.org
To: "Andy Chung" <Andy.Chung@amd.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: hwmon: Add Kandou KB9002
Date: Wed, 15 Jul 2026 09:16:36 +0000 [thread overview]
Message-ID: <20260715091637.6DE0F1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260715-kb9002-upstream-v2-2-2fd390383da5@amd.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The `reg` property is missing the `maxItems: 1` constraint and incorrectly applies `minimum` and `maximum` constraints directly to the array instance.
- [Low] The device tree binding for a PCIe retimer is incorrectly placed in the hwmon/ directory.
--
--- Patch [2]: [PATCH v2 2/4] dt-bindings: hwmon: Add Kandou KB9002 ---
commit e4c6f2bbc23572a071a648919c1c0c0e4520ad76
Author: Andy Chung <Andy.Chung@amd.com>
dt-bindings: hwmon: Add Kandou KB9002
Add device tree bindings for the Kandou KB9002 PCIe 5.0 retimer, an
SMBus target that exposes an aggregated die temperature.
> diff --git a/Documentation/devicetree/bindings/hwmon/kandou,kb9002.yaml b/Documentation/devicetree/bindings/hwmon/kandou,kb9002.yaml
> new file mode 100644
> index 0000000000000..67859e9d63c25
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/kandou,kb9002.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/hwmon/kandou,kb9002.yaml#
[Severity: Low]
Does this binding belong in the hwmon directory? Since this device is
primarily an 8-lane PCIe 5.0 retimer rather than a dedicated hardware
monitor, it seems like the binding should be placed in a physical
category directory like phy/ or pci/ instead.
[ ... ]
> +properties:
> + compatible:
> + const: kandou,kb9002
> +
> + reg:
> + minimum: 0x20
> + maximum: 0x27
[Severity: Medium]
Can this correctly constrain the I2C address? The reg property evaluates
as an array, so omitting maxItems: 1 allows multiple addresses to pass
validation.
Furthermore, applying numeric constraints directly to the array rather
than its items causes them to be silently ignored by the validator,
allowing out-of-range addresses to pass.
> +
> +required:
> + - compatible
> + - reg
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715-kb9002-upstream-v2-0-2fd390383da5@amd.com?part=2
next prev parent reply other threads:[~2026-07-15 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 9:08 [PATCH v2 0/4] hwmon: Add Kandou KB9002 PCIe retimer driver Andy Chung via B4 Relay
2026-07-15 9:08 ` [PATCH v2 1/4] dt-bindings: Add vendor prefix for Kandou Andy Chung via B4 Relay
2026-07-15 9:10 ` sashiko-bot
2026-07-15 9:08 ` [PATCH v2 2/4] dt-bindings: hwmon: Add Kandou KB9002 Andy Chung via B4 Relay
2026-07-15 9:16 ` sashiko-bot [this message]
2026-07-15 9:08 ` [PATCH v2 3/4] hwmon: (kb9002) Add driver for Kandou KB9002 retimer Andy Chung via B4 Relay
2026-07-15 9:17 ` sashiko-bot
2026-07-15 9:08 ` [PATCH v2 4/4] hwmon: (kb9002) Add documentation Andy Chung via B4 Relay
2026-07-15 9:19 ` 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=20260715091637.6DE0F1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Andy.Chung@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