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 Soekris net5501 series Error LED"
94 depends on LEDS_TRIGGERS
95 depends on X86 && GPIO_CS5535
96 select LEDS_TRIGGER_DEFAULT_ON
99 Add support for the Soekris net5501 board (detection, error led
103 tristate "LED Support for the Freecom FSG-3"
104 depends on LEDS_CLASS
107 This option enables support for the LEDs on the Freecom FSG-3.
110 tristate "LED Support for the WRAP series LEDs"
111 depends on LEDS_CLASS
112 depends on SCx200_GPIO
114 This option enables support for the PCEngines WRAP programmable LEDs.
116 config LEDS_COBALT_QUBE
117 tristate "LED Support for the Cobalt Qube series front LED"
118 depends on LEDS_CLASS
119 depends on MIPS_COBALT
121 This option enables support for the front LED on Cobalt Qube series
123 config LEDS_COBALT_RAQ
124 bool "LED Support for the Cobalt Raq series"
125 depends on LEDS_CLASS=y && MIPS_COBALT
128 This option enables support for the Cobalt Raq series LEDs.
131 tristate "LED support for SunFire servers."
132 depends on LEDS_CLASS
136 This option enables support for the Left, Middle, and Right
137 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
140 tristate "LED Support for the HP Jornada 6xx"
141 depends on LEDS_CLASS
144 This option enables LED support for the handheld
145 HP Jornada 620/660/680/690.
148 tristate "LED driver for PCA9532 dimmer"
149 depends on LEDS_CLASS
150 depends on I2C && INPUT && EXPERIMENTAL
152 This option enables support for NXP pca9532
153 LED controller. It is generally only useful
156 config LEDS_PCA9532_GPIO
157 bool "Enable GPIO support for PCA9532"
158 depends on LEDS_PCA9532
161 Allow unused pins on PCA9532 to be used as gpio.
163 To use a pin as gpio pca9532_type in pca9532_platform data needs to
164 set to PCA9532_TYPE_GPIO.
167 tristate "LED Support for GPIO connected LEDs"
168 depends on LEDS_CLASS
169 depends on GENERIC_GPIO
171 This option enables support for the LEDs connected to GPIO
172 outputs. To be useful the particular board must have LEDs
173 and they must be connected to the GPIO lines. The LEDs must be
174 defined as platform devices and/or OpenFirmware platform devices.
175 The code to use these bindings can be selected below.
178 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
179 depends on LEDS_CLASS
182 This option enables support for LEDs connected to the National
183 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
186 To compile this driver as a module, choose M here: the
187 module will be called leds-lp3944.
190 tristate "LED Support for N.S. LP5521 LED driver chip"
191 depends on LEDS_CLASS && I2C
193 If you say yes here you get support for the National Semiconductor
194 LP5521 LED driver. It is 3 channel chip with programmable engines.
195 Driver provides direct control via LED class and interface for
196 programming the engines.
199 tristate "LED Support for N.S. LP5523 LED driver chip"
200 depends on LEDS_CLASS && I2C
202 If you say yes here you get support for the National Semiconductor
203 LP5523 LED driver. It is 9 channel chip with programmable engines.
204 Driver provides direct control via LED class and interface for
205 programming the engines.
207 config LEDS_CLEVO_MAIL
208 tristate "Mail LED on Clevo notebook"
209 depends on LEDS_CLASS
210 depends on X86 && SERIO_I8042 && DMI
212 This driver makes the mail LED accessible from userspace
213 programs through the leds subsystem. This LED have three
214 known mode: off, blink at 0.5Hz and blink at 1Hz.
216 The driver supports two kinds of interface: using ledtrig-timer
217 or through /sys/class/leds/clevo::mail/brightness. As this LED
218 cannot change it's brightness it blinks instead. The brightness
219 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
222 This module can drive the mail LED for the following notebooks:
227 Clevo D400V/D470V (not tested, but might work)
229 Clevo M5x0N (not tested, but might work)
230 Positivo Mobile (Clevo M5x0V)
232 If your model is not listed here you can try the "nodetect"
235 To compile this driver as a module, choose M here: the
236 module will be called leds-clevo-mail.
239 tristate "LED Support for PCA955x I2C chips"
240 depends on LEDS_CLASS
243 This option enables support for LEDs connected to PCA955x
244 LED driver chips accessed via the I2C bus. Supported
245 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
247 config LEDS_WM831X_STATUS
248 tristate "LED support for status LEDs on WM831x PMICs"
249 depends on LEDS_CLASS
250 depends on MFD_WM831X
252 This option enables support for the status LEDs of the WM831x
256 tristate "LED Support for WM8350 AudioPlus PMIC"
257 depends on LEDS_CLASS
258 depends on MFD_WM8350
260 This option enables support for LEDs driven by the Wolfson
261 Microelectronics WM8350 AudioPlus PMIC.
264 tristate "LED Support for DA9030/DA9034 PMIC"
265 depends on LEDS_CLASS
266 depends on PMIC_DA903X
268 This option enables support for on-chip LED drivers found
269 on Dialog Semiconductor DA9030/DA9034 PMICs.
271 config LEDS_DAC124S085
272 tristate "LED Support for DAC124S085 SPI DAC"
273 depends on LEDS_CLASS
276 This option enables support for DAC124S085 SPI DAC from NatSemi,
277 which can be used to control up to four LEDs.
280 tristate "PWM driven LED Support"
281 depends on LEDS_CLASS
284 This option enables support for pwm driven LEDs
286 config LEDS_TWL4030_PWM
287 tristate "LED driver for TWL4030 PWM connected LEDs"
288 depends on LEDS_CLASS && TWL4030_CORE
290 This option enables support for TWL4030 PWM driven LEDs
292 config LEDS_REGULATOR
293 tristate "REGULATOR driven LED support"
294 depends on LEDS_CLASS
297 This option enables support for regulator driven LEDs.
300 tristate "LED driver for BD2802 RGB LED"
301 depends on LEDS_CLASS
304 This option enables support for BD2802GU RGB LED driver chips
305 accessed via the I2C bus.
307 config LEDS_INTEL_SS4200
308 tristate "LED driver for Intel NAS SS4200 series"
309 depends on LEDS_CLASS
310 depends on PCI && DMI
312 This option enables support for the Intel SS4200 series of
313 Network Attached Storage servers. You may control the hard
314 drive or power LEDs on the front panel. Using this driver
315 can stop the front LED from blinking after startup.
318 tristate "LED driver for LT3593 controllers"
319 depends on LEDS_CLASS
320 depends on GENERIC_GPIO
322 This option enables support for LEDs driven by a Linear Technology
323 LT3593 controller. This controller uses a special one-wire pulse
324 coding protocol to set the brightness.
327 tristate "LED Support for ADP5520/ADP5501 PMIC"
328 depends on LEDS_CLASS
329 depends on PMIC_ADP5520
331 This option enables support for on-chip LED drivers found
332 on Analog Devices ADP5520/ADP5501 PMICs.
334 To compile this driver as a module, choose M here: the module will
335 be called leds-adp5520.
337 config LEDS_DELL_NETBOOKS
338 tristate "External LED on Dell Business Netbooks"
339 depends on LEDS_CLASS
340 depends on X86 && ACPI_WMI
342 This adds support for the Latitude 2100 and similar
343 notebooks that have an external LED.
346 tristate "LED Support for MC13783 PMIC"
347 depends on LEDS_CLASS
348 depends on MFD_MC13783
350 This option enable support for on-chip LED drivers found
351 on Freescale Semiconductor MC13783 PMIC.
354 tristate "LED support for Network Space v2 GPIO LEDs"
355 depends on LEDS_CLASS
356 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
359 This option enable support for the dual-GPIO LED found on the
360 Network Space v2 board (and parents). This include Internet Space v2,
361 Network Space (Max) v2 and d2 Network v2 boards.
364 tristate "LED support for Big Network series LEDs"
365 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
366 depends on LEDS_CLASS
369 This option enable support for LEDs found on the LaCie 2Big
370 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
371 controlled through a GPIO extension bus.
374 bool "LED support for the HTC ASIC3"
375 depends on LEDS_CLASS
379 This option enables support for the LEDs on the HTC ASIC3. The HTC
380 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
381 cannot be used. This driver supports hardware blinking with an on+off
382 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
384 config LEDS_RENESAS_TPU
385 bool "LED support for Renesas TPU"
386 depends on LEDS_CLASS && HAVE_CLK && GENERIC_GPIO
388 This option enables build of the LED TPU platform driver,
389 suitable to drive any TPU channel on newer Renesas SoCs.
390 The driver controls the GPIO pin connected to the LED via
391 the GPIO framework and expects the LED to be connected to
392 a pin that can be driven in both GPIO mode and using TPU
393 pin function. The latter to support brightness control.
394 Brightness control is supported but hardware blinking is not.
397 bool "LED Trigger support"
398 depends on LEDS_CLASS
400 This option enables trigger support for the leds class.
401 These triggers allow kernel events to drive the LEDs and can
402 be configured via sysfs. If unsure, say Y.
404 comment "LED Triggers"
406 config LEDS_TRIGGER_TIMER
407 tristate "LED Timer Trigger"
408 depends on LEDS_TRIGGERS
410 This allows LEDs to be controlled by a programmable timer
411 via sysfs. Some LED hardware can be programmed to start
412 blinking the LED without any further software interaction.
413 For more details read Documentation/leds/leds-class.txt.
417 config LEDS_TRIGGER_IDE_DISK
418 bool "LED IDE Disk Trigger"
419 depends on IDE_GD_ATA
420 depends on LEDS_TRIGGERS
422 This allows LEDs to be controlled by IDE disk activity.
425 config LEDS_TRIGGER_HEARTBEAT
426 tristate "LED Heartbeat Trigger"
427 depends on LEDS_TRIGGERS
429 This allows LEDs to be controlled by a CPU load average.
430 The flash frequency is a hyperbolic function of the 1-minute
434 config LEDS_TRIGGER_BACKLIGHT
435 tristate "LED backlight Trigger"
436 depends on LEDS_TRIGGERS
438 This allows LEDs to be controlled as a backlight device: they
439 turn off and on when the display is blanked and unblanked.
443 config LEDS_TRIGGER_GPIO
444 tristate "LED GPIO Trigger"
445 depends on LEDS_TRIGGERS
448 This allows LEDs to be controlled by gpio events. It's good
449 when using gpios as switches and triggering the needed LEDs
450 from there. One use case is n810's keypad LEDs that could
451 be triggered by this trigger when user slides up to show
456 config LEDS_TRIGGER_DEFAULT_ON
457 tristate "LED Default ON Trigger"
458 depends on LEDS_TRIGGERS
460 This allows LEDs to be initialised in the ON state.
463 comment "iptables trigger is under Netfilter config (LED target)"
464 depends on LEDS_TRIGGERS