From: sashiko-bot@kernel.org
To: "Adrian Ambrozewicz" <aambrozewicz@nvidia.com>
Cc: conor+dt@kernel.org, linux-usb@vger.kernel.org, robh@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 02/11] dt-bindings: i2c: Add NVIDIA LSTP I2C
Date: Mon, 12 Oct 2026 17:41:34 +0000 [thread overview]
Message-ID: <sashiko-outbox-168478@kernel.org> (raw)
In-Reply-To: <20261012-lstp-usb-adapter-v1-2-aambrozewicz@nvidia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: incomplete schema validation allows unsupported clock-frequency property
--
commit 16ee132f4b8daa2cd636b3b3437f38ceb664442e
Author: Adrian Ambrozewicz <aambrozewicz@nvidia.com>
dt-bindings: i2c: Add NVIDIA LSTP I2C
This commit adds a device tree binding for the I2C controller channel on an
NVIDIA LSTP USB device. It includes configurations for the compatible string,
register ID, and a custom property for arbitration retries. The documentation
notes that the device sets the bus speed, so clock-frequency is unsupported.
> diff --git a/Documentation/devicetree/bindings/i2c/nvidia,lstp-i2c.yaml b/Documentation/devicetree/bindings/i2c/nvidia,lstp-i2c.yaml
> new file mode 100644
> index 0000000000000..eacabed52cd1c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/nvidia,lstp-i2c.yaml
> @@ -0,0 +1,71 @@
[ ... ]
> +description: |
> + I2C controller channel on an NVIDIA LSTP USB device.
> +
> + Peripherals on the bus are described as child nodes. An i2c alias
> + gives the bus a fixed number.
> +
> + The bus speed is set by the device. The LSTP protocol has no way to
> + change it, so clock-frequency is not supported and is ignored.
> +
> +allOf:
> + - $ref: /schemas/i2c/i2c-controller.yaml#
> +
> +properties:
> + compatible:
> + const: nvidia,lstp-i2c
[Severity: Low]
Since this schema inherits from /schemas/i2c/i2c-controller.yaml# which
evaluates and permits the standard clock-frequency property, should
clock-frequency: false be explicitly defined in this properties block?
Because the property is evaluated by the $ref, the unevaluatedProperties:
false directive at the bottom of the schema does not reject it. Device
trees that incorrectly specify clock-frequency for this controller will
silently pass schema validation, despite the binding's documentation stating
it is not supported.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261012-lstp-usb-adapter-v1-0-aambrozewicz@nvidia.com?part=2
next prev parent reply other threads:[~2026-10-12 17:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 17:35 [PATCH 00/11] Add NVIDIA LSTP USB adapter drivers Adrian Ambrozewicz
2026-10-12 17:35 ` [PATCH 01/11] dt-bindings: gpio: Add NVIDIA LSTP GPIO Adrian Ambrozewicz
2026-10-12 17:43 ` sashiko-bot
2026-10-13 6:09 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 02/11] dt-bindings: i2c: Add NVIDIA LSTP I2C Adrian Ambrozewicz
2026-10-12 17:41 ` sashiko-bot [this message]
2026-10-13 6:11 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 03/11] dt-bindings: spi: Add NVIDIA LSTP SPI Adrian Ambrozewicz
2026-10-12 17:46 ` sashiko-bot
2026-10-13 6:11 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 04/11] dt-bindings: usb: Add NVIDIA LSTP USB adapter Adrian Ambrozewicz
2026-10-12 17:47 ` sashiko-bot
2026-10-13 6:13 ` Krzysztof Kozlowski
2026-10-13 6:17 ` Krzysztof Kozlowski
2026-10-13 11:37 ` [PATCH 00/11] Add NVIDIA LSTP USB adapter drivers Greg Kroah-Hartman
2026-10-13 11:39 ` Greg Kroah-Hartman
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=sashiko-outbox-168478@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=aambrozewicz@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-usb@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