4 Say Y to enable Linux LED support. This allows control of supported
5 LEDs from both userspace and optionally, by kernel events (triggers).
7 This is not related to standard keyboard LEDs which are controlled
11 bool "LED Class Support"
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.
17 config LEDS_GPIO_REGISTER
20 This option provides the function gpio_led_register_device.
21 As this function is used by arch code it must not be compiled as a
29 tristate "LED Support for Marvell 88PM860x PMIC"
31 depends on MFD_88PM860X
33 This option enables support for on-chip LED drivers found on Marvell
34 Semiconductor 88PM8606 PMIC.
37 tristate "LED Support using Atmel PWM outputs"
41 This option enables support for LEDs driven using outputs
42 of the dedicated PWM controller found on newer Atmel SOCs.
45 tristate "LCD Backlight driver for LM3530"
49 This option enables support for the LCD backlight using
50 LM3530 ambient light sensor chip. This ALS chip can be
51 controlled manually or using PWM input or using ambient
55 tristate "LED Support for Locomo device"
57 depends on SHARP_LOCOMO
59 This option enables support for the LEDs on Sharp Locomo.
60 Zaurus models SL-5500 and SL-5600.
62 config LEDS_MIKROTIK_RB532
63 tristate "LED Support for Mikrotik Routerboard 532"
65 depends on MIKROTIK_RB532
67 This option enables support for the so called "User LED" of
68 Mikrotik's Routerboard 532.
71 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
73 depends on ARCH_S3C2410
75 This option enables support for LEDs connected to GPIO lines
76 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
79 tristate "LED Support for the Amstrad Delta (E3)"
81 depends on MACH_AMS_DELTA
83 This option enables support for the LEDs on Amstrad Delta (E3).
86 tristate "LED Support for Soekris net48xx series Error LED"
88 depends on SCx200_GPIO
90 This option enables support for the Soekris net4801 and net4826 error
94 tristate "LED Support for Soekris net5501 series Error LED"
95 depends on LEDS_TRIGGERS
96 depends on X86 && GPIO_CS5535
97 select LEDS_TRIGGER_DEFAULT_ON
100 Add support for the Soekris net5501 board (detection, error led
104 tristate "LED Support for the Freecom FSG-3"
105 depends on LEDS_CLASS
108 This option enables support for the LEDs on the Freecom FSG-3.
111 tristate "LED Support for the WRAP series LEDs"
112 depends on LEDS_CLASS
113 depends on SCx200_GPIO
115 This option enables support for the PCEngines WRAP programmable LEDs.
118 tristate "LED Support for ALIX.2 and ALIX.3 series"
119 depends on LEDS_CLASS
120 depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
122 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
123 You have to set leds-alix2.force=1 for boards with Award BIOS.
125 config LEDS_COBALT_QUBE
126 tristate "LED Support for the Cobalt Qube series front LED"
127 depends on LEDS_CLASS
128 depends on MIPS_COBALT
130 This option enables support for the front LED on Cobalt Qube series
132 config LEDS_COBALT_RAQ
133 bool "LED Support for the Cobalt Raq series"
134 depends on LEDS_CLASS=y && MIPS_COBALT
137 This option enables support for the Cobalt Raq series LEDs.
140 tristate "LED support for SunFire servers."
141 depends on LEDS_CLASS
145 This option enables support for the Left, Middle, and Right
146 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
149 tristate "LED Support for the HP Jornada 6xx"
150 depends on LEDS_CLASS
153 This option enables LED support for the handheld
154 HP Jornada 620/660/680/690.
157 tristate "LED driver for PCA9532 dimmer"
158 depends on LEDS_CLASS
159 depends on I2C && INPUT && EXPERIMENTAL
161 This option enables support for NXP pca9532
162 LED controller. It is generally only useful
165 config LEDS_PCA9532_GPIO
166 bool "Enable GPIO support for PCA9532"
167 depends on LEDS_PCA9532
170 Allow unused pins on PCA9532 to be used as gpio.
172 To use a pin as gpio pca9532_type in pca9532_platform data needs to
173 set to PCA9532_TYPE_GPIO.
176 tristate "LED Support for GPIO connected LEDs"
177 depends on LEDS_CLASS
178 depends on GENERIC_GPIO
180 This option enables support for the LEDs connected to GPIO
181 outputs. To be useful the particular board must have LEDs
182 and they must be connected to the GPIO lines. The LEDs must be
183 defined as platform devices and/or OpenFirmware platform devices.
184 The code to use these bindings can be selected below.
187 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
188 depends on LEDS_CLASS
191 This option enables support for LEDs connected to the National
192 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
195 To compile this driver as a module, choose M here: the
196 module will be called leds-lp3944.
199 tristate "LED Support for N.S. LP5521 LED driver chip"
200 depends on LEDS_CLASS && I2C
202 If you say yes here you get support for the National Semiconductor
203 LP5521 LED driver. It is 3 channel chip with programmable engines.
204 Driver provides direct control via LED class and interface for
205 programming the engines.
208 tristate "LED Support for N.S. LP5523 LED driver chip"
209 depends on LEDS_CLASS && I2C
211 If you say yes here you get support for the National Semiconductor
212 LP5523 LED driver. It is 9 channel chip with programmable engines.
213 Driver provides direct control via LED class and interface for
214 programming the engines.
216 config LEDS_CLEVO_MAIL
217 tristate "Mail LED on Clevo notebook"
218 depends on LEDS_CLASS
219 depends on X86 && SERIO_I8042 && DMI
221 This driver makes the mail LED accessible from userspace
222 programs through the leds subsystem. This LED have three
223 known mode: off, blink at 0.5Hz and blink at 1Hz.
225 The driver supports two kinds of interface: using ledtrig-timer
226 or through /sys/class/leds/clevo::mail/brightness. As this LED
227 cannot change it's brightness it blinks instead. The brightness
228 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
231 This module can drive the mail LED for the following notebooks:
236 Clevo D400V/D470V (not tested, but might work)
238 Clevo M5x0N (not tested, but might work)
239 Positivo Mobile (Clevo M5x0V)
241 If your model is not listed here you can try the "nodetect"
244 To compile this driver as a module, choose M here: the
245 module will be called leds-clevo-mail.
248 tristate "LED Support for PCA955x I2C chips"
249 depends on LEDS_CLASS
252 This option enables support for LEDs connected to PCA955x
253 LED driver chips accessed via the I2C bus. Supported
254 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
256 config LEDS_WM831X_STATUS
257 tristate "LED support for status LEDs on WM831x PMICs"
258 depends on LEDS_CLASS
259 depends on MFD_WM831X
261 This option enables support for the status LEDs of the WM831x
265 tristate "LED Support for WM8350 AudioPlus PMIC"
266 depends on LEDS_CLASS
267 depends on MFD_WM8350
269 This option enables support for LEDs driven by the Wolfson
270 Microelectronics WM8350 AudioPlus PMIC.
273 tristate "LED Support for DA9030/DA9034 PMIC"
274 depends on LEDS_CLASS
275 depends on PMIC_DA903X
277 This option enables support for on-chip LED drivers found
278 on Dialog Semiconductor DA9030/DA9034 PMICs.
280 config LEDS_DAC124S085
281 tristate "LED Support for DAC124S085 SPI DAC"
282 depends on LEDS_CLASS
285 This option enables support for DAC124S085 SPI DAC from NatSemi,
286 which can be used to control up to four LEDs.
289 tristate "PWM driven LED Support"
290 depends on LEDS_CLASS
293 This option enables support for pwm driven LEDs
295 config LEDS_REGULATOR
296 tristate "REGULATOR driven LED support"
297 depends on LEDS_CLASS
300 This option enables support for regulator driven LEDs.
303 tristate "LED driver for BD2802 RGB LED"
304 depends on LEDS_CLASS
307 This option enables support for BD2802GU RGB LED driver chips
308 accessed via the I2C bus.
310 config LEDS_INTEL_SS4200
311 tristate "LED driver for Intel NAS SS4200 series"
312 depends on LEDS_CLASS
313 depends on PCI && DMI
315 This option enables support for the Intel SS4200 series of
316 Network Attached Storage servers. You may control the hard
317 drive or power LEDs on the front panel. Using this driver
318 can stop the front LED from blinking after startup.
321 tristate "LED driver for LT3593 controllers"
322 depends on LEDS_CLASS
323 depends on GENERIC_GPIO
325 This option enables support for LEDs driven by a Linear Technology
326 LT3593 controller. This controller uses a special one-wire pulse
327 coding protocol to set the brightness.
330 tristate "LED Support for ADP5520/ADP5501 PMIC"
331 depends on LEDS_CLASS
332 depends on PMIC_ADP5520
334 This option enables support for on-chip LED drivers found
335 on Analog Devices ADP5520/ADP5501 PMICs.
337 To compile this driver as a module, choose M here: the module will
338 be called leds-adp5520.
340 config LEDS_DELL_NETBOOKS
341 tristate "External LED on Dell Business Netbooks"
342 depends on LEDS_CLASS
343 depends on X86 && ACPI_WMI
345 This adds support for the Latitude 2100 and similar
346 notebooks that have an external LED.
349 tristate "LED Support for MC13783 PMIC"
350 depends on LEDS_CLASS
351 depends on MFD_MC13783
353 This option enable support for on-chip LED drivers found
354 on Freescale Semiconductor MC13783 PMIC.
357 tristate "LED support for Network Space v2 GPIO LEDs"
358 depends on LEDS_CLASS
359 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
362 This option enable support for the dual-GPIO LED found on the
363 Network Space v2 board (and parents). This include Internet Space v2,
364 Network Space (Max) v2 and d2 Network v2 boards.
367 tristate "LED support for Big Network series LEDs"
368 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
371 This option enable support for LEDs found on the LaCie 2Big
372 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
373 controlled through a GPIO extension bus.
376 bool "LED support for the HTC ASIC3"
380 This option enables support for the LEDs on the HTC ASIC3. The HTC
381 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
382 cannot be used. This driver supports hardware blinking with an on+off
383 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
386 bool "LED Trigger support"
387 depends on LEDS_CLASS
389 This option enables trigger support for the leds class.
390 These triggers allow kernel events to drive the LEDs and can
391 be configured via sysfs. If unsure, say Y.
393 comment "LED Triggers"
395 config LEDS_TRIGGER_TIMER
396 tristate "LED Timer Trigger"
397 depends on LEDS_TRIGGERS
399 This allows LEDs to be controlled by a programmable timer
400 via sysfs. Some LED hardware can be programmed to start
401 blinking the LED without any further software interaction.
402 For more details read Documentation/leds-class.txt.
406 config LEDS_TRIGGER_IDE_DISK
407 bool "LED IDE Disk Trigger"
408 depends on IDE_GD_ATA
409 depends on LEDS_TRIGGERS
411 This allows LEDs to be controlled by IDE disk activity.
414 config LEDS_TRIGGER_HEARTBEAT
415 tristate "LED Heartbeat Trigger"
416 depends on LEDS_TRIGGERS
418 This allows LEDs to be controlled by a CPU load average.
419 The flash frequency is a hyperbolic function of the 1-minute
423 config LEDS_TRIGGER_BACKLIGHT
424 tristate "LED backlight Trigger"
425 depends on LEDS_TRIGGERS
427 This allows LEDs to be controlled as a backlight device: they
428 turn off and on when the display is blanked and unblanked.
432 config LEDS_TRIGGER_GPIO
433 tristate "LED GPIO Trigger"
434 depends on LEDS_TRIGGERS
437 This allows LEDs to be controlled by gpio events. It's good
438 when using gpios as switches and triggering the needed LEDs
439 from there. One use case is n810's keypad LEDs that could
440 be triggered by this trigger when user slides up to show
445 config LEDS_TRIGGER_DEFAULT_ON
446 tristate "LED Default ON Trigger"
447 depends on LEDS_TRIGGERS
449 This allows LEDs to be initialised in the ON state.
452 comment "iptables trigger is under Netfilter config (LED target)"
453 depends on LEDS_TRIGGERS