aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm47xx/base-files
diff options
context:
space:
mode:
authorStefan Lippers-Hollmann <s.l-h@gmx.de>2018-06-28 14:04:46 +0200
committerMathias Kresin <dev@kresin.me>2018-06-28 18:39:57 +0200
commit7c7ca66109468b57f06d20eafbb9523aecc91706 (patch)
tree01449755dd8e4e1874948008c1a329b7e52bb796 /target/linux/brcm47xx/base-files
parent19c7e950af8edbc3f26114266b6007851e381b5b (diff)
downloadupstream-7c7ca66109468b57f06d20eafbb9523aecc91706.tar.gz
upstream-7c7ca66109468b57f06d20eafbb9523aecc91706.tar.bz2
upstream-7c7ca66109468b57f06d20eafbb9523aecc91706.zip
ipq806x: switch the NBG6817 wlan LEDs from amber to white
The original device support patch configured the amber wlan LEDs (which are meant as error indicator by the OEM) controlled by the SOC's GPIO as wlan traffic indicators, as the correct white wlan LEDs are connected to GPIOs controlled by the QCA9984/ ath10k wlan cards were not accessible. The recent addition of GPIO/ LED support to ath10k now makes it possible to use the correct white LEDs instead - and "mac80211: ath10k: use tpt LED trigger by default" also enables them by default. While both LEDs are independent of each other (two separate LEDs sharing one light tunnel), triggering both on wlan traffic is not the intended behaviour (bright yellow light). Tested on the ZyXEL NBG6817. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
Diffstat (limited to 'target/linux/brcm47xx/base-files')
0 files changed, 0 insertions, 0 deletions