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 4/8] arm: dts: mstar: breadbee: Switch from "activity" led trigger to "cpu"
Date: Thu, 1 Jan 2026 12:43:02 +0900 [thread overview]
Message-ID: <20260101034306.1233091-5-daniel@0x0f.com> (raw)
In-Reply-To: <20260101034306.1233091-1-daniel@0x0f.com>
The activity trigger exists but is not documented in the LED binding.
A patch was sent to document it but wasn't accepted.
The intention of the LED is to show if the system is busy or not
so the cpu trigger is good enough so switch to that to clean up
the warning.
Link: https://lore.kernel.org/all/20210923065500.2284347-4-daniel@0x0f.com/
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 71da10d9228f..0f03f471a344 100644
--- a/arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi
+++ b/arch/arm/boot/dts/sigmastar/mstar-infinity-breadbee-common.dtsi
@@ -35,7 +35,7 @@ leds {
compatible = "gpio-leds";
led-red {
gpios = <&gpio MSC313_GPIO_SR_IO16 GPIO_ACTIVE_HIGH>;
- linux,default-trigger = "activity";
+ linux,default-trigger = "cpu";
};
led-yellow {
gpios = <&gpio MSC313_GPIO_SR_IO17 GPIO_ACTIVE_HIGH>;
--
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 ` [PATCH v2 3/8] arm: dts: mstar: breadbee: Correct LED names Daniel Palmer
2026-01-01 3:43 ` Daniel Palmer [this message]
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-5-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;
as well as URLs for NNTP newsgroup(s).