summaryrefslogtreecommitdiff
path: root/target/linux/lantiq/xrx200/profiles
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2015-12-11 15:05:30 +0000
committerJohn Crispin <john@openwrt.org>2015-12-11 15:05:30 +0000
commit787120e3a3e3cfdf26efc22c652743f5d91840fd (patch)
treec272cdcaeacadfdb7412b304f7f6fe1d991eacfc /target/linux/lantiq/xrx200/profiles
parent1d2a4ec287f7da699eff26c22ffcd12cc5c6fe1f (diff)
downloadmtk-20170518-787120e3a3e3cfdf26efc22c652743f5d91840fd.zip
mtk-20170518-787120e3a3e3cfdf26efc22c652743f5d91840fd.tar.gz
mtk-20170518-787120e3a3e3cfdf26efc22c652743f5d91840fd.tar.bz2
lantiq: fix led setup after switch to uci-defaults-new.sh
The switch to uci-defaults-new.sh revealed a bug in the former used uci-defaults.sh, which failed to add leds with colons in the led name. This bug isn't any longer present in uci-defaults-new.sh and therefore all via DT defined leds will be added to /etc/config/system with their initial on/off state, regardless whether they are already added by the board specific led mappings. This results for a BTHOMEHUBV5A into the following led configuration: - soc:blue:power is added as led_power with the initial state "switched on" - soc:blue:power is added as led_soc_blue_power with the initial state "switched off" With the final result of a switched off power led after boot. The only led that needs to be added is the BTHOMEHUBV5A specific dimmed led. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47850
Diffstat (limited to 'target/linux/lantiq/xrx200/profiles')
0 files changed, 0 insertions, 0 deletions