1menuconfig LEDS_TRIGGERS 2 bool "LED Trigger support" 3 depends on LEDS_CLASS 4 help 5 This option enables trigger support for the leds class. 6 These triggers allow kernel events to drive the LEDs and can 7 be configured via sysfs. If unsure, say Y. 8 9if LEDS_TRIGGERS 10 11config LEDS_TRIGGER_TIMER 12 tristate "LED Timer Trigger" 13 depends on LEDS_TRIGGERS 14 help 15 This allows LEDs to be controlled by a programmable timer 16 via sysfs. Some LED hardware can be programmed to start 17 blinking the LED without any further software interaction. 18 For more details read Documentation/leds/leds-class.txt. 19 20 If unsure, say Y. 21 22config LEDS_TRIGGER_ONESHOT 23 tristate "LED One-shot Trigger" 24 depends on LEDS_TRIGGERS 25 help 26 This allows LEDs to blink in one-shot pulses with parameters 27 controlled via sysfs. It's useful to notify the user on 28 sporadic events, when there are no clear begin and end trap points, 29 or on dense events, where this blinks the LED at constant rate if 30 rearmed continuously. 31 32 It also shows how to use the led_blink_set_oneshot() function. 33 34 If unsure, say Y. 35 36config LEDS_TRIGGER_IDE_DISK 37 bool "LED IDE Disk Trigger" 38 depends on IDE_GD_ATA 39 depends on LEDS_TRIGGERS 40 help 41 This allows LEDs to be controlled by IDE disk activity. 42 If unsure, say Y. 43 44config LEDS_TRIGGER_HEARTBEAT 45 tristate "LED Heartbeat Trigger" 46 depends on LEDS_TRIGGERS 47 help 48 This allows LEDs to be controlled by a CPU load average. 49 The flash frequency is a hyperbolic function of the 1-minute 50 load average. 51 If unsure, say Y. 52 53config LEDS_TRIGGER_BACKLIGHT 54 tristate "LED backlight Trigger" 55 depends on LEDS_TRIGGERS 56 help 57 This allows LEDs to be controlled as a backlight device: they 58 turn off and on when the display is blanked and unblanked. 59 60 If unsure, say N. 61 62config LEDS_TRIGGER_CPU 63 bool "LED CPU Trigger" 64 depends on LEDS_TRIGGERS 65 help 66 This allows LEDs to be controlled by active CPUs. This shows 67 the active CPUs across an array of LEDs so you can see which 68 CPUs are active on the system at any given moment. 69 70 If unsure, say N. 71 72config LEDS_TRIGGER_GPIO 73 tristate "LED GPIO Trigger" 74 depends on LEDS_TRIGGERS 75 depends on GPIOLIB 76 help 77 This allows LEDs to be controlled by gpio events. It's good 78 when using gpios as switches and triggering the needed LEDs 79 from there. One use case is n810's keypad LEDs that could 80 be triggered by this trigger when user slides up to show 81 keypad. 82 83 If unsure, say N. 84 85config LEDS_TRIGGER_DEFAULT_ON 86 tristate "LED Default ON Trigger" 87 depends on LEDS_TRIGGERS 88 help 89 This allows LEDs to be initialised in the ON state. 90 If unsure, say Y. 91 92comment "iptables trigger is under Netfilter config (LED target)" 93 depends on LEDS_TRIGGERS 94 95config LEDS_TRIGGER_TRANSIENT 96 tristate "LED Transient Trigger" 97 depends on LEDS_TRIGGERS 98 help 99 This allows one time activation of a transient state on 100 GPIO/PWM based hardware. 101 If unsure, say Y. 102 103endif # LEDS_TRIGGERS 104