menuconfig [31mCONFIG_LEDS_TRIGGERS[0m
bool "LED Trigger support"
depends on [31mCONFIG_LEDS_CLASS[0m
help
This option enables trigger support for the leds class.
These triggers allow kernel events to drive the LEDs and can
be configured via sysfs. If unsure, say Y.
if [31mCONFIG_LEDS_TRIGGERS[0m
config [31mCONFIG_LEDS_TRIGGER_TIMER[0m
tristate "LED Timer Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled by a programmable timer
via sysfs. Some LED hardware can be programmed to start
blinking the LED without any further software interaction.
For more details read Documentation/leds/leds-class.txt.
If unsure, say Y.
config [31mCONFIG_LEDS_TRIGGER_ONESHOT[0m
tristate "LED One-shot Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to blink in one-shot pulses with parameters
controlled via sysfs. It's useful to notify the user on
sporadic events, when there are no clear begin and end trap points,
or on dense events, where this blinks the LED at constant rate if
rearmed continuously.
It also shows how to use the led_blink_set_oneshot() function.
If unsure, say Y.
config [31mCONFIG_LEDS_TRIGGER_DISK[0m
bool "LED Disk Trigger"
depends on [31mCONFIG_IDE_GD_ATA[0m || [31mCONFIG_ATA[0m
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled by disk activity.
If unsure, say Y.
config [31mCONFIG_LEDS_TRIGGER_MTD[0m
bool "LED MTD (NAND/NOR) Trigger"
depends on [31mCONFIG_MTD[0m
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled by [31mCONFIG_MTD[0m activity.
If unsure, say N.
config [31mCONFIG_LEDS_TRIGGER_HEARTBEAT[0m
tristate "LED Heartbeat Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled by a CPU load average.
The flash frequency is a hyperbolic function of the 1-minute
load average.
If unsure, say Y.
config [31mCONFIG_LEDS_TRIGGER_BACKLIGHT[0m
tristate "LED backlight Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled as a backlight device: they
turn off and on when the display is blanked and unblanked.
If unsure, say N.
config [31mCONFIG_LEDS_TRIGGER_CPU[0m
bool "LED CPU Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled by active CPUs. This shows
the active CPUs across an array of LEDs so you can see which
CPUs are active on the system at any given moment.
If unsure, say N.
config [31mCONFIG_LEDS_TRIGGER_GPIO[0m
tristate "LED GPIO Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
This allows LEDs to be controlled by gpio events. It's good
when using gpios as switches and triggering the needed LEDs
from there. One use case is n810's keypad LEDs that could
be triggered by this trigger when user slides up to show
keypad.
If unsure, say N.
config [31mCONFIG_LEDS_TRIGGER_DEFAULT_ON[0m
tristate "LED Default ON Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be initialised in the ON state.
If unsure, say Y.
comment "iptables trigger is under Netfilter config (LED target)"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
config [31mCONFIG_LEDS_TRIGGER_TRANSIENT[0m
tristate "LED Transient Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows one time activation of a transient state on
GPIO/[31mCONFIG_PWM[0m based hardware.
If unsure, say Y.
config [31mCONFIG_LEDS_TRIGGER_CAMERA[0m
tristate "LED Camera Flash/Torch Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be controlled as a camera flash/torch device.
This enables direct flash/torch on/off by the driver, kernel space.
If unsure, say Y.
config [31mCONFIG_LEDS_TRIGGER_PANIC[0m
bool "LED Panic Trigger"
depends on [31mCONFIG_LEDS_TRIGGERS[0m
help
This allows LEDs to be configured to blink on a kernel panic.
Enabling this option will allow to mark certain LEDs as panic indicators,
allowing to blink them on a kernel panic, even if they are set to
a different trigger.
If unsure, say Y.
endif # [31mCONFIG_LEDS_TRIGGERS[0m