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 bool "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 Locomo device"
56 depends on SHARP_LOCOMO
58 This option enables support for the LEDs on Sharp Locomo.
59 Zaurus models SL-5500 and SL-5600.
61 config LEDS_MIKROTIK_RB532
62 tristate "LED Support for Mikrotik Routerboard 532"
64 depends on MIKROTIK_RB532
66 This option enables support for the so called "User LED" of
67 Mikrotik's Routerboard 532.
70 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
72 depends on ARCH_S3C2410
74 This option enables support for LEDs connected to GPIO lines
75 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
78 tristate "LED Support for the Amstrad Delta (E3)"
80 depends on MACH_AMS_DELTA
82 This option enables support for the LEDs on Amstrad Delta (E3).
85 tristate "LED Support for Soekris net48xx series Error LED"
87 depends on SCx200_GPIO
89 This option enables support for the Soekris net4801 and net4826 error
93 tristate "LED Support for the Freecom FSG-3"
97 This option enables support for the LEDs on the Freecom FSG-3.
100 tristate "LED Support for the WRAP series LEDs"
101 depends on LEDS_CLASS
102 depends on SCx200_GPIO
104 This option enables support for the PCEngines WRAP programmable LEDs.
106 config LEDS_COBALT_QUBE
107 tristate "LED Support for the Cobalt Qube series front LED"
108 depends on LEDS_CLASS
109 depends on MIPS_COBALT
111 This option enables support for the front LED on Cobalt Qube series
113 config LEDS_COBALT_RAQ
114 bool "LED Support for the Cobalt Raq series"
115 depends on LEDS_CLASS=y && MIPS_COBALT
118 This option enables support for the Cobalt Raq series LEDs.
121 tristate "LED support for SunFire servers."
122 depends on LEDS_CLASS
126 This option enables support for the Left, Middle, and Right
127 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
130 tristate "LED Support for the HP Jornada 6xx"
131 depends on LEDS_CLASS
134 This option enables LED support for the handheld
135 HP Jornada 620/660/680/690.
138 tristate "LED driver for PCA9532 dimmer"
139 depends on LEDS_CLASS
140 depends on I2C && INPUT && EXPERIMENTAL
142 This option enables support for NXP pca9532
143 LED controller. It is generally only useful
146 config LEDS_PCA9532_GPIO
147 bool "Enable GPIO support for PCA9532"
148 depends on LEDS_PCA9532
151 Allow unused pins on PCA9532 to be used as gpio.
153 To use a pin as gpio pca9532_type in pca9532_platform data needs to
154 set to PCA9532_TYPE_GPIO.
157 tristate "LED Support for GPIO connected LEDs"
158 depends on LEDS_CLASS
159 depends on GENERIC_GPIO
161 This option enables support for the LEDs connected to GPIO
162 outputs. To be useful the particular board must have LEDs
163 and they must be connected to the GPIO lines. The LEDs must be
164 defined as platform devices and/or OpenFirmware platform devices.
165 The code to use these bindings can be selected below.
168 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
169 depends on LEDS_CLASS
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 LEDS_CLASS
200 depends on X86 && SERIO_I8042 && DMI
202 This driver makes the mail LED accessible from userspace
203 programs through the leds subsystem. This LED have three
204 known mode: off, blink at 0.5Hz and blink at 1Hz.
206 The driver supports two kinds of interface: using ledtrig-timer
207 or through /sys/class/leds/clevo::mail/brightness. As this LED
208 cannot change it's brightness it blinks instead. The brightness
209 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
212 This module can drive the mail LED for the following notebooks:
217 Clevo D400V/D470V (not tested, but might work)
219 Clevo M5x0N (not tested, but might work)
220 Positivo Mobile (Clevo M5x0V)
222 If your model is not listed here you can try the "nodetect"
225 To compile this driver as a module, choose M here: the
226 module will be called leds-clevo-mail.
229 tristate "LED Support for PCA955x I2C chips"
230 depends on LEDS_CLASS
233 This option enables support for LEDs connected to PCA955x
234 LED driver chips accessed via the I2C bus. Supported
235 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
237 config LEDS_WM831X_STATUS
238 tristate "LED support for status LEDs on WM831x PMICs"
239 depends on LEDS_CLASS
240 depends on MFD_WM831X
242 This option enables support for the status LEDs of the WM831x
246 tristate "LED Support for WM8350 AudioPlus PMIC"
247 depends on LEDS_CLASS
248 depends on MFD_WM8350
250 This option enables support for LEDs driven by the Wolfson
251 Microelectronics WM8350 AudioPlus PMIC.
254 tristate "LED Support for DA9030/DA9034 PMIC"
255 depends on LEDS_CLASS
256 depends on PMIC_DA903X
258 This option enables support for on-chip LED drivers found
259 on Dialog Semiconductor DA9030/DA9034 PMICs.
261 config LEDS_DAC124S085
262 tristate "LED Support for DAC124S085 SPI DAC"
263 depends on LEDS_CLASS
266 This option enables support for DAC124S085 SPI DAC from NatSemi,
267 which can be used to control up to four LEDs.
270 tristate "PWM driven LED Support"
271 depends on LEDS_CLASS
274 This option enables support for pwm driven LEDs
276 config LEDS_REGULATOR
277 tristate "REGULATOR driven LED support"
278 depends on LEDS_CLASS
281 This option enables support for regulator driven LEDs.
284 tristate "LED driver for BD2802 RGB LED"
285 depends on LEDS_CLASS
288 This option enables support for BD2802GU RGB LED driver chips
289 accessed via the I2C bus.
291 config LEDS_INTEL_SS4200
292 tristate "LED driver for Intel NAS SS4200 series"
293 depends on LEDS_CLASS
294 depends on PCI && DMI
296 This option enables support for the Intel SS4200 series of
297 Network Attached Storage servers. You may control the hard
298 drive or power LEDs on the front panel. Using this driver
299 can stop the front LED from blinking after startup.
302 tristate "LED driver for LT3593 controllers"
303 depends on LEDS_CLASS
304 depends on GENERIC_GPIO
306 This option enables support for LEDs driven by a Linear Technology
307 LT3593 controller. This controller uses a special one-wire pulse
308 coding protocol to set the brightness.
311 tristate "LED Support for ADP5520/ADP5501 PMIC"
312 depends on LEDS_CLASS
313 depends on PMIC_ADP5520
315 This option enables support for on-chip LED drivers found
316 on Analog Devices ADP5520/ADP5501 PMICs.
318 To compile this driver as a module, choose M here: the module will
319 be called leds-adp5520.
321 config LEDS_DELL_NETBOOKS
322 tristate "External LED on Dell Business Netbooks"
323 depends on LEDS_CLASS
324 depends on X86 && ACPI_WMI
326 This adds support for the Latitude 2100 and similar
327 notebooks that have an external LED.
330 tristate "LED Support for MC13783 PMIC"
331 depends on LEDS_CLASS
332 depends on MFD_MC13783
334 This option enable support for on-chip LED drivers found
335 on Freescale Semiconductor MC13783 PMIC.
338 tristate "LED support for Network Space v2 GPIO LEDs"
339 depends on LEDS_CLASS
340 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
341 MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2
344 This option enable support for the dual-GPIO LED found on the
345 Network Space v2 board (and parents). This include Internet Space v2,
346 Network Space (Max) v2 and d2 Network v2 boards.
349 tristate "LED support for Big Network series LEDs"
350 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
351 depends on LEDS_CLASS
354 This option enable support for LEDs found on the LaCie 2Big
355 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
356 controlled through a GPIO extension bus.
359 bool "LED support for the HTC ASIC3"
360 depends on LEDS_CLASS
364 This option enables support for the LEDs on the HTC ASIC3. The HTC
365 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
366 cannot be used. This driver supports hardware blinking with an on+off
367 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
369 config LEDS_RENESAS_TPU
370 bool "LED support for Renesas TPU"
371 depends on LEDS_CLASS && HAVE_CLK && GENERIC_GPIO
373 This option enables build of the LED TPU platform driver,
374 suitable to drive any TPU channel on newer Renesas SoCs.
375 The driver controls the GPIO pin connected to the LED via
376 the GPIO framework and expects the LED to be connected to
377 a pin that can be driven in both GPIO mode and using TPU
378 pin function. The latter to support brightness control.
379 Brightness control is supported but hardware blinking is not.
382 tristate "LED Support for TCA6507 I2C chip"
383 depends on LEDS_CLASS && I2C
385 This option enables support for LEDs connected to TC6507
386 LED driver chips accessed via the I2C bus.
387 Driver support brightness control and hardware-assisted blinking.
390 tristate "LED support for MAX8997 PMIC"
391 depends on LEDS_CLASS && MFD_MAX8997
393 This option enables support for on-chip LED drivers on
397 tristate "LED support for the Bachmann OT200"
398 depends on LEDS_CLASS && HAS_IOMEM
400 This option enables support for the LEDs on the Bachmann OT200.
401 Say Y to enable LEDs on the Bachmann OT200.
404 bool "LED Trigger support"
405 depends on LEDS_CLASS
407 This option enables trigger support for the leds class.
408 These triggers allow kernel events to drive the LEDs and can
409 be configured via sysfs. If unsure, say Y.
411 comment "LED Triggers"
413 config LEDS_TRIGGER_TIMER
414 tristate "LED Timer Trigger"
415 depends on LEDS_TRIGGERS
417 This allows LEDs to be controlled by a programmable timer
418 via sysfs. Some LED hardware can be programmed to start
419 blinking the LED without any further software interaction.
420 For more details read Documentation/leds/leds-class.txt.
424 config LEDS_TRIGGER_IDE_DISK
425 bool "LED IDE Disk Trigger"
426 depends on IDE_GD_ATA
427 depends on LEDS_TRIGGERS
429 This allows LEDs to be controlled by IDE disk activity.
432 config LEDS_TRIGGER_HEARTBEAT
433 tristate "LED Heartbeat Trigger"
434 depends on LEDS_TRIGGERS
436 This allows LEDs to be controlled by a CPU load average.
437 The flash frequency is a hyperbolic function of the 1-minute
441 config LEDS_TRIGGER_BACKLIGHT
442 tristate "LED backlight Trigger"
443 depends on LEDS_TRIGGERS
445 This allows LEDs to be controlled as a backlight device: they
446 turn off and on when the display is blanked and unblanked.
450 config LEDS_TRIGGER_GPIO
451 tristate "LED GPIO Trigger"
452 depends on LEDS_TRIGGERS
455 This allows LEDs to be controlled by gpio events. It's good
456 when using gpios as switches and triggering the needed LEDs
457 from there. One use case is n810's keypad LEDs that could
458 be triggered by this trigger when user slides up to show
463 config LEDS_TRIGGER_DEFAULT_ON
464 tristate "LED Default ON Trigger"
465 depends on LEDS_TRIGGERS
467 This allows LEDs to be initialised in the ON state.
470 comment "iptables trigger is under Netfilter config (LED target)"
471 depends on LEDS_TRIGGERS