diff options
author | Lech Perczak <lech.perczak@gmail.com> | 2022-05-23 20:37:47 +0200 |
---|---|---|
committer | Christian Lamparter <chunkeey@gmail.com> | 2022-06-05 21:19:32 +0200 |
commit | 5ca45e0a21ee1bdafd3652e7e91a761a9cd0c838 (patch) | |
tree | 71225b75356840b6d4115b07af94241bf7a91c52 | |
parent | 82b59846368db85ad1470396d95e7c20157288eb (diff) | |
download | upstream-5ca45e0a21ee1bdafd3652e7e91a761a9cd0c838.tar.gz upstream-5ca45e0a21ee1bdafd3652e7e91a761a9cd0c838.tar.bz2 upstream-5ca45e0a21ee1bdafd3652e7e91a761a9cd0c838.zip |
ath79: ZTE MF286[,A,R]: use GPIO19 as ath9k LED
With the pinctrl configuration set properly by the previous commit, the
LED stays lit regardless of status of 2.4GHz radio, even if 5GHz radio
is disabled. Map GPIO19 as LED for ath9k, this way the LED will show
activity for both bands, as it is bound by logical AND with output of
ath10k-phy0 LED. This works well because during management traffic,
phy*tpt triggers typically cause LEDs to blink in unison.
Link: <https://github.com/openwrt/openwrt/pull/9941>
Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
-rw-r--r-- | target/linux/ath79/dts/qca9563_zte_mf286.dtsi | 21 |
1 files changed, 7 insertions, 14 deletions
diff --git a/target/linux/ath79/dts/qca9563_zte_mf286.dtsi b/target/linux/ath79/dts/qca9563_zte_mf286.dtsi index f7cbbb85bd..76dd7b6be6 100644 --- a/target/linux/ath79/dts/qca9563_zte_mf286.dtsi +++ b/target/linux/ath79/dts/qca9563_zte_mf286.dtsi @@ -30,6 +30,13 @@ gpios = <&gpio 7 GPIO_ACTIVE_LOW>; default-state = "on"; }; + + led-1 { + function = LED_FUNCTION_WLAN; + color = <LED_COLOR_ID_BLUE>; + gpios = <&gpio 19 GPIO_ACTIVE_LOW>; + linux,default-trigger = "phy1tpt"; + }; }; keys { @@ -66,20 +73,6 @@ }; }; -&gpio { - /* GPIO19 is used as a mask to enable WLAN LED - * in stock firmware, which is controlled directly - * by 5GHz Wi-Fi chip, which currently is inactive - * in OpenWrt - */ - led-wlan { - gpio-hog; - gpios = <19 GPIO_ACTIVE_LOW>; - output-high; - line-name = "led:wlan"; - }; -}; - &spi { status = "okay"; |