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.
21 tristate "LED Support for Marvell 88PM860x PMIC"
22 depends on LEDS_CLASS && MFD_88PM860X
24 This option enables support for on-chip LED drivers found on Marvell
25 Semiconductor 88PM8606 PMIC.
28 tristate "LED Support using Atmel PWM outputs"
29 depends on LEDS_CLASS && ATMEL_PWM
31 This option enables support for LEDs driven using outputs
32 of the dedicated PWM controller found on newer Atmel SOCs.
35 tristate "LED Support for Locomo device"
36 depends on LEDS_CLASS && SHARP_LOCOMO
38 This option enables support for the LEDs on Sharp Locomo.
39 Zaurus models SL-5500 and SL-5600.
41 config LEDS_MIKROTIK_RB532
42 tristate "LED Support for Mikrotik Routerboard 532"
43 depends on LEDS_CLASS && MIKROTIK_RB532
45 This option enables support for the so called "User LED" of
46 Mikrotik's Routerboard 532.
49 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
50 depends on LEDS_CLASS && ARCH_S3C2410
52 This option enables support for LEDs connected to GPIO lines
53 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
56 tristate "LED Support for the Amstrad Delta (E3)"
57 depends on LEDS_CLASS && MACH_AMS_DELTA
59 This option enables support for the LEDs on Amstrad Delta (E3).
62 tristate "LED Support for Soekris net48xx series Error LED"
63 depends on LEDS_CLASS && SCx200_GPIO
65 This option enables support for the Soekris net4801 and net4826 error
69 tristate "LED Support for the Freecom FSG-3"
70 depends on LEDS_CLASS && MACH_FSG
72 This option enables support for the LEDs on the Freecom FSG-3.
75 tristate "LED Support for the WRAP series LEDs"
76 depends on LEDS_CLASS && SCx200_GPIO
78 This option enables support for the PCEngines WRAP programmable LEDs.
81 tristate "LED Support for ALIX.2 and ALIX.3 series"
82 depends on LEDS_CLASS && X86 && EXPERIMENTAL
84 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
85 You have to set leds-alix2.force=1 for boards with Award BIOS.
88 tristate "LED Support for iPAQ H1940 device"
89 depends on LEDS_CLASS && ARCH_H1940
91 This option enables support for the LEDs on the h1940.
93 config LEDS_COBALT_QUBE
94 tristate "LED Support for the Cobalt Qube series front LED"
95 depends on LEDS_CLASS && MIPS_COBALT
97 This option enables support for the front LED on Cobalt Qube series
99 config LEDS_COBALT_RAQ
100 bool "LED Support for the Cobalt Raq series"
101 depends on LEDS_CLASS=y && MIPS_COBALT
104 This option enables support for the Cobalt Raq series LEDs.
107 tristate "LED support for SunFire servers."
108 depends on LEDS_CLASS && SPARC64
111 This option enables support for the Left, Middle, and Right
112 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
115 tristate "LED Support for the HP Jornada 6xx"
116 depends on LEDS_CLASS && SH_HP6XX
118 This option enables LED support for the handheld
119 HP Jornada 620/660/680/690.
122 tristate "LED driver for PCA9532 dimmer"
123 depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
125 This option enables support for NXP pca9532
126 LED controller. It is generally only useful
130 tristate "LED Support for GPIO connected LEDs"
131 depends on LEDS_CLASS && GENERIC_GPIO
133 This option enables support for the LEDs connected to GPIO
134 outputs. To be useful the particular board must have LEDs
135 and they must be connected to the GPIO lines. The LEDs must be
136 defined as platform devices and/or OpenFirmware platform devices.
137 The code to use these bindings can be selected below.
139 config LEDS_GPIO_PLATFORM
140 bool "Platform device bindings for GPIO LEDs"
144 Let the leds-gpio driver drive LEDs which have been defined as
145 platform devices. If you don't know what this means, say yes.
148 bool "OpenFirmware platform device bindings for GPIO LEDs"
149 depends on LEDS_GPIO && OF_DEVICE
152 Let the leds-gpio driver drive LEDs which have been defined as
153 of_platform devices. For instance, LEDs which are listed in a "dts"
157 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
158 depends on LEDS_CLASS && I2C
160 This option enables support for LEDs connected to the National
161 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
164 To compile this driver as a module, choose M here: the
165 module will be called leds-lp3944.
167 config LEDS_CLEVO_MAIL
168 tristate "Mail LED on Clevo notebook"
169 depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
171 This driver makes the mail LED accessible from userspace
172 programs through the leds subsystem. This LED have three
173 known mode: off, blink at 0.5Hz and blink at 1Hz.
175 The driver supports two kinds of interface: using ledtrig-timer
176 or through /sys/class/leds/clevo::mail/brightness. As this LED
177 cannot change it's brightness it blinks instead. The brightness
178 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
181 This module can drive the mail LED for the following notebooks:
186 Clevo D400V/D470V (not tested, but might work)
188 Clevo M5x0N (not tested, but might work)
189 Positivo Mobile (Clevo M5x0V)
191 If your model is not listed here you can try the "nodetect"
194 To compile this driver as a module, choose M here: the
195 module will be called leds-clevo-mail.
198 tristate "LED Support for PCA955x I2C chips"
199 depends on LEDS_CLASS && I2C
201 This option enables support for LEDs connected to PCA955x
202 LED driver chips accessed via the I2C bus. Supported
203 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
205 config LEDS_WM831X_STATUS
206 tristate "LED support for status LEDs on WM831x PMICs"
207 depends on LEDS_CLASS && MFD_WM831X
209 This option enables support for the status LEDs of the WM831x
213 tristate "LED Support for WM8350 AudioPlus PMIC"
214 depends on LEDS_CLASS && MFD_WM8350
216 This option enables support for LEDs driven by the Wolfson
217 Microelectronics WM8350 AudioPlus PMIC.
220 tristate "LED Support for DA9030/DA9034 PMIC"
221 depends on LEDS_CLASS && PMIC_DA903X
223 This option enables support for on-chip LED drivers found
224 on Dialog Semiconductor DA9030/DA9034 PMICs.
226 config LEDS_DAC124S085
227 tristate "LED Support for DAC124S085 SPI DAC"
228 depends on LEDS_CLASS && SPI
230 This option enables support for DAC124S085 SPI DAC from NatSemi,
231 which can be used to control up to four LEDs.
234 tristate "PWM driven LED Support"
235 depends on LEDS_CLASS && HAVE_PWM
237 This option enables support for pwm driven LEDs
239 config LEDS_REGULATOR
240 tristate "REGULATOR driven LED support"
241 depends on LEDS_CLASS && REGULATOR
243 This option enables support for regulator driven LEDs.
246 tristate "LED driver for BD2802 RGB LED"
247 depends on LEDS_CLASS && I2C
249 This option enables support for BD2802GU RGB LED driver chips
250 accessed via the I2C bus.
252 config LEDS_INTEL_SS4200
253 tristate "LED driver for Intel NAS SS4200 series"
254 depends on LEDS_CLASS && PCI && DMI
256 This option enables support for the Intel SS4200 series of
257 Network Attached Storage servers. You may control the hard
258 drive or power LEDs on the front panel. Using this driver
259 can stop the front LED from blinking after startup.
262 tristate "LED driver for LT3593 controllers"
263 depends on LEDS_CLASS && GENERIC_GPIO
265 This option enables support for LEDs driven by a Linear Technology
266 LT3593 controller. This controller uses a special one-wire pulse
267 coding protocol to set the brightness.
270 tristate "LED Support for ADP5520/ADP5501 PMIC"
271 depends on LEDS_CLASS && PMIC_ADP5520
273 This option enables support for on-chip LED drivers found
274 on Analog Devices ADP5520/ADP5501 PMICs.
276 To compile this driver as a module, choose M here: the module will
277 be called leds-adp5520.
279 comment "LED Triggers"
282 bool "LED Trigger support"
284 This option enables trigger support for the leds class.
285 These triggers allow kernel events to drive the LEDs and can
286 be configured via sysfs. If unsure, say Y.
288 config LEDS_TRIGGER_TIMER
289 tristate "LED Timer Trigger"
290 depends on LEDS_TRIGGERS
292 This allows LEDs to be controlled by a programmable timer
293 via sysfs. Some LED hardware can be programmed to start
294 blinking the LED without any further software interaction.
295 For more details read Documentation/leds-class.txt.
299 config LEDS_TRIGGER_IDE_DISK
300 bool "LED IDE Disk Trigger"
301 depends on LEDS_TRIGGERS && IDE_GD_ATA
303 This allows LEDs to be controlled by IDE disk activity.
306 config LEDS_TRIGGER_HEARTBEAT
307 tristate "LED Heartbeat Trigger"
308 depends on LEDS_TRIGGERS
310 This allows LEDs to be controlled by a CPU load average.
311 The flash frequency is a hyperbolic function of the 1-minute
315 config LEDS_TRIGGER_BACKLIGHT
316 tristate "LED backlight Trigger"
317 depends on LEDS_TRIGGERS
319 This allows LEDs to be controlled as a backlight device: they
320 turn off and on when the display is blanked and unblanked.
324 config LEDS_TRIGGER_GPIO
325 tristate "LED GPIO Trigger"
326 depends on LEDS_TRIGGERS
329 This allows LEDs to be controlled by gpio events. It's good
330 when using gpios as switches and triggering the needed LEDs
331 from there. One use case is n810's keypad LEDs that could
332 be triggered by this trigger when user slides up to show
337 config LEDS_TRIGGER_DEFAULT_ON
338 tristate "LED Default ON Trigger"
339 depends on LEDS_TRIGGERS
341 This allows LEDs to be initialised in the ON state.
344 comment "iptables trigger is under Netfilter config (LED target)"
345 depends on LEDS_TRIGGERS