From: sashiko-bot@kernel.org
To: "Ross Cawston" <ross@r-sc.ca>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org, lee@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: leds: add Realtek RTL9301 port LEDs
Date: Mon, 19 Oct 2026 20:04:55 +0000 [thread overview]
Message-ID: <sashiko-outbox-178158@kernel.org> (raw)
In-Reply-To: <20261018194339.132-2-ross@r-sc.ca>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: leds: rtl9301-port-leds example uses raw function string
--
commit c5aa8893c90e31ee15e18fbf27c8f17550a77f2f
Author: Ross Cawston <ross@r-sc.ca>
dt-bindings: leds: add Realtek RTL9301 port LEDs
This commit adds a devicetree binding schema for Realtek RTL9300 switch
port LEDs controlled by software.
> diff --git a/Documentation/devicetree/bindings/leds/realtek,rtl9301-port-leds.yaml b/Documentation/devicetree/bindings/leds/realtek,rtl9301-port-leds.yaml
> new file mode 100644
> index 0000000000000..8d6b35525263f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/realtek,rtl9301-port-leds.yaml
> @@ -0,0 +1,84 @@
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + led-controller@cc48 {
> + compatible = "realtek,rtl9301-port-leds";
> + reg = <0xcc48 0x84>;
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + led@0,2 {
> + reg = <0 2>;
> + color = <LED_COLOR_ID_GREEN>;
> + function = "poe";
> + function-enumerator = <1>;
> + };
> +
> + led@8,2 {
> + reg = <8 2>;
> + color = <LED_COLOR_ID_GREEN>;
> + function = "poe";
> + function-enumerator = <2>;
> + };
> + };
[Severity: Low]
In Documentation/devicetree/bindings/leds/realtek,rtl9301-port-leds.yaml,
the ^led@[0-9a-f]+,[0-3]$ child nodes reference /schemas/leds/common.yaml#,
where properties:function states:
function:
description:
LED function. Use one of the LED_FUNCTION_* prefixed definitions
from the header include/dt-bindings/leds/common.h. If there is no
matching LED_FUNCTION available, add a new one.
Should the example use a LED_FUNCTION_* macro from
include/dt-bindings/leds/common.h (or define LED_FUNCTION_POE there)
instead of the raw string literal "poe"?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018194339.132-1-ross@r-sc.ca?part=1
next prev parent reply other threads:[~2026-10-19 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 19:43 [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control Ross Cawston
2026-10-18 19:43 ` [PATCH 1/3] dt-bindings: leds: add Realtek RTL9301 port LEDs Ross Cawston
2026-10-19 20:04 ` sashiko-bot [this message]
2026-10-18 19:43 ` [PATCH 2/3] dt-bindings: net: realtek,rtl9301-switch: add port LED controller Ross Cawston
2026-10-19 20:04 ` sashiko-bot
2026-10-20 7:29 ` Krzysztof Kozlowski
2026-10-18 19:43 ` [PATCH 3/3] leds: add Realtek RTL9300 port LED driver Ross Cawston
2026-10-19 7:01 ` Uwe Kleine-König
2026-10-19 20:04 ` sashiko-bot
2026-10-18 22:36 ` [PATCH 0/3] leds: add Realtek RTL9300 port LEDs under software control Andrew Lunn
2026-10-18 23:20 ` Ross Cawston
2026-10-19 0:02 ` Andrew Lunn
2026-10-19 5:42 ` Ross Cawston
2026-10-19 6:41 ` AW: " Markus Stockhausen
2026-10-19 23:00 ` Ross Cawston
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-178158@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ross@r-sc.ca \
--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