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.
22 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"
34 This option enables support for LEDs driven using outputs
35 of the dedicated PWM controller found on newer Atmel SOCs.
38 tristate "LCD Backlight driver for LM3530"
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
48 tristate "LED Support for Locomo device"
50 depends on SHARP_LOCOMO
52 This option enables support for the LEDs on Sharp Locomo.
53 Zaurus models SL-5500 and SL-5600.
55 config LEDS_MIKROTIK_RB532
56 tristate "LED Support for Mikrotik Routerboard 532"
58 depends on MIKROTIK_RB532
60 This option enables support for the so called "User LED" of
61 Mikrotik's Routerboard 532.
64 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
66 depends on ARCH_S3C2410
68 This option enables support for LEDs connected to GPIO lines
69 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
72 tristate "LED Support for the Amstrad Delta (E3)"
74 depends on MACH_AMS_DELTA
76 This option enables support for the LEDs on Amstrad Delta (E3).
79 tristate "LED Support for Soekris net48xx series Error LED"
81 depends on SCx200_GPIO
83 This option enables support for the Soekris net4801 and net4826 error
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
93 Add support for the Soekris net5501 board (detection, error led
97 tristate "LED Support for the Freecom FSG-3"
101 This option enables support for the LEDs on the Freecom FSG-3.
104 tristate "LED Support for the WRAP series LEDs"
105 depends on LEDS_CLASS
106 depends on SCx200_GPIO
108 This option enables support for the PCEngines WRAP programmable LEDs.
111 tristate "LED Support for ALIX.2 and ALIX.3 series"
112 depends on LEDS_CLASS
113 depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
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.
118 config LEDS_COBALT_QUBE
119 tristate "LED Support for the Cobalt Qube series front LED"
120 depends on LEDS_CLASS
121 depends on MIPS_COBALT
123 This option enables support for the front LED on Cobalt Qube series
125 config LEDS_COBALT_RAQ
126 bool "LED Support for the Cobalt Raq series"
127 depends on LEDS_CLASS=y && MIPS_COBALT
130 This option enables support for the Cobalt Raq series LEDs.
133 tristate "LED support for SunFire servers."
134 depends on LEDS_CLASS
138 This option enables support for the Left, Middle, and Right
139 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
142 tristate "LED Support for the HP Jornada 6xx"
143 depends on LEDS_CLASS
146 This option enables LED support for the handheld
147 HP Jornada 620/660/680/690.
150 tristate "LED driver for PCA9532 dimmer"
151 depends on LEDS_CLASS
152 depends on I2C && INPUT && EXPERIMENTAL
154 This option enables support for NXP pca9532
155 LED controller. It is generally only useful
158 config LEDS_PCA9532_GPIO
159 bool "Enable GPIO support for PCA9532"
160 depends on LEDS_PCA9532
163 Allow unused pins on PCA9532 to be used as gpio.
165 To use a pin as gpio pca9532_type in pca9532_platform data needs to
166 set to PCA9532_TYPE_GPIO.
169 tristate "LED Support for GPIO connected LEDs"
170 depends on LEDS_CLASS
171 depends on GENERIC_GPIO
173 This option enables support for the LEDs connected to GPIO
174 outputs. To be useful the particular board must have LEDs
175 and they must be connected to the GPIO lines. The LEDs must be
176 defined as platform devices and/or OpenFirmware platform devices.
177 The code to use these bindings can be selected below.
179 config LEDS_GPIO_PLATFORM
180 bool "Platform device bindings for GPIO LEDs"
184 Let the leds-gpio driver drive LEDs which have been defined as
185 platform devices. If you don't know what this means, say yes.
188 bool "OpenFirmware platform device bindings for GPIO LEDs"
189 depends on LEDS_GPIO && OF_DEVICE
192 Let the leds-gpio driver drive LEDs which have been defined as
193 of_platform devices. For instance, LEDs which are listed in a "dts"
197 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
198 depends on LEDS_CLASS
201 This option enables support for LEDs connected to the National
202 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
205 To compile this driver as a module, choose M here: the
206 module will be called leds-lp3944.
209 tristate "LED Support for N.S. LP5521 LED driver chip"
210 depends on LEDS_CLASS && I2C
212 If you say yes here you get support for the National Semiconductor
213 LP5521 LED driver. It is 3 channel chip with programmable engines.
214 Driver provides direct control via LED class and interface for
215 programming the engines.
218 tristate "LED Support for N.S. LP5523 LED driver chip"
219 depends on LEDS_CLASS && I2C
221 If you say yes here you get support for the National Semiconductor
222 LP5523 LED driver. It is 9 channel chip with programmable engines.
223 Driver provides direct control via LED class and interface for
224 programming the engines.
226 config LEDS_CLEVO_MAIL
227 tristate "Mail LED on Clevo notebook"
228 depends on LEDS_CLASS
229 depends on X86 && SERIO_I8042 && DMI
231 This driver makes the mail LED accessible from userspace
232 programs through the leds subsystem. This LED have three
233 known mode: off, blink at 0.5Hz and blink at 1Hz.
235 The driver supports two kinds of interface: using ledtrig-timer
236 or through /sys/class/leds/clevo::mail/brightness. As this LED
237 cannot change it's brightness it blinks instead. The brightness
238 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
241 This module can drive the mail LED for the following notebooks:
246 Clevo D400V/D470V (not tested, but might work)
248 Clevo M5x0N (not tested, but might work)
249 Positivo Mobile (Clevo M5x0V)
251 If your model is not listed here you can try the "nodetect"
254 To compile this driver as a module, choose M here: the
255 module will be called leds-clevo-mail.
258 tristate "LED Support for PCA955x I2C chips"
259 depends on LEDS_CLASS
262 This option enables support for LEDs connected to PCA955x
263 LED driver chips accessed via the I2C bus. Supported
264 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
266 config LEDS_WM831X_STATUS
267 tristate "LED support for status LEDs on WM831x PMICs"
268 depends on LEDS_CLASS
269 depends on MFD_WM831X
271 This option enables support for the status LEDs of the WM831x
275 tristate "LED Support for WM8350 AudioPlus PMIC"
276 depends on LEDS_CLASS
277 depends on MFD_WM8350
279 This option enables support for LEDs driven by the Wolfson
280 Microelectronics WM8350 AudioPlus PMIC.
283 tristate "LED Support for DA9030/DA9034 PMIC"
284 depends on LEDS_CLASS
285 depends on PMIC_DA903X
287 This option enables support for on-chip LED drivers found
288 on Dialog Semiconductor DA9030/DA9034 PMICs.
290 config LEDS_DAC124S085
291 tristate "LED Support for DAC124S085 SPI DAC"
292 depends on LEDS_CLASS
295 This option enables support for DAC124S085 SPI DAC from NatSemi,
296 which can be used to control up to four LEDs.
299 tristate "PWM driven LED Support"
300 depends on LEDS_CLASS
303 This option enables support for pwm driven LEDs
305 config LEDS_REGULATOR
306 tristate "REGULATOR driven LED support"
307 depends on LEDS_CLASS
310 This option enables support for regulator driven LEDs.
313 tristate "LED driver for BD2802 RGB LED"
314 depends on LEDS_CLASS
317 This option enables support for BD2802GU RGB LED driver chips
318 accessed via the I2C bus.
320 config LEDS_INTEL_SS4200
321 tristate "LED driver for Intel NAS SS4200 series"
322 depends on LEDS_CLASS
323 depends on PCI && DMI
325 This option enables support for the Intel SS4200 series of
326 Network Attached Storage servers. You may control the hard
327 drive or power LEDs on the front panel. Using this driver
328 can stop the front LED from blinking after startup.
331 tristate "LED driver for LT3593 controllers"
332 depends on LEDS_CLASS
333 depends on GENERIC_GPIO
335 This option enables support for LEDs driven by a Linear Technology
336 LT3593 controller. This controller uses a special one-wire pulse
337 coding protocol to set the brightness.
340 tristate "LED Support for ADP5520/ADP5501 PMIC"
341 depends on LEDS_CLASS
342 depends on PMIC_ADP5520
344 This option enables support for on-chip LED drivers found
345 on Analog Devices ADP5520/ADP5501 PMICs.
347 To compile this driver as a module, choose M here: the module will
348 be called leds-adp5520.
350 config LEDS_DELL_NETBOOKS
351 tristate "External LED on Dell Business Netbooks"
352 depends on LEDS_CLASS
353 depends on X86 && ACPI_WMI
355 This adds support for the Latitude 2100 and similar
356 notebooks that have an external LED.
359 tristate "LED Support for MC13783 PMIC"
360 depends on LEDS_CLASS
361 depends on MFD_MC13783
363 This option enable support for on-chip LED drivers found
364 on Freescale Semiconductor MC13783 PMIC.
367 tristate "LED support for Network Space v2 GPIO LEDs"
368 depends on LEDS_CLASS
369 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
372 This option enable support for the dual-GPIO LED found on the
373 Network Space v2 board (and parents). This include Internet Space v2,
374 Network Space (Max) v2 and d2 Network v2 boards.
377 tristate "LED support for Big Network series LEDs"
378 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
381 This option enable support for LEDs found on the LaCie 2Big
382 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
383 controlled through a GPIO extension bus.
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