]>
Commit | Line | Data |
---|---|---|
be5ce2f1 UKK |
1 | config LEDS_GPIO_REGISTER |
2 | bool | |
3 | help | |
4 | This option provides the function gpio_led_register_device. | |
5 | As this function is used by arch code it must not be compiled as a | |
6 | module. | |
7 | ||
66242f7e | 8 | menuconfig NEW_LEDS |
c72a1d60 RP |
9 | bool "LED Support" |
10 | help | |
a8d2e7d9 RP |
11 | Say Y to enable Linux LED support. This allows control of supported |
12 | LEDs from both userspace and optionally, by kernel events (triggers). | |
13 | ||
14 | This is not related to standard keyboard LEDs which are controlled | |
15 | via the input system. | |
c72a1d60 | 16 | |
45d16f09 EM |
17 | if NEW_LEDS |
18 | ||
c72a1d60 | 19 | config LEDS_CLASS |
a403d930 | 20 | tristate "LED Class Support" |
c72a1d60 RP |
21 | help |
22 | This option enables the led sysfs class in /sys/class/leds. You'll | |
23 | need this to do anything useful with LEDs. If unsure, say N. | |
24 | ||
24f51e81 | 25 | comment "LED drivers" |
c3bc9956 | 26 | |
0a2f915b HZ |
27 | config LEDS_88PM860X |
28 | tristate "LED Support for Marvell 88PM860x PMIC" | |
0bae35e1 | 29 | depends on LEDS_CLASS |
37814fdc | 30 | depends on MFD_88PM860X |
0a2f915b HZ |
31 | help |
32 | This option enables support for on-chip LED drivers found on Marvell | |
33 | Semiconductor 88PM8606 PMIC. | |
34 | ||
de5c9ede DB |
35 | config LEDS_ATMEL_PWM |
36 | tristate "LED Support using Atmel PWM outputs" | |
0bae35e1 | 37 | depends on LEDS_CLASS |
d09e1666 | 38 | depends on ATMEL_PWM |
de5c9ede DB |
39 | help |
40 | This option enables support for LEDs driven using outputs | |
41 | of the dedicated PWM controller found on newer Atmel SOCs. | |
42 | ||
b1e6b706 SKS |
43 | config LEDS_LM3530 |
44 | tristate "LCD Backlight driver for LM3530" | |
45 | depends on LEDS_CLASS | |
46 | depends on I2C | |
47 | help | |
48 | This option enables support for the LCD backlight using | |
49 | LM3530 ambient light sensor chip. This ALS chip can be | |
50 | controlled manually or using PWM input or using ambient | |
51 | light automatically. | |
52 | ||
401dea7f JH |
53 | config LEDS_LM3533 |
54 | tristate "LED support for LM3533" | |
55 | depends on LEDS_CLASS | |
56 | depends on MFD_LM3533 | |
57 | help | |
58 | This option enables support for the LEDs on National Semiconductor / | |
59 | TI LM3533 Lighting Power chips. | |
60 | ||
61 | The LEDs can be controlled directly, through PWM input, or by the | |
62 | ambient-light-sensor interface. The chip supports | |
63 | hardware-accelerated blinking with maximum on and off periods of 9.8 | |
64 | and 77 seconds respectively. | |
65 | ||
8b7cfbec SJ |
66 | config LEDS_LM3642 |
67 | tristate "LED support for LM3642 Chip" | |
68 | depends on LEDS_CLASS && I2C | |
69 | select REGMAP_I2C | |
70 | help | |
71 | This option enables support for LEDs connected to LM3642. | |
72 | The LM3642 is a 4MHz fixed-frequency synchronous boost | |
73 | converter plus 1.5A constant current driver for a high-current | |
74 | white LED. | |
75 | ||
76 | ||
4d3cb354 RP |
77 | config LEDS_LOCOMO |
78 | tristate "LED Support for Locomo device" | |
0bae35e1 | 79 | depends on LEDS_CLASS |
d09e1666 | 80 | depends on SHARP_LOCOMO |
4d3cb354 RP |
81 | help |
82 | This option enables support for the LEDs on Sharp Locomo. | |
83 | Zaurus models SL-5500 and SL-5600. | |
84 | ||
ac67e23b PS |
85 | config LEDS_MIKROTIK_RB532 |
86 | tristate "LED Support for Mikrotik Routerboard 532" | |
0bae35e1 | 87 | depends on LEDS_CLASS |
d09e1666 | 88 | depends on MIKROTIK_RB532 |
ac67e23b PS |
89 | help |
90 | This option enables support for the so called "User LED" of | |
91 | Mikrotik's Routerboard 532. | |
92 | ||
54bdc470 BD |
93 | config LEDS_S3C24XX |
94 | tristate "LED Support for Samsung S3C24XX GPIO LEDs" | |
0bae35e1 | 95 | depends on LEDS_CLASS |
b130d5c2 | 96 | depends on ARCH_S3C24XX |
54bdc470 BD |
97 | help |
98 | This option enables support for LEDs connected to GPIO lines | |
99 | on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440. | |
100 | ||
1a87d942 CB |
101 | config LEDS_NET48XX |
102 | tristate "LED Support for Soekris net48xx series Error LED" | |
0bae35e1 | 103 | depends on LEDS_CLASS |
d09e1666 | 104 | depends on SCx200_GPIO |
1a87d942 CB |
105 | help |
106 | This option enables support for the Soekris net4801 and net4826 error | |
107 | LED. | |
108 | ||
3b2e46f8 RW |
109 | config LEDS_FSG |
110 | tristate "LED Support for the Freecom FSG-3" | |
0bae35e1 | 111 | depends on LEDS_CLASS |
d09e1666 | 112 | depends on MACH_FSG |
3b2e46f8 RW |
113 | help |
114 | This option enables support for the LEDs on the Freecom FSG-3. | |
115 | ||
0d75565f KK |
116 | config LEDS_WRAP |
117 | tristate "LED Support for the WRAP series LEDs" | |
0bae35e1 | 118 | depends on LEDS_CLASS |
d09e1666 | 119 | depends on SCx200_GPIO |
0d75565f KK |
120 | help |
121 | This option enables support for the PCEngines WRAP programmable LEDs. | |
122 | ||
f3b6b6cd YY |
123 | config LEDS_COBALT_QUBE |
124 | tristate "LED Support for the Cobalt Qube series front LED" | |
0bae35e1 | 125 | depends on LEDS_CLASS |
d09e1666 | 126 | depends on MIPS_COBALT |
2fea6f35 | 127 | help |
f3b6b6cd | 128 | This option enables support for the front LED on Cobalt Qube series |
2fea6f35 | 129 | |
97da7aaf YY |
130 | config LEDS_COBALT_RAQ |
131 | bool "LED Support for the Cobalt Raq series" | |
ec149619 | 132 | depends on LEDS_CLASS=y && MIPS_COBALT |
97da7aaf YY |
133 | select LEDS_TRIGGERS |
134 | help | |
135 | This option enables support for the Cobalt Raq series LEDs. | |
136 | ||
5843492c DM |
137 | config LEDS_SUNFIRE |
138 | tristate "LED support for SunFire servers." | |
0bae35e1 | 139 | depends on LEDS_CLASS |
d09e1666 | 140 | depends on SPARC64 |
5843492c DM |
141 | select LEDS_TRIGGERS |
142 | help | |
143 | This option enables support for the Left, Middle, and Right | |
144 | LEDs on the I/O and CPU boards of SunFire UltraSPARC servers. | |
145 | ||
d39a7a63 KE |
146 | config LEDS_HP6XX |
147 | tristate "LED Support for the HP Jornada 6xx" | |
0bae35e1 | 148 | depends on LEDS_CLASS |
d09e1666 | 149 | depends on SH_HP6XX |
d39a7a63 | 150 | help |
692105b8 | 151 | This option enables LED support for the handheld |
d39a7a63 KE |
152 | HP Jornada 620/660/680/690. |
153 | ||
e14fa824 RV |
154 | config LEDS_PCA9532 |
155 | tristate "LED driver for PCA9532 dimmer" | |
0bae35e1 | 156 | depends on LEDS_CLASS |
d09e1666 | 157 | depends on I2C && INPUT && EXPERIMENTAL |
e14fa824 RV |
158 | help |
159 | This option enables support for NXP pca9532 | |
692105b8 | 160 | LED controller. It is generally only useful |
e14fa824 RV |
161 | as a platform driver |
162 | ||
3c1ab50d JE |
163 | config LEDS_PCA9532_GPIO |
164 | bool "Enable GPIO support for PCA9532" | |
165 | depends on LEDS_PCA9532 | |
166 | depends on GPIOLIB | |
167 | help | |
168 | Allow unused pins on PCA9532 to be used as gpio. | |
169 | ||
170 | To use a pin as gpio pca9532_type in pca9532_platform data needs to | |
171 | set to PCA9532_TYPE_GPIO. | |
172 | ||
22e03f3b RA |
173 | config LEDS_GPIO |
174 | tristate "LED Support for GPIO connected LEDs" | |
0bae35e1 | 175 | depends on LEDS_CLASS |
d09e1666 | 176 | depends on GENERIC_GPIO |
22e03f3b RA |
177 | help |
178 | This option enables support for the LEDs connected to GPIO | |
179 | outputs. To be useful the particular board must have LEDs | |
a7d878af TP |
180 | and they must be connected to the GPIO lines. The LEDs must be |
181 | defined as platform devices and/or OpenFirmware platform devices. | |
182 | The code to use these bindings can be selected below. | |
183 | ||
5054d39e AO |
184 | config LEDS_LP3944 |
185 | tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip" | |
0bae35e1 | 186 | depends on LEDS_CLASS |
d09e1666 | 187 | depends on I2C |
5054d39e | 188 | help |
7f1be819 AO |
189 | This option enables support for LEDs connected to the National |
190 | Semiconductor LP3944 Lighting Management Unit (LMU) also known as | |
191 | Fun Light Chip. | |
5054d39e AO |
192 | |
193 | To compile this driver as a module, choose M here: the | |
194 | module will be called leds-lp3944. | |
195 | ||
c93d08fa MWK |
196 | config LEDS_LP55XX_COMMON |
197 | tristate "Common Driver for TI/National LP5521 and LP5523/55231" | |
198 | depends on LEDS_LP5521 || LEDS_LP5523 | |
199 | help | |
200 | This option supports common operations for LP5521 and LP5523/55231 | |
201 | devices. | |
202 | ||
f4920f67 SO |
203 | config LEDS_LP5521 |
204 | tristate "LED Support for N.S. LP5521 LED driver chip" | |
205 | depends on LEDS_CLASS && I2C | |
c93d08fa | 206 | select LEDS_LP55XX_COMMON |
f4920f67 SO |
207 | help |
208 | If you say yes here you get support for the National Semiconductor | |
209 | LP5521 LED driver. It is 3 channel chip with programmable engines. | |
210 | Driver provides direct control via LED class and interface for | |
211 | programming the engines. | |
212 | ||
213 | config LEDS_LP5523 | |
ca705321 | 214 | tristate "LED Support for TI/National LP5523/55231 LED driver chip" |
f4920f67 | 215 | depends on LEDS_CLASS && I2C |
c93d08fa | 216 | select LEDS_LP55XX_COMMON |
f4920f67 | 217 | help |
ca705321 KM |
218 | If you say yes here you get support for TI/National Semiconductor |
219 | LP5523/55231 LED driver. | |
220 | It is 9 channel chip with programmable engines. | |
f4920f67 SO |
221 | Driver provides direct control via LED class and interface for |
222 | programming the engines. | |
223 | ||
eb80411b KM |
224 | config LEDS_LP8788 |
225 | tristate "LED support for the TI LP8788 PMIC" | |
226 | depends on LEDS_CLASS | |
227 | depends on MFD_LP8788 | |
228 | help | |
229 | This option enables support for the Keyboard LEDs on the LP8788 PMIC. | |
230 | ||
cec035de | 231 | config LEDS_CLEVO_MAIL |
95dc5768 | 232 | tristate "Mail LED on Clevo notebook" |
0bae35e1 | 233 | depends on LEDS_CLASS |
d09e1666 | 234 | depends on X86 && SERIO_I8042 && DMI |
cec035de MN |
235 | help |
236 | This driver makes the mail LED accessible from userspace | |
237 | programs through the leds subsystem. This LED have three | |
238 | known mode: off, blink at 0.5Hz and blink at 1Hz. | |
239 | ||
92e015cb MN |
240 | The driver supports two kinds of interface: using ledtrig-timer |
241 | or through /sys/class/leds/clevo::mail/brightness. As this LED | |
242 | cannot change it's brightness it blinks instead. The brightness | |
243 | value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means | |
244 | blink at 1Hz. | |
cec035de MN |
245 | |
246 | This module can drive the mail LED for the following notebooks: | |
247 | ||
b3ba31f8 | 248 | Clevo D400P |
cec035de MN |
249 | Clevo D410J |
250 | Clevo D410V | |
251 | Clevo D400V/D470V (not tested, but might work) | |
252 | Clevo M540N | |
253 | Clevo M5x0N (not tested, but might work) | |
254 | Positivo Mobile (Clevo M5x0V) | |
255 | ||
b3ba31f8 | 256 | If your model is not listed here you can try the "nodetect" |
692105b8 | 257 | module parameter. |
b3ba31f8 | 258 | |
cec035de MN |
259 | To compile this driver as a module, choose M here: the |
260 | module will be called leds-clevo-mail. | |
261 | ||
f46e9203 NC |
262 | config LEDS_PCA955X |
263 | tristate "LED Support for PCA955x I2C chips" | |
0bae35e1 | 264 | depends on LEDS_CLASS |
d09e1666 | 265 | depends on I2C |
f46e9203 NC |
266 | help |
267 | This option enables support for LEDs connected to PCA955x | |
268 | LED driver chips accessed via the I2C bus. Supported | |
269 | devices include PCA9550, PCA9551, PCA9552, and PCA9553. | |
270 | ||
75cb2e1d PM |
271 | config LEDS_PCA9633 |
272 | tristate "LED support for PCA9633 I2C chip" | |
273 | depends on LEDS_CLASS | |
274 | depends on I2C | |
275 | help | |
276 | This option enables support for LEDs connected to the PCA9633 | |
277 | LED driver chip accessed via the I2C bus. | |
278 | ||
c746b551 MB |
279 | config LEDS_WM831X_STATUS |
280 | tristate "LED support for status LEDs on WM831x PMICs" | |
0bae35e1 | 281 | depends on LEDS_CLASS |
d09e1666 | 282 | depends on MFD_WM831X |
c746b551 MB |
283 | help |
284 | This option enables support for the status LEDs of the WM831x | |
285 | series of PMICs. | |
286 | ||
0081e802 MB |
287 | config LEDS_WM8350 |
288 | tristate "LED Support for WM8350 AudioPlus PMIC" | |
0bae35e1 | 289 | depends on LEDS_CLASS |
d09e1666 | 290 | depends on MFD_WM8350 |
0081e802 MB |
291 | help |
292 | This option enables support for LEDs driven by the Wolfson | |
293 | Microelectronics WM8350 AudioPlus PMIC. | |
294 | ||
9e84561c MR |
295 | config LEDS_DA903X |
296 | tristate "LED Support for DA9030/DA9034 PMIC" | |
0bae35e1 | 297 | depends on LEDS_CLASS |
d09e1666 | 298 | depends on PMIC_DA903X |
9e84561c MR |
299 | help |
300 | This option enables support for on-chip LED drivers found | |
301 | on Dialog Semiconductor DA9030/DA9034 PMICs. | |
302 | ||
5ba73631 DDC |
303 | config LEDS_DA9052 |
304 | tristate "Dialog DA9052/DA9053 LEDS" | |
305 | depends on LEDS_CLASS | |
306 | depends on PMIC_DA9052 | |
307 | help | |
308 | This option enables support for on-chip LED drivers found | |
309 | on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs. | |
310 | ||
ac2dd0f1 GL |
311 | config LEDS_DAC124S085 |
312 | tristate "LED Support for DAC124S085 SPI DAC" | |
0bae35e1 | 313 | depends on LEDS_CLASS |
d09e1666 | 314 | depends on SPI |
ac2dd0f1 GL |
315 | help |
316 | This option enables support for DAC124S085 SPI DAC from NatSemi, | |
317 | which can be used to control up to four LEDs. | |
318 | ||
41c42ff5 LF |
319 | config LEDS_PWM |
320 | tristate "PWM driven LED Support" | |
0bae35e1 | 321 | depends on LEDS_CLASS |
d09e1666 | 322 | depends on HAVE_PWM |
41c42ff5 LF |
323 | help |
324 | This option enables support for pwm driven LEDs | |
325 | ||
d4cc6a2e AO |
326 | config LEDS_REGULATOR |
327 | tristate "REGULATOR driven LED support" | |
0bae35e1 | 328 | depends on LEDS_CLASS |
d09e1666 | 329 | depends on REGULATOR |
d4cc6a2e AO |
330 | help |
331 | This option enables support for regulator driven LEDs. | |
332 | ||
0b56129b KK |
333 | config LEDS_BD2802 |
334 | tristate "LED driver for BD2802 RGB LED" | |
0bae35e1 | 335 | depends on LEDS_CLASS |
d09e1666 | 336 | depends on I2C |
0b56129b KK |
337 | help |
338 | This option enables support for BD2802GU RGB LED driver chips | |
339 | accessed via the I2C bus. | |
340 | ||
a328e95b DH |
341 | config LEDS_INTEL_SS4200 |
342 | tristate "LED driver for Intel NAS SS4200 series" | |
0bae35e1 | 343 | depends on LEDS_CLASS |
d09e1666 | 344 | depends on PCI && DMI |
a328e95b DH |
345 | help |
346 | This option enables support for the Intel SS4200 series of | |
347 | Network Attached Storage servers. You may control the hard | |
348 | drive or power LEDs on the front panel. Using this driver | |
349 | can stop the front LED from blinking after startup. | |
350 | ||
a8dd18fe DM |
351 | config LEDS_LT3593 |
352 | tristate "LED driver for LT3593 controllers" | |
0bae35e1 | 353 | depends on LEDS_CLASS |
d09e1666 | 354 | depends on GENERIC_GPIO |
a8dd18fe DM |
355 | help |
356 | This option enables support for LEDs driven by a Linear Technology | |
357 | LT3593 controller. This controller uses a special one-wire pulse | |
358 | coding protocol to set the brightness. | |
359 | ||
ed4a10b4 MH |
360 | config LEDS_ADP5520 |
361 | tristate "LED Support for ADP5520/ADP5501 PMIC" | |
0bae35e1 | 362 | depends on LEDS_CLASS |
d09e1666 | 363 | depends on PMIC_ADP5520 |
ed4a10b4 MH |
364 | help |
365 | This option enables support for on-chip LED drivers found | |
366 | on Analog Devices ADP5520/ADP5501 PMICs. | |
367 | ||
368 | To compile this driver as a module, choose M here: the module will | |
369 | be called leds-adp5520. | |
370 | ||
72dcd8d0 BR |
371 | config LEDS_DELL_NETBOOKS |
372 | tristate "External LED on Dell Business Netbooks" | |
0bae35e1 | 373 | depends on LEDS_CLASS |
72dcd8d0 BR |
374 | depends on X86 && ACPI_WMI |
375 | help | |
376 | This adds support for the Latitude 2100 and similar | |
377 | notebooks that have an external LED. | |
378 | ||
7fdcef8a PR |
379 | config LEDS_MC13783 |
380 | tristate "LED Support for MC13783 PMIC" | |
0bae35e1 | 381 | depends on LEDS_CLASS |
7fdcef8a PR |
382 | depends on MFD_MC13783 |
383 | help | |
384 | This option enable support for on-chip LED drivers found | |
385 | on Freescale Semiconductor MC13783 PMIC. | |
386 | ||
11efe71f SG |
387 | config LEDS_NS2 |
388 | tristate "LED support for Network Space v2 GPIO LEDs" | |
0bae35e1 | 389 | depends on LEDS_CLASS |
b12e2c12 | 390 | depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \ |
ecee1e47 SG |
391 | MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2 || \ |
392 | MACH_NETSPACE_V2_DT || MACH_INETSPACE_V2_DT || \ | |
7f9871d9 | 393 | MACH_NETSPACE_MAX_V2_DT || MACH_NETSPACE_MINI_V2_DT |
11efe71f SG |
394 | default y |
395 | help | |
396 | This option enable support for the dual-GPIO LED found on the | |
397 | Network Space v2 board (and parents). This include Internet Space v2, | |
398 | Network Space (Max) v2 and d2 Network v2 boards. | |
399 | ||
24467832 SG |
400 | config LEDS_NETXBIG |
401 | tristate "LED support for Big Network series LEDs" | |
402 | depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2 | |
2504f6da | 403 | depends on LEDS_CLASS |
24467832 SG |
404 | default y |
405 | help | |
406 | This option enable support for LEDs found on the LaCie 2Big | |
407 | and 5Big Network v2 boards. The LEDs are wired to a CPLD and are | |
408 | controlled through a GPIO extension bus. | |
409 | ||
7d9e7e9f PP |
410 | config LEDS_ASIC3 |
411 | bool "LED support for the HTC ASIC3" | |
9473c4c1 | 412 | depends on LEDS_CLASS=y |
7d9e7e9f PP |
413 | depends on MFD_ASIC3 |
414 | default y | |
415 | help | |
416 | This option enables support for the LEDs on the HTC ASIC3. The HTC | |
417 | ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver | |
418 | cannot be used. This driver supports hardware blinking with an on+off | |
419 | period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700. | |
420 | ||
f59b6f9f MD |
421 | config LEDS_RENESAS_TPU |
422 | bool "LED support for Renesas TPU" | |
9473c4c1 | 423 | depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO |
f59b6f9f MD |
424 | help |
425 | This option enables build of the LED TPU platform driver, | |
426 | suitable to drive any TPU channel on newer Renesas SoCs. | |
427 | The driver controls the GPIO pin connected to the LED via | |
428 | the GPIO framework and expects the LED to be connected to | |
429 | a pin that can be driven in both GPIO mode and using TPU | |
430 | pin function. The latter to support brightness control. | |
431 | Brightness control is supported but hardware blinking is not. | |
432 | ||
a6d511e5 N |
433 | config LEDS_TCA6507 |
434 | tristate "LED Support for TCA6507 I2C chip" | |
435 | depends on LEDS_CLASS && I2C | |
436 | help | |
437 | This option enables support for LEDs connected to TC6507 | |
438 | LED driver chips accessed via the I2C bus. | |
439 | Driver support brightness control and hardware-assisted blinking. | |
440 | ||
8584cb82 DK |
441 | config LEDS_MAX8997 |
442 | tristate "LED support for MAX8997 PMIC" | |
443 | depends on LEDS_CLASS && MFD_MAX8997 | |
444 | help | |
445 | This option enables support for on-chip LED drivers on | |
446 | MAXIM MAX8997 PMIC. | |
447 | ||
b98d13c7 SJ |
448 | config LEDS_LM355x |
449 | tristate "LED support for LM355x Chips, LM3554 and LM3556" | |
32abb478 SJ |
450 | depends on LEDS_CLASS && I2C |
451 | select REGMAP_I2C | |
452 | help | |
b98d13c7 SJ |
453 | This option enables support for LEDs connected to LM355x. |
454 | LM355x includes Torch, Flash and Indicator functions. | |
32abb478 | 455 | |
e9a4593c SAS |
456 | config LEDS_OT200 |
457 | tristate "LED support for the Bachmann OT200" | |
458 | depends on LEDS_CLASS && HAS_IOMEM | |
459 | help | |
460 | This option enables support for the LEDs on the Bachmann OT200. | |
461 | Say Y to enable LEDs on the Bachmann OT200. | |
462 | ||
b54cf35a JSM |
463 | config LEDS_BLINKM |
464 | tristate "LED support for the BlinkM I2C RGB LED" | |
465 | depends on LEDS_CLASS | |
466 | depends on I2C | |
467 | help | |
468 | This option enables support for the BlinkM RGB LED connected | |
469 | through I2C. Say Y to enable support for the BlinkM LED. | |
470 | ||
24f51e81 BD |
471 | config LEDS_TRIGGERS |
472 | bool "LED Trigger support" | |
0bae35e1 | 473 | depends on LEDS_CLASS |
24f51e81 BD |
474 | help |
475 | This option enables trigger support for the leds class. | |
476 | These triggers allow kernel events to drive the LEDs and can | |
477 | be configured via sysfs. If unsure, say Y. | |
478 | ||
d09e1666 HS |
479 | comment "LED Triggers" |
480 | ||
6655c6fe RP |
481 | config LEDS_TRIGGER_TIMER |
482 | tristate "LED Timer Trigger" | |
0bae35e1 | 483 | depends on LEDS_TRIGGERS |
6655c6fe RP |
484 | help |
485 | This allows LEDs to be controlled by a programmable timer | |
4c79141d MN |
486 | via sysfs. Some LED hardware can be programmed to start |
487 | blinking the LED without any further software interaction. | |
395cf969 | 488 | For more details read Documentation/leds/leds-class.txt. |
4c79141d MN |
489 | |
490 | If unsure, say Y. | |
6655c6fe | 491 | |
5e417281 FB |
492 | config LEDS_TRIGGER_ONESHOT |
493 | tristate "LED One-shot Trigger" | |
494 | depends on LEDS_TRIGGERS | |
495 | help | |
496 | This allows LEDs to blink in one-shot pulses with parameters | |
497 | controlled via sysfs. It's useful to notify the user on | |
498 | sporadic events, when there are no clear begin and end trap points, | |
499 | or on dense events, where this blinks the LED at constant rate if | |
500 | rearmed continuously. | |
501 | ||
502 | It also shows how to use the led_blink_set_oneshot() function. | |
503 | ||
504 | If unsure, say Y. | |
505 | ||
2bfb646c | 506 | config LEDS_TRIGGER_IDE_DISK |
baa351ea | 507 | bool "LED IDE Disk Trigger" |
d09e1666 | 508 | depends on IDE_GD_ATA |
0bae35e1 | 509 | depends on LEDS_TRIGGERS |
2bfb646c RP |
510 | help |
511 | This allows LEDs to be controlled by IDE disk activity. | |
512 | If unsure, say Y. | |
513 | ||
891c668b AN |
514 | config LEDS_TRIGGER_HEARTBEAT |
515 | tristate "LED Heartbeat Trigger" | |
0bae35e1 | 516 | depends on LEDS_TRIGGERS |
891c668b AN |
517 | help |
518 | This allows LEDs to be controlled by a CPU load average. | |
519 | The flash frequency is a hyperbolic function of the 1-minute | |
520 | load average. | |
521 | If unsure, say Y. | |
522 | ||
132e9306 RG |
523 | config LEDS_TRIGGER_BACKLIGHT |
524 | tristate "LED backlight Trigger" | |
0bae35e1 | 525 | depends on LEDS_TRIGGERS |
132e9306 RG |
526 | help |
527 | This allows LEDs to be controlled as a backlight device: they | |
528 | turn off and on when the display is blanked and unblanked. | |
529 | ||
530 | If unsure, say N. | |
531 | ||
8f88731d BW |
532 | config LEDS_TRIGGER_CPU |
533 | bool "LED CPU Trigger" | |
534 | depends on LEDS_TRIGGERS | |
535 | help | |
536 | This allows LEDs to be controlled by active CPUs. This shows | |
537 | the active CPUs across an array of LEDs so you can see which | |
538 | CPUs are active on the system at any given moment. | |
539 | ||
540 | If unsure, say N. | |
541 | ||
17354bfe FB |
542 | config LEDS_TRIGGER_GPIO |
543 | tristate "LED GPIO Trigger" | |
0bae35e1 | 544 | depends on LEDS_TRIGGERS |
17354bfe FB |
545 | depends on GPIOLIB |
546 | help | |
547 | This allows LEDs to be controlled by gpio events. It's good | |
548 | when using gpios as switches and triggering the needed LEDs | |
549 | from there. One use case is n810's keypad LEDs that could | |
550 | be triggered by this trigger when user slides up to show | |
551 | keypad. | |
552 | ||
553 | If unsure, say N. | |
554 | ||
060856c7 NF |
555 | config LEDS_TRIGGER_DEFAULT_ON |
556 | tristate "LED Default ON Trigger" | |
0bae35e1 | 557 | depends on LEDS_TRIGGERS |
060856c7 NF |
558 | help |
559 | This allows LEDs to be initialised in the ON state. | |
560 | If unsure, say Y. | |
561 | ||
268cb38e AN |
562 | comment "iptables trigger is under Netfilter config (LED target)" |
563 | depends on LEDS_TRIGGERS | |
564 | ||
44e1e9f8 SK |
565 | config LEDS_TRIGGER_TRANSIENT |
566 | tristate "LED Transient Trigger" | |
567 | depends on LEDS_TRIGGERS | |
568 | help | |
569 | This allows one time activation of a transient state on | |
dff67758 | 570 | GPIO/PWM based hardware. |
44e1e9f8 SK |
571 | If unsure, say Y. |
572 | ||
66242f7e | 573 | endif # NEW_LEDS |