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
13 bool "LED Class Support"
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.
23 tristate "LED Support for Marvell 88PM860x PMIC"
24 depends on MFD_88PM860X
26 This option enables support for on-chip LED drivers found on Marvell
27 Semiconductor 88PM8606 PMIC.
30 tristate "LED Support using Atmel PWM outputs"
33 This option enables support for LEDs driven using outputs
34 of the dedicated PWM controller found on newer Atmel SOCs.
37 tristate "LED Support for Locomo device"
38 depends on SHARP_LOCOMO
40 This option enables support for the LEDs on Sharp Locomo.
41 Zaurus models SL-5500 and SL-5600.
43 config LEDS_MIKROTIK_RB532
44 tristate "LED Support for Mikrotik Routerboard 532"
45 depends on MIKROTIK_RB532
47 This option enables support for the so called "User LED" of
48 Mikrotik's Routerboard 532.
51 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
52 depends on ARCH_S3C2410
54 This option enables support for LEDs connected to GPIO lines
55 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
58 tristate "LED Support for the Amstrad Delta (E3)"
59 depends on MACH_AMS_DELTA
61 This option enables support for the LEDs on Amstrad Delta (E3).
64 tristate "LED Support for Soekris net48xx series Error LED"
65 depends on SCx200_GPIO
67 This option enables support for the Soekris net4801 and net4826 error
71 tristate "LED Support for Soekris net5501 series Error LED"
72 depends on LEDS_TRIGGERS
73 depends on X86 && LEDS_GPIO_PLATFORM && GPIO_CS5535
74 select LEDS_TRIGGER_DEFAULT_ON
77 Add support for the Soekris net5501 board (detection, error led
81 tristate "LED Support for the Freecom FSG-3"
84 This option enables support for the LEDs on the Freecom FSG-3.
87 tristate "LED Support for the WRAP series LEDs"
88 depends on SCx200_GPIO
90 This option enables support for the PCEngines WRAP programmable LEDs.
93 tristate "LED Support for ALIX.2 and ALIX.3 series"
94 depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
96 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
97 You have to set leds-alix2.force=1 for boards with Award BIOS.
100 tristate "LED Support for iPAQ H1940 device"
101 depends on ARCH_H1940
103 This option enables support for the LEDs on the h1940.
105 config LEDS_COBALT_QUBE
106 tristate "LED Support for the Cobalt Qube series front LED"
107 depends on MIPS_COBALT
109 This option enables support for the front LED on Cobalt Qube series
111 config LEDS_COBALT_RAQ
112 bool "LED Support for the Cobalt Raq series"
113 depends on LEDS_CLASS=y && MIPS_COBALT
116 This option enables support for the Cobalt Raq series LEDs.
119 tristate "LED support for SunFire servers."
123 This option enables support for the Left, Middle, and Right
124 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
127 tristate "LED Support for the HP Jornada 6xx"
130 This option enables LED support for the handheld
131 HP Jornada 620/660/680/690.
134 tristate "LED driver for PCA9532 dimmer"
135 depends on I2C && INPUT && EXPERIMENTAL
137 This option enables support for NXP pca9532
138 LED controller. It is generally only useful
142 tristate "LED Support for GPIO connected LEDs"
143 depends on GENERIC_GPIO
145 This option enables support for the LEDs connected to GPIO
146 outputs. To be useful the particular board must have LEDs
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.
151 config LEDS_GPIO_PLATFORM
152 bool "Platform device bindings for GPIO LEDs"
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.
160 bool "OpenFirmware platform device bindings for GPIO LEDs"
161 depends on LEDS_GPIO && OF_DEVICE
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"
169 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
172 This option enables support for LEDs connected to the National
173 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
176 To compile this driver as a module, choose M here: the
177 module will be called leds-lp3944.
180 tristate "LED Support for N.S. LP5521 LED driver chip"
181 depends on LEDS_CLASS && I2C
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.
189 tristate "LED Support for N.S. LP5523 LED driver chip"
190 depends on LEDS_CLASS && I2C
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.
197 config LEDS_CLEVO_MAIL
198 tristate "Mail LED on Clevo notebook"
199 depends on X86 && SERIO_I8042 && DMI
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.
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
211 This module can drive the mail LED for the following notebooks:
216 Clevo D400V/D470V (not tested, but might work)
218 Clevo M5x0N (not tested, but might work)
219 Positivo Mobile (Clevo M5x0V)
221 If your model is not listed here you can try the "nodetect"
224 To compile this driver as a module, choose M here: the
225 module will be called leds-clevo-mail.
228 tristate "LED Support for PCA955x I2C chips"
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.
235 config LEDS_WM831X_STATUS
236 tristate "LED support for status LEDs on WM831x PMICs"
237 depends on MFD_WM831X
239 This option enables support for the status LEDs of the WM831x
243 tristate "LED Support for WM8350 AudioPlus PMIC"
244 depends on MFD_WM8350
246 This option enables support for LEDs driven by the Wolfson
247 Microelectronics WM8350 AudioPlus PMIC.
250 tristate "LED Support for DA9030/DA9034 PMIC"
251 depends on PMIC_DA903X
253 This option enables support for on-chip LED drivers found
254 on Dialog Semiconductor DA9030/DA9034 PMICs.
256 config LEDS_DAC124S085
257 tristate "LED Support for DAC124S085 SPI DAC"
260 This option enables support for DAC124S085 SPI DAC from NatSemi,
261 which can be used to control up to four LEDs.
264 tristate "PWM driven LED Support"
267 This option enables support for pwm driven LEDs
269 config LEDS_REGULATOR
270 tristate "REGULATOR driven LED support"
273 This option enables support for regulator driven LEDs.
276 tristate "LED driver for BD2802 RGB LED"
279 This option enables support for BD2802GU RGB LED driver chips
280 accessed via the I2C bus.
282 config LEDS_INTEL_SS4200
283 tristate "LED driver for Intel NAS SS4200 series"
284 depends on PCI && DMI
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.
292 tristate "LED driver for LT3593 controllers"
293 depends on GENERIC_GPIO
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.
300 tristate "LED Support for ADP5520/ADP5501 PMIC"
301 depends on PMIC_ADP5520
303 This option enables support for on-chip LED drivers found
304 on Analog Devices ADP5520/ADP5501 PMICs.
306 To compile this driver as a module, choose M here: the module will
307 be called leds-adp5520.
309 config LEDS_DELL_NETBOOKS
310 tristate "External LED on Dell Business Netbooks"
311 depends on X86 && ACPI_WMI
313 This adds support for the Latitude 2100 and similar
314 notebooks that have an external LED.
317 tristate "LED Support for MC13783 PMIC"
318 depends on MFD_MC13783
320 This option enable support for on-chip LED drivers found
321 on Freescale Semiconductor MC13783 PMIC.
324 tristate "LED support for Network Space v2 GPIO LEDs"
325 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
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.
333 tristate "LED support for Big Network series LEDs"
334 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
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.
342 bool "LED Trigger support"
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.
350 comment "LED Triggers"
352 config LEDS_TRIGGER_TIMER
353 tristate "LED Timer Trigger"
355 This allows LEDs to be controlled by a programmable timer
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.
362 config LEDS_TRIGGER_IDE_DISK
363 bool "LED IDE Disk Trigger"
364 depends on IDE_GD_ATA
366 This allows LEDs to be controlled by IDE disk activity.
369 config LEDS_TRIGGER_HEARTBEAT
370 tristate "LED Heartbeat Trigger"
372 This allows LEDs to be controlled by a CPU load average.
373 The flash frequency is a hyperbolic function of the 1-minute
377 config LEDS_TRIGGER_BACKLIGHT
378 tristate "LED backlight Trigger"
380 This allows LEDs to be controlled as a backlight device: they
381 turn off and on when the display is blanked and unblanked.
385 config LEDS_TRIGGER_GPIO
386 tristate "LED GPIO Trigger"
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
397 config LEDS_TRIGGER_DEFAULT_ON
398 tristate "LED Default ON Trigger"
400 This allows LEDs to be initialised in the ON state.
403 comment "iptables trigger is under Netfilter config (LED target)"
404 depends on LEDS_TRIGGERS
406 endif # LEDS_TRIGGERS