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 && EXPERIMENTAL
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.
197 tristate "LED Support for N.S. LP5521 LED driver chip"
198 depends on LEDS_CLASS && I2C
200 If you say yes here you get support for the National Semiconductor
201 LP5521 LED driver. It is 3 channel chip with programmable engines.
202 Driver provides direct control via LED class and interface for
203 programming the engines.
206 tristate "LED Support for TI/National LP5523/55231 LED driver chip"
207 depends on LEDS_CLASS && I2C
209 If you say yes here you get support for TI/National Semiconductor
210 LP5523/55231 LED driver.
211 It is 9 channel chip with programmable engines.
212 Driver provides direct control via LED class and interface for
213 programming the engines.
216 tristate "LED support for the TI LP8788 PMIC"
217 depends on LEDS_CLASS
218 depends on MFD_LP8788
220 This option enables support for the Keyboard LEDs on the LP8788 PMIC.
222 config LEDS_CLEVO_MAIL
223 tristate "Mail LED on Clevo notebook"
224 depends on LEDS_CLASS
225 depends on X86 && SERIO_I8042 && DMI
227 This driver makes the mail LED accessible from userspace
228 programs through the leds subsystem. This LED have three
229 known mode: off, blink at 0.5Hz and blink at 1Hz.
231 The driver supports two kinds of interface: using ledtrig-timer
232 or through /sys/class/leds/clevo::mail/brightness. As this LED
233 cannot change it's brightness it blinks instead. The brightness
234 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
237 This module can drive the mail LED for the following notebooks:
242 Clevo D400V/D470V (not tested, but might work)
244 Clevo M5x0N (not tested, but might work)
245 Positivo Mobile (Clevo M5x0V)
247 If your model is not listed here you can try the "nodetect"
250 To compile this driver as a module, choose M here: the
251 module will be called leds-clevo-mail.
254 tristate "LED Support for PCA955x I2C chips"
255 depends on LEDS_CLASS
258 This option enables support for LEDs connected to PCA955x
259 LED driver chips accessed via the I2C bus. Supported
260 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
263 tristate "LED support for PCA9633 I2C chip"
264 depends on LEDS_CLASS
267 This option enables support for LEDs connected to the PCA9633
268 LED driver chip accessed via the I2C bus.
270 config LEDS_WM831X_STATUS
271 tristate "LED support for status LEDs on WM831x PMICs"
272 depends on LEDS_CLASS
273 depends on MFD_WM831X
275 This option enables support for the status LEDs of the WM831x
279 tristate "LED Support for WM8350 AudioPlus PMIC"
280 depends on LEDS_CLASS
281 depends on MFD_WM8350
283 This option enables support for LEDs driven by the Wolfson
284 Microelectronics WM8350 AudioPlus PMIC.
287 tristate "LED Support for DA9030/DA9034 PMIC"
288 depends on LEDS_CLASS
289 depends on PMIC_DA903X
291 This option enables support for on-chip LED drivers found
292 on Dialog Semiconductor DA9030/DA9034 PMICs.
295 tristate "Dialog DA9052/DA9053 LEDS"
296 depends on LEDS_CLASS
297 depends on PMIC_DA9052
299 This option enables support for on-chip LED drivers found
300 on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
302 config LEDS_DAC124S085
303 tristate "LED Support for DAC124S085 SPI DAC"
304 depends on LEDS_CLASS
307 This option enables support for DAC124S085 SPI DAC from NatSemi,
308 which can be used to control up to four LEDs.
311 tristate "PWM driven LED Support"
312 depends on LEDS_CLASS
315 This option enables support for pwm driven LEDs
317 config LEDS_REGULATOR
318 tristate "REGULATOR driven LED support"
319 depends on LEDS_CLASS
322 This option enables support for regulator driven LEDs.
325 tristate "LED driver for BD2802 RGB LED"
326 depends on LEDS_CLASS
329 This option enables support for BD2802GU RGB LED driver chips
330 accessed via the I2C bus.
332 config LEDS_INTEL_SS4200
333 tristate "LED driver for Intel NAS SS4200 series"
334 depends on LEDS_CLASS
335 depends on PCI && DMI
337 This option enables support for the Intel SS4200 series of
338 Network Attached Storage servers. You may control the hard
339 drive or power LEDs on the front panel. Using this driver
340 can stop the front LED from blinking after startup.
343 tristate "LED driver for LT3593 controllers"
344 depends on LEDS_CLASS
345 depends on GENERIC_GPIO
347 This option enables support for LEDs driven by a Linear Technology
348 LT3593 controller. This controller uses a special one-wire pulse
349 coding protocol to set the brightness.
352 tristate "LED Support for ADP5520/ADP5501 PMIC"
353 depends on LEDS_CLASS
354 depends on PMIC_ADP5520
356 This option enables support for on-chip LED drivers found
357 on Analog Devices ADP5520/ADP5501 PMICs.
359 To compile this driver as a module, choose M here: the module will
360 be called leds-adp5520.
362 config LEDS_DELL_NETBOOKS
363 tristate "External LED on Dell Business Netbooks"
364 depends on LEDS_CLASS
365 depends on X86 && ACPI_WMI
367 This adds support for the Latitude 2100 and similar
368 notebooks that have an external LED.
371 tristate "LED Support for MC13783 PMIC"
372 depends on LEDS_CLASS
373 depends on MFD_MC13783
375 This option enable support for on-chip LED drivers found
376 on Freescale Semiconductor MC13783 PMIC.
379 tristate "LED support for Network Space v2 GPIO LEDs"
380 depends on LEDS_CLASS
381 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
382 MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2
385 This option enable support for the dual-GPIO LED found on the
386 Network Space v2 board (and parents). This include Internet Space v2,
387 Network Space (Max) v2 and d2 Network v2 boards.
390 tristate "LED support for Big Network series LEDs"
391 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
392 depends on LEDS_CLASS
395 This option enable support for LEDs found on the LaCie 2Big
396 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
397 controlled through a GPIO extension bus.
400 bool "LED support for the HTC ASIC3"
401 depends on LEDS_CLASS=y
405 This option enables support for the LEDs on the HTC ASIC3. The HTC
406 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
407 cannot be used. This driver supports hardware blinking with an on+off
408 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
410 config LEDS_RENESAS_TPU
411 bool "LED support for Renesas TPU"
412 depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO
414 This option enables build of the LED TPU platform driver,
415 suitable to drive any TPU channel on newer Renesas SoCs.
416 The driver controls the GPIO pin connected to the LED via
417 the GPIO framework and expects the LED to be connected to
418 a pin that can be driven in both GPIO mode and using TPU
419 pin function. The latter to support brightness control.
420 Brightness control is supported but hardware blinking is not.
423 tristate "LED Support for TCA6507 I2C chip"
424 depends on LEDS_CLASS && I2C
426 This option enables support for LEDs connected to TC6507
427 LED driver chips accessed via the I2C bus.
428 Driver support brightness control and hardware-assisted blinking.
431 tristate "LED support for MAX8997 PMIC"
432 depends on LEDS_CLASS && MFD_MAX8997
434 This option enables support for on-chip LED drivers on
438 tristate "LED support for LM355x Chips, LM3554 and LM3556"
439 depends on LEDS_CLASS && I2C
442 This option enables support for LEDs connected to LM355x.
443 LM355x includes Torch, Flash and Indicator functions.
446 tristate "LED support for the Bachmann OT200"
447 depends on LEDS_CLASS && HAS_IOMEM
449 This option enables support for the LEDs on the Bachmann OT200.
450 Say Y to enable LEDs on the Bachmann OT200.
453 tristate "LED support for the BlinkM I2C RGB LED"
454 depends on LEDS_CLASS
457 This option enables support for the BlinkM RGB LED connected
458 through I2C. Say Y to enable support for the BlinkM LED.
461 bool "LED Trigger support"
462 depends on LEDS_CLASS
464 This option enables trigger support for the leds class.
465 These triggers allow kernel events to drive the LEDs and can
466 be configured via sysfs. If unsure, say Y.
468 comment "LED Triggers"
470 config LEDS_TRIGGER_TIMER
471 tristate "LED Timer Trigger"
472 depends on LEDS_TRIGGERS
474 This allows LEDs to be controlled by a programmable timer
475 via sysfs. Some LED hardware can be programmed to start
476 blinking the LED without any further software interaction.
477 For more details read Documentation/leds/leds-class.txt.
481 config LEDS_TRIGGER_ONESHOT
482 tristate "LED One-shot Trigger"
483 depends on LEDS_TRIGGERS
485 This allows LEDs to blink in one-shot pulses with parameters
486 controlled via sysfs. It's useful to notify the user on
487 sporadic events, when there are no clear begin and end trap points,
488 or on dense events, where this blinks the LED at constant rate if
489 rearmed continuously.
491 It also shows how to use the led_blink_set_oneshot() function.
495 config LEDS_TRIGGER_IDE_DISK
496 bool "LED IDE Disk Trigger"
497 depends on IDE_GD_ATA
498 depends on LEDS_TRIGGERS
500 This allows LEDs to be controlled by IDE disk activity.
503 config LEDS_TRIGGER_HEARTBEAT
504 tristate "LED Heartbeat Trigger"
505 depends on LEDS_TRIGGERS
507 This allows LEDs to be controlled by a CPU load average.
508 The flash frequency is a hyperbolic function of the 1-minute
512 config LEDS_TRIGGER_BACKLIGHT
513 tristate "LED backlight Trigger"
514 depends on LEDS_TRIGGERS
516 This allows LEDs to be controlled as a backlight device: they
517 turn off and on when the display is blanked and unblanked.
521 config LEDS_TRIGGER_CPU
522 bool "LED CPU Trigger"
523 depends on LEDS_TRIGGERS
525 This allows LEDs to be controlled by active CPUs. This shows
526 the active CPUs across an array of LEDs so you can see which
527 CPUs are active on the system at any given moment.
531 config LEDS_TRIGGER_GPIO
532 tristate "LED GPIO Trigger"
533 depends on LEDS_TRIGGERS
536 This allows LEDs to be controlled by gpio events. It's good
537 when using gpios as switches and triggering the needed LEDs
538 from there. One use case is n810's keypad LEDs that could
539 be triggered by this trigger when user slides up to show
544 config LEDS_TRIGGER_DEFAULT_ON
545 tristate "LED Default ON Trigger"
546 depends on LEDS_TRIGGERS
548 This allows LEDs to be initialised in the ON state.
551 comment "iptables trigger is under Netfilter config (LED target)"
552 depends on LEDS_TRIGGERS
554 config LEDS_TRIGGER_TRANSIENT
555 tristate "LED Transient Trigger"
556 depends on LEDS_TRIGGERS
558 This allows one time activation of a transient state on
559 GPIO/PWM based hardware.