bcm53xx: ea9200: use network LED trigger

The LED controls the state of all wireless interfaces. Use the new
network LED trigger to control this.

Signed-off-by: Rosen Penev <rosenp@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/22223
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>

diff --git a/target/linux/bcm53xx/image/Makefile b/target/linux/bcm53xx/image/Makefile
index 1327e252fe29118a1548dcde0db9f76aeefc5112..38a2b3a8305b4b00a2e4f3d08302a967f54dc411 100644 (file)
--- a/target/linux/bcm53xx/image/Makefile
+++ b/target/linux/bcm53xx/image/Makefile
@@ -343,7 +343,7 @@ define Device/linksys_ea9200
   DEVICE_VENDOR := Linksys
   DEVICE_MODEL := EA9200
   DEVICE_VARIANT := v1
-  DEVICE_PACKAGES := $(BRCMFMAC_43602A1) $(USB3_PACKAGES)
+  DEVICE_PACKAGES := $(BRCMFMAC_43602A1) $(USB3_PACKAGES) kmod-ledtrig-network
 endef
 TARGET_DEVICES += linksys_ea9200
 

diff --git a/target/linux/bcm53xx/patches-6.12/326-ARM-dts-BCM5301X-EA9200-use-network-LED-trigger.patch b/target/linux/bcm53xx/patches-6.12/326-ARM-dts-BCM5301X-EA9200-use-network-LED-trigger.patch
new file mode 100644 (file)
index 0000000..4983ee6
--- /dev/null
+++ b/target/linux/bcm53xx/patches-6.12/326-ARM-dts-BCM5301X-EA9200-use-network-LED-trigger.patch
@@ -0,0 +1,24 @@
+From: Rosen Penev <rosenp@gmail.com>
+Subject: [PATCH] ARM: dts: BCM5301X: EA9200: use network LED trigger for WLAN LED
+
+The "rfkill-none" trigger is only registered when CONFIG_RFKILL_LEDS is
+enabled, which OpenWrt disables tree-wide, so the WLAN LED never lights
+up. Use the network LED trigger instead.
+
+Signed-off-by: Rosen Penev <rosenp@gmail.com>
+---
+ arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+--- a/arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts
++++ b/arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts
+@@ -62,7 +62,8 @@
+                       color = <LED_COLOR_ID_AMBER>;
+                       function = LED_FUNCTION_WLAN;
+                       gpios = <&chipcommon 0 GPIO_ACTIVE_LOW>;
+-                      linux,default-trigger = "rfkill-none";
++                      linux,default-trigger = "network";
++                      family = "wlan";
+               };
+ 
+               led-1 {

diff --git a/target/linux/bcm53xx/patches-6.18/326-ARM-dts-BCM5301X-EA9200-use-network-LED-trigger.patch b/target/linux/bcm53xx/patches-6.18/326-ARM-dts-BCM5301X-EA9200-use-network-LED-trigger.patch
new file mode 100644 (file)
index 0000000..4983ee6
--- /dev/null
+++ b/target/linux/bcm53xx/patches-6.18/326-ARM-dts-BCM5301X-EA9200-use-network-LED-trigger.patch
@@ -0,0 +1,24 @@
+From: Rosen Penev <rosenp@gmail.com>
+Subject: [PATCH] ARM: dts: BCM5301X: EA9200: use network LED trigger for WLAN LED
+
+The "rfkill-none" trigger is only registered when CONFIG_RFKILL_LEDS is
+enabled, which OpenWrt disables tree-wide, so the WLAN LED never lights
+up. Use the network LED trigger instead.
+
+Signed-off-by: Rosen Penev <rosenp@gmail.com>
+---
+ arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+--- a/arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts
++++ b/arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts
+@@ -62,7 +62,8 @@
+                       color = <LED_COLOR_ID_AMBER>;
+                       function = LED_FUNCTION_WLAN;
+                       gpios = <&chipcommon 0 GPIO_ACTIVE_LOW>;
+-                      linux,default-trigger = "rfkill-none";
++                      linux,default-trigger = "network";
++                      family = "wlan";
+               };
+ 
+               led-1 {