aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic-2.6/config-2.6.23
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2008-02-02 01:21:54 +0000
committerFelix Fietkau <nbd@openwrt.org>2008-02-02 01:21:54 +0000
commita2ba826425ad14f2b0f8d33486720260a9495c26 (patch)
tree8621560065e7b3ef5acb72e2be7593c72098cdcf /target/linux/generic-2.6/config-2.6.23
parent738d610209c81288218c31b1edd99e20449550ae (diff)
downloadupstream-a2ba826425ad14f2b0f8d33486720260a9495c26.tar.gz
upstream-a2ba826425ad14f2b0f8d33486720260a9495c26.tar.bz2
upstream-a2ba826425ad14f2b0f8d33486720260a9495c26.zip
"default-on" LED Trigger
The current LED subsystem always initialises LEDs in the OFF state. This is fine for most LEDs but some should be on right from boot (e.g. POWER LED). Following some discussion with the LED subsystem maintainers, a trigger was recommended as the best way to implement this functionality. Here is a patch to add a new trigger "default-on" which will initialise an LED in the ON state. It is not compiled by default. Particular thanks to Rod Whitby for all his help with this. Signed-off-by: Nick Forbes <nick.forbes@incepta.com> SVN-Revision: 10348
Diffstat (limited to 'target/linux/generic-2.6/config-2.6.23')
-rw-r--r--target/linux/generic-2.6/config-2.6.231
1 files changed, 1 insertions, 0 deletions
diff --git a/target/linux/generic-2.6/config-2.6.23 b/target/linux/generic-2.6/config-2.6.23
index e92c8b3f1b..734842144e 100644
--- a/target/linux/generic-2.6/config-2.6.23
+++ b/target/linux/generic-2.6/config-2.6.23
@@ -677,6 +677,7 @@ CONFIG_LEDS_TRIGGER_HEARTBEAT=y
# CONFIG_LEDS_TRIGGER_IDE_DISK is not set
# CONFIG_LEDS_TRIGGER_MORSE is not set
CONFIG_LEDS_TRIGGER_TIMER=y
+# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
# CONFIG_LEGACY_PTYS is not set
CONFIG_LIBCRC32C=m
# CONFIG_LIBERTAS is not set