projects / mirror_ubuntu-bionic-kernel.git / blame
| Commit | Line | Data |
|---|---|---|
| f07fb521 KM |
1 | menuconfig 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 | ||
| 9 | if LEDS_TRIGGERS | |
| 10 | ||
| 11 | config 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 | ||
| 22 | config 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 | ||
| eb25cb99 SL |
36 | config LEDS_TRIGGER_DISK |
| 37 | bool "LED Disk Trigger" | |
| 38 | depends on IDE_GD_ATA || ATA | |
| f07fb521 KM |
39 | depends on LEDS_TRIGGERS |
| 40 | help | |
| eb25cb99 | 41 | This allows LEDs to be controlled by disk activity. |
| f07fb521 KM |
42 | If unsure, say Y. |
| 43 | ||
| 4b721174 EG |
44 | config 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 | ||
| f07fb521 KM |
52 | config 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 | ||
| 61 | config 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 | ||
| 70 | config 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 | ||
| 7df4f9a9 WT |
80 | config LEDS_TRIGGER_ACTIVITY |
| 81 | tristate "LED activity Trigger" | |
| 82 | depends on LEDS_TRIGGERS | |
| 83 | help | |
| 84 | This allows LEDs to be controlled by a immediate CPU usage. | |
| 85 | The flash frequency and duty cycle varies from faint flashes to | |
| 86 | intense brightness depending on the instant CPU load. | |
| 87 | If unsure, say N. | |
| 88 | ||
| f07fb521 KM |
89 | config LEDS_TRIGGER_GPIO |
| 90 | tristate "LED GPIO Trigger" | |
| 91 | depends on LEDS_TRIGGERS | |
| 82322741 | 92 | depends on GPIOLIB || COMPILE_TEST |
| f07fb521 KM |
93 | help |
| 94 | This allows LEDs to be controlled by gpio events. It's good | |
| 95 | when using gpios as switches and triggering the needed LEDs | |
| 96 | from there. One use case is n810's keypad LEDs that could | |
| 97 | be triggered by this trigger when user slides up to show | |
| 98 | keypad. | |
| 99 | ||
| 100 | If unsure, say N. | |
| 101 | ||
| 102 | config LEDS_TRIGGER_DEFAULT_ON | |
| 103 | tristate "LED Default ON Trigger" | |
| 104 | depends on LEDS_TRIGGERS | |
| 105 | help | |
| 106 | This allows LEDs to be initialised in the ON state. | |
| 107 | If unsure, say Y. | |
| 108 | ||
| 109 | comment "iptables trigger is under Netfilter config (LED target)" | |
| 110 | depends on LEDS_TRIGGERS | |
| 111 | ||
| 112 | config LEDS_TRIGGER_TRANSIENT | |
| 113 | tristate "LED Transient Trigger" | |
| 114 | depends on LEDS_TRIGGERS | |
| 115 | help | |
| 116 | This allows one time activation of a transient state on | |
| 117 | GPIO/PWM based hardware. | |
| 118 | If unsure, say Y. | |
| 119 | ||
| 48a1d032 KM |
120 | config LEDS_TRIGGER_CAMERA |
| 121 | tristate "LED Camera Flash/Torch Trigger" | |
| 122 | depends on LEDS_TRIGGERS | |
| 123 | help | |
| 124 | This allows LEDs to be controlled as a camera flash/torch device. | |
| 125 | This enables direct flash/torch on/off by the driver, kernel space. | |
| 126 | If unsure, say Y. | |
| 127 | ||
| 916fe619 EG |
128 | config LEDS_TRIGGER_PANIC |
| 129 | bool "LED Panic Trigger" | |
| 130 | depends on LEDS_TRIGGERS | |
| 131 | help | |
| 132 | This allows LEDs to be configured to blink on a kernel panic. | |
| ba93cdce EG |
133 | Enabling this option will allow to mark certain LEDs as panic indicators, |
| 134 | allowing to blink them on a kernel panic, even if they are set to | |
| 135 | a different trigger. | |
| 916fe619 EG |
136 | If unsure, say Y. |
| 137 | ||
| f07fb521 | 138 | endif # LEDS_TRIGGERS |