]>
Commit | Line | Data |
---|---|---|
66242f7e | 1 | menuconfig NEW_LEDS |
c72a1d60 RP |
2 | bool "LED Support" |
3 | help | |
a8d2e7d9 RP |
4 | Say Y to enable Linux LED support. This allows control of supported |
5 | LEDs from both userspace and optionally, by kernel events (triggers). | |
6 | ||
7 | This is not related to standard keyboard LEDs which are controlled | |
8 | via the input system. | |
c72a1d60 | 9 | |
66242f7e JE |
10 | if NEW_LEDS |
11 | ||
c72a1d60 | 12 | config LEDS_CLASS |
5ada28bf | 13 | bool "LED Class Support" |
c72a1d60 RP |
14 | help |
15 | This option enables the led sysfs class in /sys/class/leds. You'll | |
16 | need this to do anything useful with LEDs. If unsure, say N. | |
17 | ||
d09e1666 HS |
18 | if LEDS_CLASS |
19 | ||
24f51e81 | 20 | comment "LED drivers" |
c3bc9956 | 21 | |
0a2f915b HZ |
22 | config LEDS_88PM860X |
23 | tristate "LED Support for Marvell 88PM860x PMIC" | |
37814fdc | 24 | depends on MFD_88PM860X |
0a2f915b HZ |
25 | help |
26 | This option enables support for on-chip LED drivers found on Marvell | |
27 | Semiconductor 88PM8606 PMIC. | |
28 | ||
de5c9ede DB |
29 | config LEDS_ATMEL_PWM |
30 | tristate "LED Support using Atmel PWM outputs" | |
d09e1666 | 31 | depends on ATMEL_PWM |
de5c9ede DB |
32 | help |
33 | This option enables support for LEDs driven using outputs | |
34 | of the dedicated PWM controller found on newer Atmel SOCs. | |
35 | ||
4d3cb354 RP |
36 | config LEDS_LOCOMO |
37 | tristate "LED Support for Locomo device" | |
d09e1666 | 38 | depends on SHARP_LOCOMO |
4d3cb354 RP |
39 | help |
40 | This option enables support for the LEDs on Sharp Locomo. | |
41 | Zaurus models SL-5500 and SL-5600. | |
42 | ||
ac67e23b PS |
43 | config LEDS_MIKROTIK_RB532 |
44 | tristate "LED Support for Mikrotik Routerboard 532" | |
d09e1666 | 45 | depends on MIKROTIK_RB532 |
ac67e23b PS |
46 | help |
47 | This option enables support for the so called "User LED" of | |
48 | Mikrotik's Routerboard 532. | |
49 | ||
54bdc470 BD |
50 | config LEDS_S3C24XX |
51 | tristate "LED Support for Samsung S3C24XX GPIO LEDs" | |
d09e1666 | 52 | depends on ARCH_S3C2410 |
54bdc470 BD |
53 | help |
54 | This option enables support for LEDs connected to GPIO lines | |
55 | on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440. | |
56 | ||
9becde79 JM |
57 | config LEDS_AMS_DELTA |
58 | tristate "LED Support for the Amstrad Delta (E3)" | |
d09e1666 | 59 | depends on MACH_AMS_DELTA |
9becde79 JM |
60 | help |
61 | This option enables support for the LEDs on Amstrad Delta (E3). | |
62 | ||
1a87d942 CB |
63 | config LEDS_NET48XX |
64 | tristate "LED Support for Soekris net48xx series Error LED" | |
d09e1666 | 65 | depends on SCx200_GPIO |
1a87d942 CB |
66 | help |
67 | This option enables support for the Soekris net4801 and net4826 error | |
68 | LED. | |
69 | ||
14e40f64 BIP |
70 | config LEDS_NET5501 |
71 | tristate "LED Support for Soekris net5501 series Error LED" | |
37814fdc RP |
72 | depends on LEDS_TRIGGERS |
73 | depends on X86 && LEDS_GPIO_PLATFORM && GPIO_CS5535 | |
14e40f64 BIP |
74 | select LEDS_TRIGGER_DEFAULT_ON |
75 | default n | |
76 | help | |
77 | Add support for the Soekris net5501 board (detection, error led | |
78 | and GPIO). | |
79 | ||
3b2e46f8 RW |
80 | config LEDS_FSG |
81 | tristate "LED Support for the Freecom FSG-3" | |
d09e1666 | 82 | depends on MACH_FSG |
3b2e46f8 RW |
83 | help |
84 | This option enables support for the LEDs on the Freecom FSG-3. | |
85 | ||
0d75565f KK |
86 | config LEDS_WRAP |
87 | tristate "LED Support for the WRAP series LEDs" | |
d09e1666 | 88 | depends on SCx200_GPIO |
0d75565f KK |
89 | help |
90 | This option enables support for the PCEngines WRAP programmable LEDs. | |
91 | ||
ec9a943c CB |
92 | config LEDS_ALIX2 |
93 | tristate "LED Support for ALIX.2 and ALIX.3 series" | |
d09e1666 | 94 | depends on X86 && !GPIO_CS5535 && !CS5535_GPIO |
ec9a943c CB |
95 | help |
96 | This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs. | |
2216c6e8 | 97 | You have to set leds-alix2.force=1 for boards with Award BIOS. |
ec9a943c | 98 | |
bd4009af AP |
99 | config LEDS_H1940 |
100 | tristate "LED Support for iPAQ H1940 device" | |
d09e1666 | 101 | depends on ARCH_H1940 |
bd4009af AP |
102 | help |
103 | This option enables support for the LEDs on the h1940. | |
104 | ||
f3b6b6cd YY |
105 | config LEDS_COBALT_QUBE |
106 | tristate "LED Support for the Cobalt Qube series front LED" | |
d09e1666 | 107 | depends on MIPS_COBALT |
2fea6f35 | 108 | help |
f3b6b6cd | 109 | This option enables support for the front LED on Cobalt Qube series |
2fea6f35 | 110 | |
97da7aaf YY |
111 | config LEDS_COBALT_RAQ |
112 | bool "LED Support for the Cobalt Raq series" | |
ec149619 | 113 | depends on LEDS_CLASS=y && MIPS_COBALT |
97da7aaf YY |
114 | select LEDS_TRIGGERS |
115 | help | |
116 | This option enables support for the Cobalt Raq series LEDs. | |
117 | ||
5843492c DM |
118 | config LEDS_SUNFIRE |
119 | tristate "LED support for SunFire servers." | |
d09e1666 | 120 | depends on SPARC64 |
5843492c DM |
121 | select LEDS_TRIGGERS |
122 | help | |
123 | This option enables support for the Left, Middle, and Right | |
124 | LEDs on the I/O and CPU boards of SunFire UltraSPARC servers. | |
125 | ||
d39a7a63 KE |
126 | config LEDS_HP6XX |
127 | tristate "LED Support for the HP Jornada 6xx" | |
d09e1666 | 128 | depends on SH_HP6XX |
d39a7a63 | 129 | help |
692105b8 | 130 | This option enables LED support for the handheld |
d39a7a63 KE |
131 | HP Jornada 620/660/680/690. |
132 | ||
e14fa824 RV |
133 | config LEDS_PCA9532 |
134 | tristate "LED driver for PCA9532 dimmer" | |
d09e1666 | 135 | depends on I2C && INPUT && EXPERIMENTAL |
e14fa824 RV |
136 | help |
137 | This option enables support for NXP pca9532 | |
692105b8 | 138 | LED controller. It is generally only useful |
e14fa824 RV |
139 | as a platform driver |
140 | ||
22e03f3b RA |
141 | config LEDS_GPIO |
142 | tristate "LED Support for GPIO connected LEDs" | |
d09e1666 | 143 | depends on GENERIC_GPIO |
22e03f3b RA |
144 | help |
145 | This option enables support for the LEDs connected to GPIO | |
146 | outputs. To be useful the particular board must have LEDs | |
a7d878af TP |
147 | and they must be connected to the GPIO lines. The LEDs must be |
148 | defined as platform devices and/or OpenFirmware platform devices. | |
149 | The code to use these bindings can be selected below. | |
150 | ||
151 | config LEDS_GPIO_PLATFORM | |
152 | bool "Platform device bindings for GPIO LEDs" | |
153 | depends on LEDS_GPIO | |
154 | default y | |
155 | help | |
156 | Let the leds-gpio driver drive LEDs which have been defined as | |
157 | platform devices. If you don't know what this means, say yes. | |
158 | ||
159 | config LEDS_GPIO_OF | |
160 | bool "OpenFirmware platform device bindings for GPIO LEDs" | |
161 | depends on LEDS_GPIO && OF_DEVICE | |
162 | default y | |
163 | help | |
164 | Let the leds-gpio driver drive LEDs which have been defined as | |
165 | of_platform devices. For instance, LEDs which are listed in a "dts" | |
166 | file. | |
22e03f3b | 167 | |
5054d39e AO |
168 | config LEDS_LP3944 |
169 | tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip" | |
d09e1666 | 170 | depends on I2C |
5054d39e | 171 | help |
7f1be819 AO |
172 | This option enables support for LEDs connected to the National |
173 | Semiconductor LP3944 Lighting Management Unit (LMU) also known as | |
174 | Fun Light Chip. | |
5054d39e AO |
175 | |
176 | To compile this driver as a module, choose M here: the | |
177 | module will be called leds-lp3944. | |
178 | ||
f4920f67 SO |
179 | config LEDS_LP5521 |
180 | tristate "LED Support for N.S. LP5521 LED driver chip" | |
181 | depends on LEDS_CLASS && I2C | |
182 | help | |
183 | If you say yes here you get support for the National Semiconductor | |
184 | LP5521 LED driver. It is 3 channel chip with programmable engines. | |
185 | Driver provides direct control via LED class and interface for | |
186 | programming the engines. | |
187 | ||
188 | config LEDS_LP5523 | |
189 | tristate "LED Support for N.S. LP5523 LED driver chip" | |
190 | depends on LEDS_CLASS && I2C | |
191 | help | |
192 | If you say yes here you get support for the National Semiconductor | |
193 | LP5523 LED driver. It is 9 channel chip with programmable engines. | |
194 | Driver provides direct control via LED class and interface for | |
195 | programming the engines. | |
196 | ||
cec035de | 197 | config LEDS_CLEVO_MAIL |
95dc5768 | 198 | tristate "Mail LED on Clevo notebook" |
d09e1666 | 199 | depends on X86 && SERIO_I8042 && DMI |
cec035de MN |
200 | help |
201 | This driver makes the mail LED accessible from userspace | |
202 | programs through the leds subsystem. This LED have three | |
203 | known mode: off, blink at 0.5Hz and blink at 1Hz. | |
204 | ||
92e015cb MN |
205 | The driver supports two kinds of interface: using ledtrig-timer |
206 | or through /sys/class/leds/clevo::mail/brightness. As this LED | |
207 | cannot change it's brightness it blinks instead. The brightness | |
208 | value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means | |
209 | blink at 1Hz. | |
cec035de MN |
210 | |
211 | This module can drive the mail LED for the following notebooks: | |
212 | ||
b3ba31f8 | 213 | Clevo D400P |
cec035de MN |
214 | Clevo D410J |
215 | Clevo D410V | |
216 | Clevo D400V/D470V (not tested, but might work) | |
217 | Clevo M540N | |
218 | Clevo M5x0N (not tested, but might work) | |
219 | Positivo Mobile (Clevo M5x0V) | |
220 | ||
b3ba31f8 | 221 | If your model is not listed here you can try the "nodetect" |
692105b8 | 222 | module parameter. |
b3ba31f8 | 223 | |
cec035de MN |
224 | To compile this driver as a module, choose M here: the |
225 | module will be called leds-clevo-mail. | |
226 | ||
f46e9203 NC |
227 | config LEDS_PCA955X |
228 | tristate "LED Support for PCA955x I2C chips" | |
d09e1666 | 229 | depends on I2C |
f46e9203 NC |
230 | help |
231 | This option enables support for LEDs connected to PCA955x | |
232 | LED driver chips accessed via the I2C bus. Supported | |
233 | devices include PCA9550, PCA9551, PCA9552, and PCA9553. | |
234 | ||
c746b551 MB |
235 | config LEDS_WM831X_STATUS |
236 | tristate "LED support for status LEDs on WM831x PMICs" | |
d09e1666 | 237 | depends on MFD_WM831X |
c746b551 MB |
238 | help |
239 | This option enables support for the status LEDs of the WM831x | |
240 | series of PMICs. | |
241 | ||
0081e802 MB |
242 | config LEDS_WM8350 |
243 | tristate "LED Support for WM8350 AudioPlus PMIC" | |
d09e1666 | 244 | depends on MFD_WM8350 |
0081e802 MB |
245 | help |
246 | This option enables support for LEDs driven by the Wolfson | |
247 | Microelectronics WM8350 AudioPlus PMIC. | |
248 | ||
9e84561c MR |
249 | config LEDS_DA903X |
250 | tristate "LED Support for DA9030/DA9034 PMIC" | |
d09e1666 | 251 | depends on PMIC_DA903X |
9e84561c MR |
252 | help |
253 | This option enables support for on-chip LED drivers found | |
254 | on Dialog Semiconductor DA9030/DA9034 PMICs. | |
255 | ||
ac2dd0f1 GL |
256 | config LEDS_DAC124S085 |
257 | tristate "LED Support for DAC124S085 SPI DAC" | |
d09e1666 | 258 | depends on SPI |
ac2dd0f1 GL |
259 | help |
260 | This option enables support for DAC124S085 SPI DAC from NatSemi, | |
261 | which can be used to control up to four LEDs. | |
262 | ||
41c42ff5 LF |
263 | config LEDS_PWM |
264 | tristate "PWM driven LED Support" | |
d09e1666 | 265 | depends on HAVE_PWM |
41c42ff5 LF |
266 | help |
267 | This option enables support for pwm driven LEDs | |
268 | ||
d4cc6a2e AO |
269 | config LEDS_REGULATOR |
270 | tristate "REGULATOR driven LED support" | |
d09e1666 | 271 | depends on REGULATOR |
d4cc6a2e AO |
272 | help |
273 | This option enables support for regulator driven LEDs. | |
274 | ||
0b56129b KK |
275 | config LEDS_BD2802 |
276 | tristate "LED driver for BD2802 RGB LED" | |
d09e1666 | 277 | depends on I2C |
0b56129b KK |
278 | help |
279 | This option enables support for BD2802GU RGB LED driver chips | |
280 | accessed via the I2C bus. | |
281 | ||
a328e95b DH |
282 | config LEDS_INTEL_SS4200 |
283 | tristate "LED driver for Intel NAS SS4200 series" | |
d09e1666 | 284 | depends on PCI && DMI |
a328e95b DH |
285 | help |
286 | This option enables support for the Intel SS4200 series of | |
287 | Network Attached Storage servers. You may control the hard | |
288 | drive or power LEDs on the front panel. Using this driver | |
289 | can stop the front LED from blinking after startup. | |
290 | ||
a8dd18fe DM |
291 | config LEDS_LT3593 |
292 | tristate "LED driver for LT3593 controllers" | |
d09e1666 | 293 | depends on GENERIC_GPIO |
a8dd18fe DM |
294 | help |
295 | This option enables support for LEDs driven by a Linear Technology | |
296 | LT3593 controller. This controller uses a special one-wire pulse | |
297 | coding protocol to set the brightness. | |
298 | ||
ed4a10b4 MH |
299 | config LEDS_ADP5520 |
300 | tristate "LED Support for ADP5520/ADP5501 PMIC" | |
d09e1666 | 301 | depends on PMIC_ADP5520 |
ed4a10b4 MH |
302 | help |
303 | This option enables support for on-chip LED drivers found | |
304 | on Analog Devices ADP5520/ADP5501 PMICs. | |
305 | ||
306 | To compile this driver as a module, choose M here: the module will | |
307 | be called leds-adp5520. | |
308 | ||
72dcd8d0 BR |
309 | config LEDS_DELL_NETBOOKS |
310 | tristate "External LED on Dell Business Netbooks" | |
311 | depends on X86 && ACPI_WMI | |
312 | help | |
313 | This adds support for the Latitude 2100 and similar | |
314 | notebooks that have an external LED. | |
315 | ||
7fdcef8a PR |
316 | config LEDS_MC13783 |
317 | tristate "LED Support for MC13783 PMIC" | |
318 | depends on MFD_MC13783 | |
319 | help | |
320 | This option enable support for on-chip LED drivers found | |
321 | on Freescale Semiconductor MC13783 PMIC. | |
322 | ||
11efe71f SG |
323 | config LEDS_NS2 |
324 | tristate "LED support for Network Space v2 GPIO LEDs" | |
84712e9a | 325 | depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2 |
11efe71f SG |
326 | default y |
327 | help | |
328 | This option enable support for the dual-GPIO LED found on the | |
329 | Network Space v2 board (and parents). This include Internet Space v2, | |
330 | Network Space (Max) v2 and d2 Network v2 boards. | |
331 | ||
24467832 SG |
332 | config LEDS_NETXBIG |
333 | tristate "LED support for Big Network series LEDs" | |
334 | depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2 | |
335 | default y | |
336 | help | |
337 | This option enable support for LEDs found on the LaCie 2Big | |
338 | and 5Big Network v2 boards. The LEDs are wired to a CPLD and are | |
339 | controlled through a GPIO extension bus. | |
340 | ||
24f51e81 BD |
341 | config LEDS_TRIGGERS |
342 | bool "LED Trigger support" | |
24f51e81 BD |
343 | help |
344 | This option enables trigger support for the leds class. | |
345 | These triggers allow kernel events to drive the LEDs and can | |
346 | be configured via sysfs. If unsure, say Y. | |
347 | ||
d09e1666 HS |
348 | if LEDS_TRIGGERS |
349 | ||
350 | comment "LED Triggers" | |
351 | ||
6655c6fe RP |
352 | config LEDS_TRIGGER_TIMER |
353 | tristate "LED Timer Trigger" | |
6655c6fe RP |
354 | help |
355 | This allows LEDs to be controlled by a programmable timer | |
4c79141d MN |
356 | via sysfs. Some LED hardware can be programmed to start |
357 | blinking the LED without any further software interaction. | |
358 | For more details read Documentation/leds-class.txt. | |
359 | ||
360 | If unsure, say Y. | |
6655c6fe | 361 | |
2bfb646c | 362 | config LEDS_TRIGGER_IDE_DISK |
baa351ea | 363 | bool "LED IDE Disk Trigger" |
d09e1666 | 364 | depends on IDE_GD_ATA |
2bfb646c RP |
365 | help |
366 | This allows LEDs to be controlled by IDE disk activity. | |
367 | If unsure, say Y. | |
368 | ||
891c668b AN |
369 | config LEDS_TRIGGER_HEARTBEAT |
370 | tristate "LED Heartbeat Trigger" | |
891c668b AN |
371 | help |
372 | This allows LEDs to be controlled by a CPU load average. | |
373 | The flash frequency is a hyperbolic function of the 1-minute | |
374 | load average. | |
375 | If unsure, say Y. | |
376 | ||
132e9306 RG |
377 | config LEDS_TRIGGER_BACKLIGHT |
378 | tristate "LED backlight Trigger" | |
132e9306 RG |
379 | help |
380 | This allows LEDs to be controlled as a backlight device: they | |
381 | turn off and on when the display is blanked and unblanked. | |
382 | ||
383 | If unsure, say N. | |
384 | ||
17354bfe FB |
385 | config LEDS_TRIGGER_GPIO |
386 | tristate "LED GPIO Trigger" | |
17354bfe FB |
387 | depends on GPIOLIB |
388 | help | |
389 | This allows LEDs to be controlled by gpio events. It's good | |
390 | when using gpios as switches and triggering the needed LEDs | |
391 | from there. One use case is n810's keypad LEDs that could | |
392 | be triggered by this trigger when user slides up to show | |
393 | keypad. | |
394 | ||
395 | If unsure, say N. | |
396 | ||
060856c7 NF |
397 | config LEDS_TRIGGER_DEFAULT_ON |
398 | tristate "LED Default ON Trigger" | |
060856c7 NF |
399 | help |
400 | This allows LEDs to be initialised in the ON state. | |
401 | If unsure, say Y. | |
402 | ||
268cb38e AN |
403 | comment "iptables trigger is under Netfilter config (LED target)" |
404 | depends on LEDS_TRIGGERS | |
405 | ||
d09e1666 HS |
406 | endif # LEDS_TRIGGERS |
407 | ||
408 | endif # LEDS_CLASS | |
409 | ||
66242f7e | 410 | endif # NEW_LEDS |