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.
78 You have to set leds-alix2.force=1 for boards with Award BIOS.
81 tristate "LED Support for iPAQ H1940 device"
82 depends on LEDS_CLASS && ARCH_H1940
84 This option enables support for the LEDs on the h1940.
86 config LEDS_COBALT_QUBE
87 tristate "LED Support for the Cobalt Qube series front LED"
88 depends on LEDS_CLASS && MIPS_COBALT
90 This option enables support for the front LED on Cobalt Qube series
92 config LEDS_COBALT_RAQ
93 bool "LED Support for the Cobalt Raq series"
94 depends on LEDS_CLASS=y && MIPS_COBALT
97 This option enables support for the Cobalt Raq series LEDs.
100 tristate "LED support for SunFire servers."
101 depends on LEDS_CLASS && SPARC64
104 This option enables support for the Left, Middle, and Right
105 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
108 tristate "LED Support for the HP Jornada 6xx"
109 depends on LEDS_CLASS && SH_HP6XX
111 This option enables LED support for the handheld
112 HP Jornada 620/660/680/690.
115 tristate "LED driver for PCA9532 dimmer"
116 depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
118 This option enables support for NXP pca9532
119 LED controller. It is generally only useful
123 tristate "LED Support for GPIO connected LEDs"
124 depends on LEDS_CLASS && GENERIC_GPIO
126 This option enables support for the LEDs connected to GPIO
127 outputs. To be useful the particular board must have LEDs
128 and they must be connected to the GPIO lines. The LEDs must be
129 defined as platform devices and/or OpenFirmware platform devices.
130 The code to use these bindings can be selected below.
132 config LEDS_GPIO_PLATFORM
133 bool "Platform device bindings for GPIO LEDs"
137 Let the leds-gpio driver drive LEDs which have been defined as
138 platform devices. If you don't know what this means, say yes.
141 bool "OpenFirmware platform device bindings for GPIO LEDs"
142 depends on LEDS_GPIO && OF_DEVICE
145 Let the leds-gpio driver drive LEDs which have been defined as
146 of_platform devices. For instance, LEDs which are listed in a "dts"
149 config LEDS_CLEVO_MAIL
150 tristate "Mail LED on Clevo notebook"
151 depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
153 This driver makes the mail LED accessible from userspace
154 programs through the leds subsystem. This LED have three
155 known mode: off, blink at 0.5Hz and blink at 1Hz.
157 The driver supports two kinds of interface: using ledtrig-timer
158 or through /sys/class/leds/clevo::mail/brightness. As this LED
159 cannot change it's brightness it blinks instead. The brightness
160 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
163 This module can drive the mail LED for the following notebooks:
168 Clevo D400V/D470V (not tested, but might work)
170 Clevo M5x0N (not tested, but might work)
171 Positivo Mobile (Clevo M5x0V)
173 If your model is not listed here you can try the "nodetect"
176 To compile this driver as a module, choose M here: the
177 module will be called leds-clevo-mail.
180 tristate "LED Support for PCA955x I2C chips"
181 depends on LEDS_CLASS && I2C
183 This option enables support for LEDs connected to PCA955x
184 LED driver chips accessed via the I2C bus. Supported
185 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
188 tristate "LED Support for WM8350 AudioPlus PMIC"
189 depends on LEDS_CLASS && MFD_WM8350
191 This option enables support for LEDs driven by the Wolfson
192 Microelectronics WM8350 AudioPlus PMIC.
195 tristate "LED Support for DA9030/DA9034 PMIC"
196 depends on LEDS_CLASS && PMIC_DA903X
198 This option enables support for on-chip LED drivers found
199 on Dialog Semiconductor DA9030/DA9034 PMICs.
201 config LEDS_DAC124S085
202 tristate "LED Support for DAC124S085 SPI DAC"
203 depends on LEDS_CLASS && SPI
205 This option enables support for DAC124S085 SPI DAC from NatSemi,
206 which can be used to control up to four LEDs.
209 tristate "PWM driven LED Support"
210 depends on LEDS_CLASS && HAVE_PWM
212 This option enables support for pwm driven LEDs
215 tristate "LED driver for BD2802 RGB LED"
216 depends on LEDS_CLASS && I2C
218 This option enables support for BD2802GU RGB LED driver chips
219 accessed via the I2C bus.
221 comment "LED Triggers"
224 bool "LED Trigger support"
226 This option enables trigger support for the leds class.
227 These triggers allow kernel events to drive the LEDs and can
228 be configured via sysfs. If unsure, say Y.
230 config LEDS_TRIGGER_TIMER
231 tristate "LED Timer Trigger"
232 depends on LEDS_TRIGGERS
234 This allows LEDs to be controlled by a programmable timer
235 via sysfs. Some LED hardware can be programmed to start
236 blinking the LED without any further software interaction.
237 For more details read Documentation/leds-class.txt.
241 config LEDS_TRIGGER_IDE_DISK
242 bool "LED IDE Disk Trigger"
243 depends on LEDS_TRIGGERS && IDE_GD_ATA
245 This allows LEDs to be controlled by IDE disk activity.
248 config LEDS_TRIGGER_HEARTBEAT
249 tristate "LED Heartbeat Trigger"
250 depends on LEDS_TRIGGERS
252 This allows LEDs to be controlled by a CPU load average.
253 The flash frequency is a hyperbolic function of the 1-minute
257 config LEDS_TRIGGER_BACKLIGHT
258 tristate "LED backlight Trigger"
259 depends on LEDS_TRIGGERS
261 This allows LEDs to be controlled as a backlight device: they
262 turn off and on when the display is blanked and unblanked.
266 config LEDS_TRIGGER_GPIO
267 tristate "LED GPIO Trigger"
268 depends on LEDS_TRIGGERS
271 This allows LEDs to be controlled by gpio events. It's good
272 when using gpios as switches and triggering the needed LEDs
273 from there. One use case is n810's keypad LEDs that could
274 be triggered by this trigger when user slides up to show
279 config LEDS_TRIGGER_DEFAULT_ON
280 tristate "LED Default ON Trigger"
281 depends on LEDS_TRIGGERS
283 This allows LEDs to be initialised in the ON state.
286 comment "iptables trigger is under Netfilter config (LED target)"
287 depends on LEDS_TRIGGERS