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_DISK 37 bool "LED Disk Trigger" 38 depends on IDE_GD_ATA || ATA 39 depends on LEDS_TRIGGERS 40 help 41 This allows LEDs to be controlled by disk activity. 42 If unsure, say Y. 43 44config LEDS_TRIGGER_MTD 45 bool "LED MTD (NAND/NOR) Trigger" 46 depends on MTD 47 depends on LEDS_TRIGGERS 48 help 49 This allows LEDs to be controlled by MTD activity. 50 If unsure, say N. 51 52config LEDS_TRIGGER_HEARTBEAT 53 tristate "LED Heartbeat Trigger" 54 depends on LEDS_TRIGGERS 55 help 56 This allows LEDs to be controlled by a CPU load average. 57 The flash frequency is a hyperbolic function of the 1-minute 58 load average. 59 If unsure, say Y. 60 61config LEDS_TRIGGER_BACKLIGHT 62 tristate "LED backlight Trigger" 63 depends on LEDS_TRIGGERS 64 help 65 This allows LEDs to be controlled as a backlight device: they 66 turn off and on when the display is blanked and unblanked. 67 68 If unsure, say N. 69 70config LEDS_TRIGGER_CPU 71 bool "LED CPU Trigger" 72 depends on LEDS_TRIGGERS 73 help 74 This allows LEDs to be controlled by active CPUs. This shows 75 the active CPUs across an array of LEDs so you can see which 76 CPUs are active on the system at any given moment. 77 78 If unsure, say N. 79 80config LEDS_TRIGGER_GPIO 81 tristate "LED GPIO Trigger" 82 depends on LEDS_TRIGGERS 83 depends on GPIOLIB || COMPILE_TEST 84 help 85 This allows LEDs to be controlled by gpio events. It's good 86 when using gpios as switches and triggering the needed LEDs 87 from there. One use case is n810's keypad LEDs that could 88 be triggered by this trigger when user slides up to show 89 keypad. 90 91 If unsure, say N. 92 93config LEDS_TRIGGER_DEFAULT_ON 94 tristate "LED Default ON Trigger" 95 depends on LEDS_TRIGGERS 96 help 97 This allows LEDs to be initialised in the ON state. 98 If unsure, say Y. 99 100comment "iptables trigger is under Netfilter config (LED target)" 101 depends on LEDS_TRIGGERS 102 103config LEDS_TRIGGER_TRANSIENT 104 tristate "LED Transient Trigger" 105 depends on LEDS_TRIGGERS 106 help 107 This allows one time activation of a transient state on 108 GPIO/PWM based hardware. 109 If unsure, say Y. 110 111config LEDS_TRIGGER_CAMERA 112 tristate "LED Camera Flash/Torch Trigger" 113 depends on LEDS_TRIGGERS 114 help 115 This allows LEDs to be controlled as a camera flash/torch device. 116 This enables direct flash/torch on/off by the driver, kernel space. 117 If unsure, say Y. 118 119config LEDS_TRIGGER_PANIC 120 bool "LED Panic Trigger" 121 depends on LEDS_TRIGGERS 122 help 123 This allows LEDs to be configured to blink on a kernel panic. 124 Enabling this option will allow to mark certain LEDs as panic indicators, 125 allowing to blink them on a kernel panic, even if they are set to 126 a different trigger. 127 If unsure, say Y. 128 129endif # LEDS_TRIGGERS 130