From: Daniel Palmer <daniel@0x0f.com>
To: krzk+dt@kernel.org, romain.perier@gmail.com, robh@kernel.org,
conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH v2 3/8] arm: dts: mstar: breadbee: Correct LED names
Date: Thu, 1 Jan 2026 12:43:01 +0900 [thread overview]
Message-ID: <20260101034306.1233091-4-daniel@0x0f.com> (raw)
In-Reply-To: <20260101034306.1233091-1-daniel@0x0f.com>
The dt validation stuff whats the names of the leds to match
a regexp.
Prefix the names with "led-" to make the validation happy.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
.../boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi b/arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi
index 99f5a5603dc7..71da10d9228f 100644
--- a/arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi
+++ b/arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi
@@ -33,11 +33,11 @@ vcc_io: regulator-io {
leds {
compatible = "gpio-leds";
- red {
+ led-red {
gpios = <&gpio MSC313_GPIO_SR_IO16 GPIO_ACTIVE_HIGH>;
linux,default-trigger = "activity";
};
- yellow {
+ led-yellow {
gpios = <&gpio MSC313_GPIO_SR_IO17 GPIO_ACTIVE_HIGH>;
linux,default-trigger = "heartbeat";
};
--
2.51.0
next prev parent reply other threads:[~2026-01-01 3:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 3:42 [PATCH v2 0/8] Sigmastar DT warnings fixing Daniel Palmer
2026-01-01 3:42 ` [PATCH v2 1/8] dt-bindings: clk: mstar msc313 cpupll: Correct clock-cells value Daniel Palmer
2026-01-01 4:33 ` Rob Herring (Arm)
2026-01-02 10:15 ` Krzysztof Kozlowski
2026-01-01 3:43 ` [PATCH v2 2/8] arm: dts: mstar: breadbee: Correct regulator names Daniel Palmer
2026-01-01 3:43 ` Daniel Palmer [this message]
2026-01-01 3:43 ` [PATCH v2 4/8] arm: dts: mstar: breadbee: Switch from "activity" led trigger to "cpu" Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 5/8] arm: dts: mstar: infinity: Correct opp table name Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 6/8] arm: dts: mstar: infinity2m: ssd202d: Correct memory node name Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 7/8] arm: dts: mstar: v7: Move the reboot node Daniel Palmer
2026-01-01 3:43 ` [PATCH v2 8/8] arm: dts: mstar: v7: Add sizes and ranges to sram Daniel Palmer
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=20260101034306.1233091-4-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=romain.perier@gmail.com \
/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
all inboxes | Powered by JetHome®