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