From: Fabio Estevam <festevam@gmail.com>
To: heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@nabladev.com>
Subject: [PATCH] ARM: dts: rockchip: Fix LED node names on rk3288-phycore-rdk
Date: Wed, 11 Mar 2026 10:56:04 -0300 [thread overview]
Message-ID: <20260311135604.21634-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@nabladev.com>
According to nxp,pca953x.yaml, the pattern for the led names should be:
"^led-[0-9a-z]+$".
Change it accordingly to fix the following dt-schema warning"
leddimmer@62 (nxp,pca9533): 'led1', 'led2', 'led3', 'led4' do not match any
of the regexes: '^led-[0-9a-z]+$', '^pinctrl-[0-9]+$'
Signed-off-by: Fabio Estevam <festevam@nabladev.com>
---
arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts b/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts
index d411fd9811fd..46362e804daf 100644
--- a/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts
+++ b/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts
@@ -125,25 +125,25 @@ leddim: leddimmer@62 {
compatible = "nxp,pca9533";
reg = <0x62>;
- led1 {
+ led-1 {
label = "red:user1";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
};
- led2 {
+ led-2 {
label = "green:user2";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
};
- led3 {
+ led-3 {
label = "blue:user3";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
};
- led4 {
+ led-4 {
label = "red:user4";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
--
2.43.0
WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@nabladev.com>
Subject: [PATCH] ARM: dts: rockchip: Fix LED node names on rk3288-phycore-rdk
Date: Wed, 11 Mar 2026 10:56:04 -0300 [thread overview]
Message-ID: <20260311135604.21634-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@nabladev.com>
According to nxp,pca953x.yaml, the pattern for the led names should be:
"^led-[0-9a-z]+$".
Change it accordingly to fix the following dt-schema warning"
leddimmer@62 (nxp,pca9533): 'led1', 'led2', 'led3', 'led4' do not match any
of the regexes: '^led-[0-9a-z]+$', '^pinctrl-[0-9]+$'
Signed-off-by: Fabio Estevam <festevam@nabladev.com>
---
arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts b/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts
index d411fd9811fd..46362e804daf 100644
--- a/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts
+++ b/arch/arm/boot/dts/rockchip/rk3288-phycore-rdk.dts
@@ -125,25 +125,25 @@ leddim: leddimmer@62 {
compatible = "nxp,pca9533";
reg = <0x62>;
- led1 {
+ led-1 {
label = "red:user1";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
};
- led2 {
+ led-2 {
label = "green:user2";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
};
- led3 {
+ led-3 {
label = "blue:user3";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
};
- led4 {
+ led-4 {
label = "red:user4";
linux,default-trigger = "none";
type = <PCA9532_TYPE_LED>;
--
2.43.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2026-03-11 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 13:56 Fabio Estevam [this message]
2026-03-11 13:56 ` [PATCH] ARM: dts: rockchip: Fix LED node names on rk3288-phycore-rdk Fabio Estevam
2026-03-12 20:00 ` Heiko Stuebner
2026-03-12 20:00 ` Heiko Stuebner
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=20260311135604.21634-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@nabladev.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.