4 Say Y to enable Linux LED support. This allows control of supported
5 LEDs from both userspace and optionally, by kernel events (triggers).
7 This is not related to standard keyboard LEDs which are controlled
13 tristate "LED Class Support"
15 This option enables the led sysfs class in /sys/class/leds. You'll
16 need this to do anything useful with LEDs. If unsure, say N.
23 tristate "LED Support for Marvell 88PM860x PMIC"
24 depends on MFD_88PM860X
26 This option enables support for on-chip LED drivers found on Marvell
27 Semiconductor 88PM8606 PMIC.
30 tristate "LED Support using Atmel PWM outputs"
33 This option enables support for LEDs driven using outputs
34 of the dedicated PWM controller found on newer Atmel SOCs.
37 tristate "LED Support for Locomo device"
38 depends on SHARP_LOCOMO
40 This option enables support for the LEDs on Sharp Locomo.
41 Zaurus models SL-5500 and SL-5600.
43 config LEDS_MIKROTIK_RB532
44 tristate "LED Support for Mikrotik Routerboard 532"
45 depends on MIKROTIK_RB532
47 This option enables support for the so called "User LED" of
48 Mikrotik's Routerboard 532.
51 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
52 depends on ARCH_S3C2410
54 This option enables support for LEDs connected to GPIO lines
55 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
58 tristate "LED Support for the Amstrad Delta (E3)"
59 depends on MACH_AMS_DELTA
61 This option enables support for the LEDs on Amstrad Delta (E3).
64 tristate "LED Support for Soekris net48xx series Error LED"
65 depends on SCx200_GPIO
67 This option enables support for the Soekris net4801 and net4826 error
71 tristate "LED Support for Soekris net5501 series Error LED"
72 depends on LEDS_TRIGGERS
73 depends on X86 && LEDS_GPIO_PLATFORM && GPIO_CS5535
74 select LEDS_TRIGGER_DEFAULT_ON
77 Add support for the Soekris net5501 board (detection, error led
81 tristate "LED Support for the Freecom FSG-3"
84 This option enables support for the LEDs on the Freecom FSG-3.
87 tristate "LED Support for the WRAP series LEDs"
88 depends on SCx200_GPIO
90 This option enables support for the PCEngines WRAP programmable LEDs.
93 tristate "LED Support for ALIX.2 and ALIX.3 series"
94 depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
96 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
97 You have to set leds-alix2.force=1 for boards with Award BIOS.
100 tristate "LED Support for iPAQ H1940 device"
101 depends on ARCH_H1940
103 This option enables support for the LEDs on the h1940.
105 config LEDS_COBALT_QUBE
106 tristate "LED Support for the Cobalt Qube series front LED"
107 depends on MIPS_COBALT
109 This option enables support for the front LED on Cobalt Qube series
111 config LEDS_COBALT_RAQ
112 bool "LED Support for the Cobalt Raq series"
113 depends on LEDS_CLASS=y && MIPS_COBALT
116 This option enables support for the Cobalt Raq series LEDs.
119 tristate "LED support for SunFire servers."
123 This option enables support for the Left, Middle, and Right
124 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
127 tristate "LED Support for the HP Jornada 6xx"
130 This option enables LED support for the handheld
131 HP Jornada 620/660/680/690.
134 tristate "LED driver for PCA9532 dimmer"
135 depends on I2C && INPUT && EXPERIMENTAL
137 This option enables support for NXP pca9532
138 LED controller. It is generally only useful
142 tristate "LED Support for GPIO connected LEDs"
143 depends on GENERIC_GPIO
145 This option enables support for the LEDs connected to GPIO
146 outputs. To be useful the particular board must have LEDs
147 and they must be connected to the GPIO lines. The LEDs must be
148 defined as platform devices and/or OpenFirmware platform devices.
149 The code to use these bindings can be selected below.
151 config LEDS_GPIO_PLATFORM
152 bool "Platform device bindings for GPIO LEDs"
156 Let the leds-gpio driver drive LEDs which have been defined as
157 platform devices. If you don't know what this means, say yes.
160 bool "OpenFirmware platform device bindings for GPIO LEDs"
161 depends on LEDS_GPIO && OF_DEVICE
164 Let the leds-gpio driver drive LEDs which have been defined as
165 of_platform devices. For instance, LEDs which are listed in a "dts"
168 config LEDS_NEWTON_PWM
169 bool "LED Support for newton pwm"
170 depends on LEDS_CLASS&&ARCH_RK29
173 Let the leds-gpio driver drive LEDs which have been defined as
174 platform devices. If you don't know what this means, say yes.
177 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
180 This option enables support for LEDs connected to the National
181 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
184 To compile this driver as a module, choose M here: the
185 module will be called leds-lp3944.
187 config LEDS_CLEVO_MAIL
188 tristate "Mail LED on Clevo notebook"
189 depends on X86 && SERIO_I8042 && DMI
191 This driver makes the mail LED accessible from userspace
192 programs through the leds subsystem. This LED have three
193 known mode: off, blink at 0.5Hz and blink at 1Hz.
195 The driver supports two kinds of interface: using ledtrig-timer
196 or through /sys/class/leds/clevo::mail/brightness. As this LED
197 cannot change it's brightness it blinks instead. The brightness
198 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
201 This module can drive the mail LED for the following notebooks:
206 Clevo D400V/D470V (not tested, but might work)
208 Clevo M5x0N (not tested, but might work)
209 Positivo Mobile (Clevo M5x0V)
211 If your model is not listed here you can try the "nodetect"
214 To compile this driver as a module, choose M here: the
215 module will be called leds-clevo-mail.
218 tristate "LED Support for PCA955x I2C chips"
221 This option enables support for LEDs connected to PCA955x
222 LED driver chips accessed via the I2C bus. Supported
223 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
225 config LEDS_WM831X_STATUS
226 tristate "LED support for status LEDs on WM831x PMICs"
227 depends on MFD_WM831X
229 This option enables support for the status LEDs of the WM831x
233 tristate "LED Support for WM8350 AudioPlus PMIC"
234 depends on MFD_WM8350
236 This option enables support for LEDs driven by the Wolfson
237 Microelectronics WM8350 AudioPlus PMIC.
240 tristate "LED Support for DA9030/DA9034 PMIC"
241 depends on PMIC_DA903X
243 This option enables support for on-chip LED drivers found
244 on Dialog Semiconductor DA9030/DA9034 PMICs.
246 config LEDS_DAC124S085
247 tristate "LED Support for DAC124S085 SPI DAC"
250 This option enables support for DAC124S085 SPI DAC from NatSemi,
251 which can be used to control up to four LEDs.
254 tristate "PWM driven LED Support"
257 This option enables support for pwm driven LEDs
259 config LEDS_REGULATOR
260 tristate "REGULATOR driven LED support"
263 This option enables support for regulator driven LEDs.
266 tristate "LED driver for BD2802 RGB LED"
269 This option enables support for BD2802GU RGB LED driver chips
270 accessed via the I2C bus.
273 tristate "LED driver for ATT1272 LED"
274 depends on LEDS_CLASS && I2C
276 This option enables support for ATT1272 LED driver chips
277 accessed via the I2C bus.
279 config LEDS_INTEL_SS4200
280 tristate "LED driver for Intel NAS SS4200 series"
281 depends on PCI && DMI
283 This option enables support for the Intel SS4200 series of
284 Network Attached Storage servers. You may control the hard
285 drive or power LEDs on the front panel. Using this driver
286 can stop the front LED from blinking after startup.
289 tristate "LED driver for LT3593 controllers"
290 depends on GENERIC_GPIO
292 This option enables support for LEDs driven by a Linear Technology
293 LT3593 controller. This controller uses a special one-wire pulse
294 coding protocol to set the brightness.
297 tristate "LED Support for ADP5520/ADP5501 PMIC"
298 depends on PMIC_ADP5520
300 This option enables support for on-chip LED drivers found
301 on Analog Devices ADP5520/ADP5501 PMICs.
303 To compile this driver as a module, choose M here: the module will
304 be called leds-adp5520.
306 config LEDS_DELL_NETBOOKS
307 tristate "External LED on Dell Business Netbooks"
308 depends on X86 && ACPI_WMI
310 This adds support for the Latitude 2100 and similar
311 notebooks that have an external LED.
314 tristate "LED Support for MC13783 PMIC"
315 depends on MFD_MC13783
317 This option enable support for on-chip LED drivers found
318 on Freescale Semiconductor MC13783 PMIC.
321 tristate "LED support for Network Space v2 GPIO LEDs"
322 depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2
325 This option enable support for the dual-GPIO LED found on the
326 Network Space v2 board (and parents). This include Internet Space v2,
327 Network Space (Max) v2 and d2 Network v2 boards.
330 bool "LED Trigger support"
332 This option enables trigger support for the leds class.
333 These triggers allow kernel events to drive the LEDs and can
334 be configured via sysfs. If unsure, say Y.
338 comment "LED Triggers"
340 config LEDS_TRIGGER_TIMER
341 tristate "LED Timer Trigger"
343 This allows LEDs to be controlled by a programmable timer
344 via sysfs. Some LED hardware can be programmed to start
345 blinking the LED without any further software interaction.
346 For more details read Documentation/leds-class.txt.
350 config LEDS_TRIGGER_IDE_DISK
351 bool "LED IDE Disk Trigger"
352 depends on IDE_GD_ATA
354 This allows LEDs to be controlled by IDE disk activity.
357 config LEDS_TRIGGER_HEARTBEAT
358 tristate "LED Heartbeat Trigger"
360 This allows LEDs to be controlled by a CPU load average.
361 The flash frequency is a hyperbolic function of the 1-minute
365 config LEDS_TRIGGER_BACKLIGHT
366 tristate "LED backlight Trigger"
368 This allows LEDs to be controlled as a backlight device: they
369 turn off and on when the display is blanked and unblanked.
373 config LEDS_TRIGGER_GPIO
374 tristate "LED GPIO Trigger"
377 This allows LEDs to be controlled by gpio events. It's good
378 when using gpios as switches and triggering the needed LEDs
379 from there. One use case is n810's keypad LEDs that could
380 be triggered by this trigger when user slides up to show
385 config LEDS_TRIGGER_DEFAULT_ON
386 tristate "LED Default ON Trigger"
388 This allows LEDs to be initialised in the ON state.
391 comment "iptables trigger is under Netfilter config (LED target)"
392 depends on LEDS_TRIGGERS
394 endif # LEDS_TRIGGERS