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 using Atmel PWM outputs"
22 depends on LEDS_CLASS && ATMEL_PWM
24 This option enables support for LEDs driven using outputs
25 of the dedicated PWM controller found on newer Atmel SOCs.
28 tristate "LED Support for Locomo device"
29 depends on LEDS_CLASS && SHARP_LOCOMO
31 This option enables support for the LEDs on Sharp Locomo.
32 Zaurus models SL-5500 and SL-5600.
34 config LEDS_MIKROTIK_RB532
35 tristate "LED Support for Mikrotik Routerboard 532"
36 depends on LEDS_CLASS && MIKROTIK_RB532
38 This option enables support for the so called "User LED" of
39 Mikrotik's Routerboard 532.
42 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
43 depends on LEDS_CLASS && ARCH_S3C2410
45 This option enables support for LEDs connected to GPIO lines
46 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
49 tristate "LED Support for the Amstrad Delta (E3)"
50 depends on LEDS_CLASS && MACH_AMS_DELTA
52 This option enables support for the LEDs on Amstrad Delta (E3).
55 tristate "LED Support for Soekris net48xx series Error LED"
56 depends on LEDS_CLASS && SCx200_GPIO
58 This option enables support for the Soekris net4801 and net4826 error
62 tristate "LED Support for the Freecom FSG-3"
63 depends on LEDS_CLASS && MACH_FSG
65 This option enables support for the LEDs on the Freecom FSG-3.
68 tristate "LED Support for the WRAP series LEDs"
69 depends on LEDS_CLASS && SCx200_GPIO
71 This option enables support for the PCEngines WRAP programmable LEDs.
74 tristate "LED Support for ALIX.2 and ALIX.3 series"
75 depends on LEDS_CLASS && X86 && EXPERIMENTAL
77 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
80 tristate "LED Support for iPAQ H1940 device"
81 depends on LEDS_CLASS && ARCH_H1940
83 This option enables support for the LEDs on the h1940.
85 config LEDS_COBALT_QUBE
86 tristate "LED Support for the Cobalt Qube series front LED"
87 depends on LEDS_CLASS && MIPS_COBALT
89 This option enables support for the front LED on Cobalt Qube series
91 config LEDS_COBALT_RAQ
92 bool "LED Support for the Cobalt Raq series"
93 depends on LEDS_CLASS=y && MIPS_COBALT
96 This option enables support for the Cobalt Raq series LEDs.
99 tristate "LED support for SunFire servers."
100 depends on LEDS_CLASS && SPARC64
103 This option enables support for the Left, Middle, and Right
104 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
107 tristate "LED Support for the HP Jornada 6xx"
108 depends on LEDS_CLASS && SH_HP6XX
110 This option enables LED support for the handheld
111 HP Jornada 620/660/680/690.
114 tristate "LED driver for PCA9532 dimmer"
115 depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
117 This option enables support for NXP pca9532
118 LED controller. It is generally only useful
122 tristate "LED Support for GPIO connected LEDs"
123 depends on LEDS_CLASS && GENERIC_GPIO
125 This option enables support for the LEDs connected to GPIO
126 outputs. To be useful the particular board must have LEDs
127 and they must be connected to the GPIO lines. The LEDs must be
128 defined as platform devices and/or OpenFirmware platform devices.
129 The code to use these bindings can be selected below.
131 config LEDS_GPIO_PLATFORM
132 bool "Platform device bindings for GPIO LEDs"
136 Let the leds-gpio driver drive LEDs which have been defined as
137 platform devices. If you don't know what this means, say yes.
140 bool "OpenFirmware platform device bindings for GPIO LEDs"
141 depends on LEDS_GPIO && OF_DEVICE
144 Let the leds-gpio driver drive LEDs which have been defined as
145 of_platform devices. For instance, LEDs which are listed in a "dts"
148 config LEDS_CLEVO_MAIL
149 tristate "Mail LED on Clevo notebook"
150 depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
152 This driver makes the mail LED accessible from userspace
153 programs through the leds subsystem. This LED have three
154 known mode: off, blink at 0.5Hz and blink at 1Hz.
156 The driver supports two kinds of interface: using ledtrig-timer
157 or through /sys/class/leds/clevo::mail/brightness. As this LED
158 cannot change it's brightness it blinks instead. The brightness
159 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
162 This module can drive the mail LED for the following notebooks:
167 Clevo D400V/D470V (not tested, but might work)
169 Clevo M5x0N (not tested, but might work)
170 Positivo Mobile (Clevo M5x0V)
172 If your model is not listed here you can try the "nodetect"
175 To compile this driver as a module, choose M here: the
176 module will be called leds-clevo-mail.
179 tristate "LED Support for PCA955x I2C chips"
180 depends on LEDS_CLASS && I2C
182 This option enables support for LEDs connected to PCA955x
183 LED driver chips accessed via the I2C bus. Supported
184 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
187 tristate "LED Support for WM8350 AudioPlus PMIC"
188 depends on LEDS_CLASS && MFD_WM8350
190 This option enables support for LEDs driven by the Wolfson
191 Microelectronics WM8350 AudioPlus PMIC.
194 tristate "LED Support for DA9030/DA9034 PMIC"
195 depends on LEDS_CLASS && PMIC_DA903X
197 This option enables support for on-chip LED drivers found
198 on Dialog Semiconductor DA9030/DA9034 PMICs.
200 config LEDS_DAC124S085
201 tristate "LED Support for DAC124S085 SPI DAC"
202 depends on LEDS_CLASS && SPI
204 This option enables support for DAC124S085 SPI DAC from NatSemi,
205 which can be used to control up to four LEDs.
208 tristate "PWM driven LED Support"
209 depends on LEDS_CLASS && HAVE_PWM
211 This option enables support for pwm driven LEDs
214 tristate "LED driver for BD2802 RGB LED"
215 depends on LEDS_CLASS && I2C
217 This option enables support for BD2802GU RGB LED driver chips
218 accessed via the I2C bus.
220 comment "LED Triggers"
223 bool "LED Trigger support"
225 This option enables trigger support for the leds class.
226 These triggers allow kernel events to drive the LEDs and can
227 be configured via sysfs. If unsure, say Y.
229 config LEDS_TRIGGER_TIMER
230 tristate "LED Timer Trigger"
231 depends on LEDS_TRIGGERS
233 This allows LEDs to be controlled by a programmable timer
234 via sysfs. Some LED hardware can be programmed to start
235 blinking the LED without any further software interaction.
236 For more details read Documentation/leds-class.txt.
240 config LEDS_TRIGGER_IDE_DISK
241 bool "LED IDE Disk Trigger"
242 depends on LEDS_TRIGGERS && IDE_GD_ATA
244 This allows LEDs to be controlled by IDE disk activity.
247 config LEDS_TRIGGER_HEARTBEAT
248 tristate "LED Heartbeat Trigger"
249 depends on LEDS_TRIGGERS
251 This allows LEDs to be controlled by a CPU load average.
252 The flash frequency is a hyperbolic function of the 1-minute
256 config LEDS_TRIGGER_BACKLIGHT
257 tristate "LED backlight Trigger"
258 depends on LEDS_TRIGGERS
260 This allows LEDs to be controlled as a backlight device: they
261 turn off and on when the display is blanked and unblanked.
265 config LEDS_TRIGGER_GPIO
266 tristate "LED GPIO Trigger"
267 depends on LEDS_TRIGGERS
270 This allows LEDs to be controlled by gpio events. It's good
271 when using gpios as switches and triggering the needed LEDs
272 from there. One use case is n810's keypad LEDs that could
273 be triggered by this trigger when user slides up to show
278 config LEDS_TRIGGER_DEFAULT_ON
279 tristate "LED Default ON Trigger"
280 depends on LEDS_TRIGGERS
282 This allows LEDs to be initialised in the ON state.
285 comment "iptables trigger is under Netfilter config (LED target)"
286 depends on LEDS_TRIGGERS