1 config LEDS_GPIO_REGISTER
4 This option provides the function gpio_led_register_device.
5 As this function is used by arch code it must not be compiled as a
11 Say Y to enable Linux LED support. This allows control of supported
12 LEDs from both userspace and optionally, by kernel events (triggers).
14 This is not related to standard keyboard LEDs which are controlled
20 tristate "LED Class Support"
22 This option enables the led sysfs class in /sys/class/leds. You'll
23 need this to do anything useful with LEDs. If unsure, say N.
28 tristate "LED Support for Marvell 88PM860x PMIC"
30 depends on MFD_88PM860X
32 This option enables support for on-chip LED drivers found on Marvell
33 Semiconductor 88PM8606 PMIC.
36 tristate "LCD Backlight driver for LM3530"
40 This option enables support for the LCD backlight using
41 LM3530 ambient light sensor chip. This ALS chip can be
42 controlled manually or using PWM input or using ambient
46 tristate "LED support for LM3533"
50 This option enables support for the LEDs on National Semiconductor /
51 TI LM3533 Lighting Power chips.
53 The LEDs can be controlled directly, through PWM input, or by the
54 ambient-light-sensor interface. The chip supports
55 hardware-accelerated blinking with maximum on and off periods of 9.8
56 and 77 seconds respectively.
59 tristate "LED support for LM3642 Chip"
60 depends on LEDS_CLASS && I2C
63 This option enables support for LEDs connected to LM3642.
64 The LM3642 is a 4MHz fixed-frequency synchronous boost
65 converter plus 1.5A constant current driver for a high-current
70 tristate "LED Support for Locomo device"
72 depends on SHARP_LOCOMO
74 This option enables support for the LEDs on Sharp Locomo.
75 Zaurus models SL-5500 and SL-5600.
77 config LEDS_MIKROTIK_RB532
78 tristate "LED Support for Mikrotik Routerboard 532"
80 depends on MIKROTIK_RB532
82 This option enables support for the so called "User LED" of
83 Mikrotik's Routerboard 532.
86 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
88 depends on ARCH_S3C24XX
90 This option enables support for LEDs connected to GPIO lines
91 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
94 tristate "LED Support for Soekris net48xx series Error LED"
96 depends on SCx200_GPIO
98 This option enables support for the Soekris net4801 and net4826 error
102 tristate "LED Support for the Freecom FSG-3"
103 depends on LEDS_CLASS
106 This option enables support for the LEDs on the Freecom FSG-3.
109 tristate "LED Support for the WRAP series LEDs"
110 depends on LEDS_CLASS
111 depends on SCx200_GPIO
113 This option enables support for the PCEngines WRAP programmable LEDs.
115 config LEDS_COBALT_QUBE
116 tristate "LED Support for the Cobalt Qube series front LED"
117 depends on LEDS_CLASS
118 depends on MIPS_COBALT
120 This option enables support for the front LED on Cobalt Qube series
122 config LEDS_COBALT_RAQ
123 bool "LED Support for the Cobalt Raq series"
124 depends on LEDS_CLASS=y && MIPS_COBALT
127 This option enables support for the Cobalt Raq series LEDs.
130 tristate "LED support for SunFire servers."
131 depends on LEDS_CLASS
135 This option enables support for the Left, Middle, and Right
136 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
138 config LEDS_IPAQ_MICRO
139 tristate "LED Support for the Compaq iPAQ h3xxx"
140 depends on MFD_IPAQ_MICRO
142 Choose this option if you want to use the notification LED on
143 Compaq/HP iPAQ h3100 and h3600.
146 tristate "LED Support for the HP Jornada 6xx"
147 depends on LEDS_CLASS
150 This option enables LED support for the handheld
151 HP Jornada 620/660/680/690.
154 tristate "LED driver for PCA9532 dimmer"
155 depends on LEDS_CLASS
156 depends on I2C && INPUT
158 This option enables support for NXP pca9532
159 LED controller. It is generally only useful
162 config LEDS_PCA9532_GPIO
163 bool "Enable GPIO support for PCA9532"
164 depends on LEDS_PCA9532
167 Allow unused pins on PCA9532 to be used as gpio.
169 To use a pin as gpio pca9532_type in pca9532_platform data needs to
170 set to PCA9532_TYPE_GPIO.
173 tristate "LED Support for GPIO connected LEDs"
174 depends on LEDS_CLASS
177 This option enables support for the LEDs connected to GPIO
178 outputs. To be useful the particular board must have LEDs
179 and they must be connected to the GPIO lines. The LEDs must be
180 defined as platform devices and/or OpenFirmware platform devices.
181 The code to use these bindings can be selected below.
184 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
185 depends on LEDS_CLASS
188 This option enables support for LEDs connected to the National
189 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
192 To compile this driver as a module, choose M here: the
193 module will be called leds-lp3944.
195 config LEDS_LP55XX_COMMON
196 tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501"
197 depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501
200 This option supports common operations for LP5521/5523/55231/5562/8501
204 tristate "LED Support for N.S. LP5521 LED driver chip"
205 depends on LEDS_CLASS && I2C
206 select LEDS_LP55XX_COMMON
208 If you say yes here you get support for the National Semiconductor
209 LP5521 LED driver. It is 3 channel chip with programmable engines.
210 Driver provides direct control via LED class and interface for
211 programming the engines.
214 tristate "LED Support for TI/National LP5523/55231 LED driver chip"
215 depends on LEDS_CLASS && I2C
216 select LEDS_LP55XX_COMMON
218 If you say yes here you get support for TI/National Semiconductor
219 LP5523/55231 LED driver.
220 It is 9 channel chip with programmable engines.
221 Driver provides direct control via LED class and interface for
222 programming the engines.
225 tristate "LED Support for TI LP5562 LED driver chip"
226 depends on LEDS_CLASS && I2C
227 select LEDS_LP55XX_COMMON
229 If you say yes here you get support for TI LP5562 LED driver.
230 It is 4 channels chip with programmable engines.
231 Driver provides direct control via LED class and interface for
232 programming the engines.
235 tristate "LED Support for TI LP8501 LED driver chip"
236 depends on LEDS_CLASS && I2C
237 select LEDS_LP55XX_COMMON
239 If you say yes here you get support for TI LP8501 LED driver.
240 It is 9 channel chip with programmable engines.
241 Driver provides direct control via LED class and interface for
242 programming the engines.
243 It is similar as LP5523, but output power selection is available.
244 And register layout and engine program schemes are different.
247 tristate "LED support for the TI LP8788 PMIC"
248 depends on LEDS_CLASS
249 depends on MFD_LP8788
251 This option enables support for the Keyboard LEDs on the LP8788 PMIC.
253 config LEDS_CLEVO_MAIL
254 tristate "Mail LED on Clevo notebook"
255 depends on LEDS_CLASS
256 depends on X86 && SERIO_I8042 && DMI
258 This driver makes the mail LED accessible from userspace
259 programs through the leds subsystem. This LED have three
260 known mode: off, blink at 0.5Hz and blink at 1Hz.
262 The driver supports two kinds of interface: using ledtrig-timer
263 or through /sys/class/leds/clevo::mail/brightness. As this LED
264 cannot change it's brightness it blinks instead. The brightness
265 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
268 This module can drive the mail LED for the following notebooks:
273 Clevo D400V/D470V (not tested, but might work)
275 Clevo M5x0N (not tested, but might work)
276 Positivo Mobile (Clevo M5x0V)
278 If your model is not listed here you can try the "nodetect"
281 To compile this driver as a module, choose M here: the
282 module will be called leds-clevo-mail.
285 tristate "LED Support for PCA955x I2C chips"
286 depends on LEDS_CLASS
289 This option enables support for LEDs connected to PCA955x
290 LED driver chips accessed via the I2C bus. Supported
291 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
294 tristate "LED support for PCA963x I2C chip"
295 depends on LEDS_CLASS
298 This option enables support for LEDs connected to the PCA963x
299 LED driver chip accessed via the I2C bus. Supported
300 devices include PCA9633 and PCA9634
302 config LEDS_WM831X_STATUS
303 tristate "LED support for status LEDs on WM831x PMICs"
304 depends on LEDS_CLASS
305 depends on MFD_WM831X
307 This option enables support for the status LEDs of the WM831x
311 tristate "LED Support for WM8350 AudioPlus PMIC"
312 depends on LEDS_CLASS
313 depends on MFD_WM8350
315 This option enables support for LEDs driven by the Wolfson
316 Microelectronics WM8350 AudioPlus PMIC.
319 tristate "LED Support for DA9030/DA9034 PMIC"
320 depends on LEDS_CLASS
321 depends on PMIC_DA903X
323 This option enables support for on-chip LED drivers found
324 on Dialog Semiconductor DA9030/DA9034 PMICs.
327 tristate "Dialog DA9052/DA9053 LEDS"
328 depends on LEDS_CLASS
329 depends on PMIC_DA9052
331 This option enables support for on-chip LED drivers found
332 on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
334 config LEDS_DAC124S085
335 tristate "LED Support for DAC124S085 SPI DAC"
336 depends on LEDS_CLASS
339 This option enables support for DAC124S085 SPI DAC from NatSemi,
340 which can be used to control up to four LEDs.
343 tristate "PWM driven LED Support"
344 depends on LEDS_CLASS
347 This option enables support for pwm driven LEDs
349 config LEDS_REGULATOR
350 tristate "REGULATOR driven LED support"
351 depends on LEDS_CLASS
354 This option enables support for regulator driven LEDs.
357 tristate "LED driver for BD2802 RGB LED"
358 depends on LEDS_CLASS
361 This option enables support for BD2802GU RGB LED driver chips
362 accessed via the I2C bus.
364 config LEDS_INTEL_SS4200
365 tristate "LED driver for Intel NAS SS4200 series"
366 depends on LEDS_CLASS
367 depends on PCI && DMI
369 This option enables support for the Intel SS4200 series of
370 Network Attached Storage servers. You may control the hard
371 drive or power LEDs on the front panel. Using this driver
372 can stop the front LED from blinking after startup.
375 tristate "LED driver for LT3593 controllers"
376 depends on LEDS_CLASS
379 This option enables support for LEDs driven by a Linear Technology
380 LT3593 controller. This controller uses a special one-wire pulse
381 coding protocol to set the brightness.
384 tristate "LED Support for ADP5520/ADP5501 PMIC"
385 depends on LEDS_CLASS
386 depends on PMIC_ADP5520
388 This option enables support for on-chip LED drivers found
389 on Analog Devices ADP5520/ADP5501 PMICs.
391 To compile this driver as a module, choose M here: the module will
392 be called leds-adp5520.
394 config LEDS_DELL_NETBOOKS
395 tristate "External LED on Dell Business Netbooks"
396 depends on LEDS_CLASS
397 depends on X86 && ACPI_WMI
399 This adds support for the Latitude 2100 and similar
400 notebooks that have an external LED.
403 tristate "LED Support for MC13XXX PMIC"
404 depends on LEDS_CLASS
405 depends on MFD_MC13XXX
407 This option enable support for on-chip LED drivers found
408 on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC.
411 tristate "LED support for Network Space v2 GPIO LEDs"
412 depends on LEDS_CLASS
413 depends on MACH_KIRKWOOD
416 This option enable support for the dual-GPIO LED found on the
417 Network Space v2 board (and parents). This include Internet Space v2,
418 Network Space (Max) v2 and d2 Network v2 boards.
421 tristate "LED support for Big Network series LEDs"
422 depends on LEDS_CLASS
423 depends on MACH_KIRKWOOD
426 This option enable support for LEDs found on the LaCie 2Big
427 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
428 controlled through a GPIO extension bus.
431 bool "LED support for the HTC ASIC3"
432 depends on LEDS_CLASS=y
436 This option enables support for the LEDs on the HTC ASIC3. The HTC
437 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
438 cannot be used. This driver supports hardware blinking with an on+off
439 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
442 tristate "LED Support for TCA6507 I2C chip"
443 depends on LEDS_CLASS && I2C
445 This option enables support for LEDs connected to TC6507
446 LED driver chips accessed via the I2C bus.
447 Driver support brightness control and hardware-assisted blinking.
450 tristate "LED support for MAX8997 PMIC"
451 depends on LEDS_CLASS && MFD_MAX8997
453 This option enables support for on-chip LED drivers on
457 tristate "LED support for LM355x Chips, LM3554 and LM3556"
458 depends on LEDS_CLASS && I2C
461 This option enables support for LEDs connected to LM355x.
462 LM355x includes Torch, Flash and Indicator functions.
465 tristate "LED support for the Bachmann OT200"
466 depends on LEDS_CLASS && HAS_IOMEM && (X86_32 || COMPILE_TEST)
468 This option enables support for the LEDs on the Bachmann OT200.
469 Say Y to enable LEDs on the Bachmann OT200.
471 config LEDS_MENF21BMC
472 tristate "LED support for the MEN 14F021P00 BMC"
473 depends on LEDS_CLASS && MFD_MENF21BMC
475 Say Y here to include support for the MEN 14F021P00 BMC LEDs.
477 This driver can also be built as a module. If so the module
478 will be called leds-menf21bmc.
480 comment "LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)"
483 tristate "LED support for the BlinkM I2C RGB LED"
484 depends on LEDS_CLASS
487 This option enables support for the BlinkM RGB LED connected
488 through I2C. Say Y to enable support for the BlinkM LED.
491 bool "LED support for LEDs on system controllers"
492 depends on LEDS_CLASS=y
493 depends on MFD_SYSCON
496 This option enabled support for the LEDs on syscon type
497 devices. This will only work with device tree enabled
500 config LEDS_VERSATILE
501 tristate "LED support for the ARM Versatile and RealView"
502 depends on ARCH_REALVIEW || ARCH_VERSATILE
503 depends on LEDS_CLASS
505 This option enabled support for the LEDs on the ARM Versatile
506 and RealView boards. Say Y to enabled these.
508 comment "LED Triggers"
509 source "drivers/leds/trigger/Kconfig"