From: sashiko-bot@kernel.org
To: "Ninad Naik" <ninadnaik07@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2] dt-bindings: leds: bcm6358: Convert to DT schema
Date: Tue, 09 Jun 2026 18:42:35 +0000 [thread overview]
Message-ID: <20260609184236.335711F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260609181731.1379846-1-ninadnaik07@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The LED sub-node uses `additionalProperties: false` alongside `$ref: common.yaml#`, which silently rejects standard LED properties.
- [Low] Unused `#include <dt-bindings/leds/common.h>` in the device tree example.
--
commit 7f21f3b199b43205368512a4bc4314dd320036e1
Author: Ninad Naik <ninadnaik07@gmail.com>
dt-bindings: leds: bcm6358: Convert to DT schema
This commit converts the text bindings for the Broadcom BCM6358 LED
controller to DT schema.
> diff --git a/Documentation/devicetree/bindings/leds/brcm,bcm6358-leds.yaml b/Documentation/devicetree/bindings/leds/brcm,bcm6358-leds.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/brcm,bcm6358-leds.yaml
[ ... ]
> +patternProperties:
> + "^led@(0|1?[0-9a-f])$":
> + type: object
> + $ref: common.yaml#
> + description: Each LED is represented as a sub-node of
> + this device.
> +
> + properties:
> + reg:
> + description: LED pin number (0 to 31).
> + maxItems: 1
> +
> + label: true
> +
> + default-state: true
> +
> + linux,default-trigger: true
> +
> + active-low: true
> +
> + required:
> + - reg
> +
> + additionalProperties: false
[Severity: Medium]
Does this restrict the child node to only locally declared properties,
rejecting the standard LED properties inherited from common.yaml#?
In DT schemas, additionalProperties does not consider properties evaluated
via a $ref. Could this cause validation errors if standard LED properties
are used in the device tree? Should unevaluatedProperties: false be used
here instead?
> +
> +required:
> + - compatible
> + - reg
> + - "#address-cells"
> + - "#size-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
[Severity: Low]
This isn't a bug, but the header is included here without any of its macros
being referenced in the example nodes.
> + led-controller@fffe00d0 {
> + compatible = "brcm,bcm6358-leds";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0xfffe00d0 0x8>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609181731.1379846-1-ninadnaik07@gmail.com?part=1
prev parent reply other threads:[~2026-06-09 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 18:17 [PATCH v2] dt-bindings: leds: bcm6358: Convert to DT schema Ninad Naik
2026-06-09 18:42 ` sashiko-bot [this message]
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=20260609184236.335711F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ninadnaik07@gmail.com \
--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