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.
117 tristate "LED Support for ALIX.2 and ALIX.3 series"
118 depends on LEDS_CLASS
119 depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
121 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
122 You have to set leds-alix2.force=1 for boards with Award BIOS.
124 config LEDS_COBALT_QUBE
125 tristate "LED Support for the Cobalt Qube series front LED"
126 depends on LEDS_CLASS
127 depends on MIPS_COBALT
129 This option enables support for the front LED on Cobalt Qube series
131 config LEDS_COBALT_RAQ
132 bool "LED Support for the Cobalt Raq series"
133 depends on LEDS_CLASS=y && MIPS_COBALT
136 This option enables support for the Cobalt Raq series LEDs.
139 tristate "LED support for SunFire servers."
140 depends on LEDS_CLASS
144 This option enables support for the Left, Middle, and Right
145 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
148 tristate "LED Support for the HP Jornada 6xx"
149 depends on LEDS_CLASS
152 This option enables LED support for the handheld
153 HP Jornada 620/660/680/690.
156 tristate "LED driver for PCA9532 dimmer"
157 depends on LEDS_CLASS
158 depends on I2C && INPUT && EXPERIMENTAL
160 This option enables support for NXP pca9532
161 LED controller. It is generally only useful
164 config LEDS_PCA9532_GPIO
165 bool "Enable GPIO support for PCA9532"
166 depends on LEDS_PCA9532
169 Allow unused pins on PCA9532 to be used as gpio.
171 To use a pin as gpio pca9532_type in pca9532_platform data needs to
172 set to PCA9532_TYPE_GPIO.
175 tristate "LED Support for GPIO connected LEDs"
176 depends on LEDS_CLASS
177 depends on GENERIC_GPIO
179 This option enables support for the LEDs connected to GPIO
180 outputs. To be useful the particular board must have LEDs
181 and they must be connected to the GPIO lines. The LEDs must be
182 defined as platform devices and/or OpenFirmware platform devices.
183 The code to use these bindings can be selected below.
186 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
187 depends on LEDS_CLASS
190 This option enables support for LEDs connected to the National
191 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
194 To compile this driver as a module, choose M here: the
195 module will be called leds-lp3944.
198 tristate "LED Support for N.S. LP5521 LED driver chip"
199 depends on LEDS_CLASS && I2C
201 If you say yes here you get support for the National Semiconductor
202 LP5521 LED driver. It is 3 channel chip with programmable engines.
203 Driver provides direct control via LED class and interface for
204 programming the engines.
207 tristate "LED Support for N.S. LP5523 LED driver chip"
208 depends on LEDS_CLASS && I2C
210 If you say yes here you get support for the National Semiconductor
211 LP5523 LED driver. It is 9 channel chip with programmable engines.
212 Driver provides direct control via LED class and interface for
213 programming the engines.
215 config LEDS_CLEVO_MAIL
216 tristate "Mail LED on Clevo notebook"
217 depends on LEDS_CLASS
218 depends on X86 && SERIO_I8042 && DMI
220 This driver makes the mail LED accessible from userspace
221 programs through the leds subsystem. This LED have three
222 known mode: off, blink at 0.5Hz and blink at 1Hz.
224 The driver supports two kinds of interface: using ledtrig-timer
225 or through /sys/class/leds/clevo::mail/brightness. As this LED
226 cannot change it's brightness it blinks instead. The brightness
227 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
230 This module can drive the mail LED for the following notebooks:
235 Clevo D400V/D470V (not tested, but might work)
237 Clevo M5x0N (not tested, but might work)
238 Positivo Mobile (Clevo M5x0V)
240 If your model is not listed here you can try the "nodetect"
243 To compile this driver as a module, choose M here: the
244 module will be called leds-clevo-mail.
247 tristate "LED Support for PCA955x I2C chips"
248 depends on LEDS_CLASS
251 This option enables support for LEDs connected to PCA955x
252 LED driver chips accessed via the I2C bus. Supported
253 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
255 config LEDS_WM831X_STATUS
256 tristate "LED support for status LEDs on WM831x PMICs"
257 depends on LEDS_CLASS
258 depends on MFD_WM831X
260 This option enables support for the status LEDs of the WM831x
264 tristate "LED Support for WM8350 AudioPlus PMIC"
265 depends on LEDS_CLASS
266 depends on MFD_WM8350
268 This option enables support for LEDs driven by the Wolfson
269 Microelectronics WM8350 AudioPlus PMIC.
272 tristate "LED Support for DA9030/DA9034 PMIC"
273 depends on LEDS_CLASS
274 depends on PMIC_DA903X
276 This option enables support for on-chip LED drivers found
277 on Dialog Semiconductor DA9030/DA9034 PMICs.
279 config LEDS_DAC124S085
280 tristate "LED Support for DAC124S085 SPI DAC"
281 depends on LEDS_CLASS
284 This option enables support for DAC124S085 SPI DAC from NatSemi,
285 which can be used to control up to four LEDs.
288 tristate "PWM driven LED Support"
289 depends on LEDS_CLASS
292 This option enables support for pwm driven LEDs
294 config LEDS_REGULATOR
295 tristate "REGULATOR driven LED support"
296 depends on LEDS_CLASS
299 This option enables support for regulator driven LEDs.
302 tristate "LED driver for BD2802 RGB LED"
303 depends on LEDS_CLASS
306 This option enables support for BD2802GU RGB LED driver chips
307 accessed via the I2C bus.
309 config LEDS_INTEL_SS4200
310 tristate "LED driver for Intel NAS SS4200 series"
311 depends on LEDS_CLASS
312 depends on PCI && DMI
315 This option enables support for the Intel SS4200 series of
316 Network Attached Storage servers. You may control the hard
317 drive or power LEDs on the front panel. Using this driver
318 can stop the front LED from blinking after startup.
321 tristate "LED driver for LT3593 controllers"
322 depends on LEDS_CLASS
323 depends on GENERIC_GPIO
325 This option enables support for LEDs driven by a Linear Technology
326 LT3593 controller. This controller uses a special one-wire pulse
327 coding protocol to set the brightness.
330 tristate "LED Support for ADP5520/ADP5501 PMIC"
331 depends on LEDS_CLASS
332 depends on PMIC_ADP5520
334 This option enables support for on-chip LED drivers found
335 on Analog Devices ADP5520/ADP5501 PMICs.
337 To compile this driver as a module, choose M here: the module will
338 be called leds-adp5520.
340 config LEDS_DELL_NETBOOKS
341 tristate "External LED on Dell Business Netbooks"
342 depends on LEDS_CLASS
343 depends on X86 && ACPI_WMI
345 This adds support for the Latitude 2100 and similar
346 notebooks that have an external LED.
349 tristate "LED Support for MC13783 PMIC"
350 depends on LEDS_CLASS
351 depends on MFD_MC13783
353 This option enable support for on-chip LED drivers found
354 on Freescale Semiconductor MC13783 PMIC.
357 tristate "LED support for Network Space v2 GPIO LEDs"
358 depends on LEDS_CLASS
359 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
362 This option enable support for the dual-GPIO LED found on the
363 Network Space v2 board (and parents). This include Internet Space v2,
364 Network Space (Max) v2 and d2 Network v2 boards.
367 tristate "LED support for Big Network series LEDs"
368 depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
369 depends on LEDS_CLASS
372 This option enable support for LEDs found on the LaCie 2Big
373 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
374 controlled through a GPIO extension bus.
377 bool "LED support for the HTC ASIC3"
378 depends on LEDS_CLASS
382 This option enables support for the LEDs on the HTC ASIC3. The HTC
383 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
384 cannot be used. This driver supports hardware blinking with an on+off
385 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
388 bool "LED Trigger support"
389 depends on LEDS_CLASS
391 This option enables trigger support for the leds class.
392 These triggers allow kernel events to drive the LEDs and can
393 be configured via sysfs. If unsure, say Y.
395 comment "LED Triggers"
397 config LEDS_TRIGGER_TIMER
398 tristate "LED Timer Trigger"
399 depends on LEDS_TRIGGERS
401 This allows LEDs to be controlled by a programmable timer
402 via sysfs. Some LED hardware can be programmed to start
403 blinking the LED without any further software interaction.
404 For more details read Documentation/leds-class.txt.
408 config LEDS_TRIGGER_IDE_DISK
409 bool "LED IDE Disk Trigger"
410 depends on IDE_GD_ATA
411 depends on LEDS_TRIGGERS
413 This allows LEDs to be controlled by IDE disk activity.
416 config LEDS_TRIGGER_HEARTBEAT
417 tristate "LED Heartbeat Trigger"
418 depends on LEDS_TRIGGERS
420 This allows LEDs to be controlled by a CPU load average.
421 The flash frequency is a hyperbolic function of the 1-minute
425 config LEDS_TRIGGER_BACKLIGHT
426 tristate "LED backlight Trigger"
427 depends on LEDS_TRIGGERS
429 This allows LEDs to be controlled as a backlight device: they
430 turn off and on when the display is blanked and unblanked.
434 config LEDS_TRIGGER_GPIO
435 tristate "LED GPIO Trigger"
436 depends on LEDS_TRIGGERS
439 This allows LEDs to be controlled by gpio events. It's good
440 when using gpios as switches and triggering the needed LEDs
441 from there. One use case is n810's keypad LEDs that could
442 be triggered by this trigger when user slides up to show
447 config LEDS_TRIGGER_DEFAULT_ON
448 tristate "LED Default ON Trigger"
449 depends on LEDS_TRIGGERS
451 This allows LEDs to be initialised in the ON state.
454 comment "iptables trigger is under Netfilter config (LED target)"
455 depends on LEDS_TRIGGERS