From: sashiko-bot@kernel.org
To: "Loic Poulain" <loic.poulain@oss.qualcomm.com>
Cc: linux-leds@vger.kernel.org, lee@kernel.org, robh@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 4/4] arm64: dts: monaco-arduino-monza: microcontroller LEDs
Date: Fri, 10 Jul 2026 14:14:44 +0000 [thread overview]
Message-ID: <20260710141444.C255C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260710-monza-leds-v5-4-a8972d28c28f@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Use of deprecated `label` property in new LED device tree nodes
--
--- Patch [4]: [PATCH v5 4/4] arm64: dts: monaco-arduino-monza: microcontroller LEDs ---
commit 2e709948eba4cbeeb0ee03878eb97fe42c4fdd87
Author: Loic Poulain <loic.poulain@oss.qualcomm.com>
arm64: dts: monaco-arduino-monza: microcontroller LEDs
This commit adds onboard MCU/STM32 microcontroller LED definitions to the
monaco-arduino-monza device tree. It configures a PCA9635-compatible LED
controller with four RGB LEDs.
> diff --git a/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts b/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts
> index 379b796f261f4..83ccc4eec3423 100644
> --- a/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts
> +++ b/arch/arm64/boot/dts/qcom/monaco-arduino-monza.dts
[ ... ]
> @@ -156,6 +157,115 @@ vreg_nvme: regulator-3p3-m2 {
[ ... ]
> +&cci1_i2c1 {
> + led-controller@22 {
> + compatible = "nxp,pca9635";
[ ... ]
> + multi-led@0 {
> + reg = <0>;
> + label = "stm-led-1";
[Severity: Medium]
Are these label properties necessary?
Since color and function are already defined just below this line, adding the
deprecated label property overrides the standard naming conventions. This
creates sysfs directories like /sys/class/leds/stm-led-1 instead of the
standard color:function format expected by modern user-space LED managers.
Would it be better to omit the label property here and in the multi-led@1,
multi-led@2, and multi-led@3 nodes?
> + color = <LED_COLOR_ID_RGB>;
> + function = LED_FUNCTION_STATUS;
> + #address-cells = <1>;
> + #size-cells = <0>;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260710-monza-leds-v5-0-a8972d28c28f@oss.qualcomm.com?part=4
prev parent reply other threads:[~2026-07-10 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 13:49 [PATCH v5 0/4] leds: pca963x: Add multicolor support and enable Monza RGB LEDs Loic Poulain
2026-07-10 13:49 ` [PATCH v5 1/4] dt-bindings: leds: nxp,pca963x: fix reg maximum for pca9635 Loic Poulain
2026-07-10 13:54 ` sashiko-bot
2026-07-10 13:49 ` [PATCH v5 2/4] dt-bindings: leds: nxp,pca963x: add multicolor LED support Loic Poulain
2026-07-10 13:59 ` sashiko-bot
2026-07-10 13:49 ` [PATCH v5 3/4] leds: pca963x: add multicolor LED class support Loic Poulain
2026-07-10 14:10 ` sashiko-bot
2026-07-10 13:49 ` [PATCH v5 4/4] arm64: dts: monaco-arduino-monza: microcontroller LEDs Loic Poulain
2026-07-10 14:14 ` 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=20260710141444.C255C1F000E9@smtp.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=loic.poulain@oss.qualcomm.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