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 "LED Support using Atmel PWM outputs"
40 This option enables support for LEDs driven using outputs
41 of the dedicated PWM controller found on newer Atmel SOCs.
44 tristate "LCD Backlight driver for LM3530"
48 This option enables support for the LCD backlight using
49 LM3530 ambient light sensor chip. This ALS chip can be
50 controlled manually or using PWM input or using ambient
54 tristate "LED support for LM3533"
58 This option enables support for the LEDs on National Semiconductor /
59 TI LM3533 Lighting Power chips.
61 The LEDs can be controlled directly, through PWM input, or by the
62 ambient-light-sensor interface. The chip supports
63 hardware-accelerated blinking with maximum on and off periods of 9.8
64 and 77 seconds respectively.
67 tristate "LED support for LM3642 Chip"
68 depends on LEDS_CLASS && I2C
71 This option enables support for LEDs connected to LM3642.
72 The LM3642 is a 4MHz fixed-frequency synchronous boost
73 converter plus 1.5A constant current driver for a high-current
78 tristate "LED Support for Locomo device"
80 depends on SHARP_LOCOMO
82 This option enables support for the LEDs on Sharp Locomo.
83 Zaurus models SL-5500 and SL-5600.
85 config LEDS_MIKROTIK_RB532
86 tristate "LED Support for Mikrotik Routerboard 532"
88 depends on MIKROTIK_RB532
90 This option enables support for the so called "User LED" of
91 Mikrotik's Routerboard 532.
94 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
96 depends on ARCH_S3C24XX
98 This option enables support for LEDs connected to GPIO lines
99 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
102 tristate "LED Support for Soekris net48xx series Error LED"
103 depends on LEDS_CLASS
104 depends on SCx200_GPIO
106 This option enables support for the Soekris net4801 and net4826 error
110 tristate "LED Support for the Freecom FSG-3"
111 depends on LEDS_CLASS
114 This option enables support for the LEDs on the Freecom FSG-3.
117 tristate "LED Support for the WRAP series LEDs"
118 depends on LEDS_CLASS
119 depends on SCx200_GPIO
121 This option enables support for the PCEngines WRAP programmable LEDs.
123 config LEDS_COBALT_QUBE
124 tristate "LED Support for the Cobalt Qube series front LED"
125 depends on LEDS_CLASS
126 depends on MIPS_COBALT
128 This option enables support for the front LED on Cobalt Qube series
130 config LEDS_COBALT_RAQ
131 bool "LED Support for the Cobalt Raq series"
132 depends on LEDS_CLASS=y && MIPS_COBALT
135 This option enables support for the Cobalt Raq series LEDs.
138 tristate "LED support for SunFire servers."
139 depends on LEDS_CLASS
143 This option enables support for the Left, Middle, and Right
144 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
147 tristate "LED Support for the HP Jornada 6xx"
148 depends on LEDS_CLASS
151 This option enables LED support for the handheld
152 HP Jornada 620/660/680/690.
155 tristate "LED driver for PCA9532 dimmer"
156 depends on LEDS_CLASS
157 depends on I2C && INPUT
159 This option enables support for NXP pca9532
160 LED controller. It is generally only useful
163 config LEDS_PCA9532_GPIO
164 bool "Enable GPIO support for PCA9532"
165 depends on LEDS_PCA9532
168 Allow unused pins on PCA9532 to be used as gpio.
170 To use a pin as gpio pca9532_type in pca9532_platform data needs to
171 set to PCA9532_TYPE_GPIO.
174 tristate "LED Support for GPIO connected LEDs"
175 depends on LEDS_CLASS
176 depends on GENERIC_GPIO
178 This option enables support for the LEDs connected to GPIO
179 outputs. To be useful the particular board must have LEDs
180 and they must be connected to the GPIO lines. The LEDs must be
181 defined as platform devices and/or OpenFirmware platform devices.
182 The code to use these bindings can be selected below.
185 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
186 depends on LEDS_CLASS
189 This option enables support for LEDs connected to the National
190 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
193 To compile this driver as a module, choose M here: the
194 module will be called leds-lp3944.
196 config LEDS_LP55XX_COMMON
197 tristate "Common Driver for TI/National LP5521, LP5523/55231 and LP5562"
198 depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562
201 This option supports common operations for LP5521 and LP5523/55231
205 tristate "LED Support for N.S. LP5521 LED driver chip"
206 depends on LEDS_CLASS && I2C
207 select LEDS_LP55XX_COMMON
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.
215 tristate "LED Support for TI/National LP5523/55231 LED driver chip"
216 depends on LEDS_CLASS && I2C
217 select LEDS_LP55XX_COMMON
219 If you say yes here you get support for TI/National Semiconductor
220 LP5523/55231 LED driver.
221 It is 9 channel chip with programmable engines.
222 Driver provides direct control via LED class and interface for
223 programming the engines.
226 tristate "LED Support for TI LP5562 LED driver chip"
227 depends on LEDS_CLASS && I2C
228 select LEDS_LP55XX_COMMON
230 If you say yes here you get support for TI LP5562 LED driver.
231 It is 4 channels chip with programmable engines.
232 Driver provides direct control via LED class and interface for
233 programming the engines.
236 tristate "LED support for the TI LP8788 PMIC"
237 depends on LEDS_CLASS
238 depends on MFD_LP8788
240 This option enables support for the Keyboard LEDs on the LP8788 PMIC.
242 config LEDS_CLEVO_MAIL
243 tristate "Mail LED on Clevo notebook"
244 depends on LEDS_CLASS
245 depends on X86 && SERIO_I8042 && DMI
247 This driver makes the mail LED accessible from userspace
248 programs through the leds subsystem. This LED have three
249 known mode: off, blink at 0.5Hz and blink at 1Hz.
251 The driver supports two kinds of interface: using ledtrig-timer
252 or through /sys/class/leds/clevo::mail/brightness. As this LED
253 cannot change it's brightness it blinks instead. The brightness
254 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
257 This module can drive the mail LED for the following notebooks:
262 Clevo D400V/D470V (not tested, but might work)
264 Clevo M5x0N (not tested, but might work)
265 Positivo Mobile (Clevo M5x0V)
267 If your model is not listed here you can try the "nodetect"
270 To compile this driver as a module, choose M here: the
271 module will be called leds-clevo-mail.
274 tristate "LED Support for PCA955x I2C chips"
275 depends on LEDS_CLASS
278 This option enables support for LEDs connected to PCA955x
279 LED driver chips accessed via the I2C bus. Supported
280 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
283 tristate "LED support for PCA9633 I2C chip"
284 depends on LEDS_CLASS
287 This option enables support for LEDs connected to the PCA9633
288 LED driver chip accessed via the I2C bus.
290 config LEDS_WM831X_STATUS
291 tristate "LED support for status LEDs on WM831x PMICs"
292 depends on LEDS_CLASS
293 depends on MFD_WM831X
295 This option enables support for the status LEDs of the WM831x
299 tristate "LED Support for WM8350 AudioPlus PMIC"
300 depends on LEDS_CLASS
301 depends on MFD_WM8350
303 This option enables support for LEDs driven by the Wolfson
304 Microelectronics WM8350 AudioPlus PMIC.
307 tristate "LED Support for DA9030/DA9034 PMIC"
308 depends on LEDS_CLASS
309 depends on PMIC_DA903X
311 This option enables support for on-chip LED drivers found
312 on Dialog Semiconductor DA9030/DA9034 PMICs.
315 tristate "Dialog DA9052/DA9053 LEDS"
316 depends on LEDS_CLASS
317 depends on PMIC_DA9052
319 This option enables support for on-chip LED drivers found
320 on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
322 config LEDS_DAC124S085
323 tristate "LED Support for DAC124S085 SPI DAC"
324 depends on LEDS_CLASS
327 This option enables support for DAC124S085 SPI DAC from NatSemi,
328 which can be used to control up to four LEDs.
331 tristate "PWM driven LED Support"
332 depends on LEDS_CLASS
335 This option enables support for pwm driven LEDs
337 config LEDS_REGULATOR
338 tristate "REGULATOR driven LED support"
339 depends on LEDS_CLASS
342 This option enables support for regulator driven LEDs.
345 tristate "LED driver for BD2802 RGB LED"
346 depends on LEDS_CLASS
349 This option enables support for BD2802GU RGB LED driver chips
350 accessed via the I2C bus.
352 config LEDS_INTEL_SS4200
353 tristate "LED driver for Intel NAS SS4200 series"
354 depends on LEDS_CLASS
355 depends on PCI && DMI
357 This option enables support for the Intel SS4200 series of
358 Network Attached Storage servers. You may control the hard
359 drive or power LEDs on the front panel. Using this driver
360 can stop the front LED from blinking after startup.
363 tristate "LED driver for LT3593 controllers"
364 depends on LEDS_CLASS
365 depends on GENERIC_GPIO
367 This option enables support for LEDs driven by a Linear Technology
368 LT3593 controller. This controller uses a special one-wire pulse
369 coding protocol to set the brightness.
372 tristate "LED Support for ADP5520/ADP5501 PMIC"
373 depends on LEDS_CLASS
374 depends on PMIC_ADP5520
376 This option enables support for on-chip LED drivers found
377 on Analog Devices ADP5520/ADP5501 PMICs.
379 To compile this driver as a module, choose M here: the module will
380 be called leds-adp5520.
382 config LEDS_DELL_NETBOOKS
383 tristate "External LED on Dell Business Netbooks"
384 depends on LEDS_CLASS
385 depends on X86 && ACPI_WMI
387 This adds support for the Latitude 2100 and similar
388 notebooks that have an external LED.
391 tristate "LED Support for MC13783 PMIC"
392 depends on LEDS_CLASS
393 depends on MFD_MC13783
395 This option enable support for on-chip LED drivers found
396 on Freescale Semiconductor MC13783 PMIC.
399 tristate "LED support for Network Space v2 GPIO LEDs"
400 depends on LEDS_CLASS
401 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
402 MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2 || \
403 MACH_NETSPACE_V2_DT || MACH_INETSPACE_V2_DT || \
404 MACH_NETSPACE_MAX_V2_DT || MACH_NETSPACE_MINI_V2_DT
407 This option enable support for the dual-GPIO LED found on the
408 Network Space v2 board (and parents). This include Internet Space v2,
409 Network Space (Max) v2 and d2 Network v2 boards.
412 tristate "LED support for Big Network series LEDs"
413 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
414 depends on LEDS_CLASS
417 This option enable support for LEDs found on the LaCie 2Big
418 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
419 controlled through a GPIO extension bus.
422 bool "LED support for the HTC ASIC3"
423 depends on LEDS_CLASS=y
427 This option enables support for the LEDs on the HTC ASIC3. The HTC
428 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
429 cannot be used. This driver supports hardware blinking with an on+off
430 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
432 config LEDS_RENESAS_TPU
433 bool "LED support for Renesas TPU"
434 depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO
436 This option enables build of the LED TPU platform driver,
437 suitable to drive any TPU channel on newer Renesas SoCs.
438 The driver controls the GPIO pin connected to the LED via
439 the GPIO framework and expects the LED to be connected to
440 a pin that can be driven in both GPIO mode and using TPU
441 pin function. The latter to support brightness control.
442 Brightness control is supported but hardware blinking is not.
445 tristate "LED Support for TCA6507 I2C chip"
446 depends on LEDS_CLASS && I2C
448 This option enables support for LEDs connected to TC6507
449 LED driver chips accessed via the I2C bus.
450 Driver support brightness control and hardware-assisted blinking.
453 tristate "LED support for MAX8997 PMIC"
454 depends on LEDS_CLASS && MFD_MAX8997
456 This option enables support for on-chip LED drivers on
460 tristate "LED support for LM355x Chips, LM3554 and LM3556"
461 depends on LEDS_CLASS && I2C
464 This option enables support for LEDs connected to LM355x.
465 LM355x includes Torch, Flash and Indicator functions.
468 tristate "LED support for the Bachmann OT200"
469 depends on LEDS_CLASS && HAS_IOMEM
471 This option enables support for the LEDs on the Bachmann OT200.
472 Say Y to enable LEDs on the Bachmann OT200.
475 tristate "LED support for the BlinkM I2C RGB LED"
476 depends on LEDS_CLASS
479 This option enables support for the BlinkM RGB LED connected
480 through I2C. Say Y to enable support for the BlinkM LED.
482 comment "LED Triggers"
483 source "drivers/leds/trigger/Kconfig"