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.
35 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
36 depends on LEDS_CLASS && ARCH_S3C2410
38 This option enables support for LEDs connected to GPIO lines
39 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
42 tristate "LED Support for the Amstrad Delta (E3)"
43 depends on LEDS_CLASS && MACH_AMS_DELTA
45 This option enables support for the LEDs on Amstrad Delta (E3).
48 tristate "LED Support for Soekris net48xx series Error LED"
49 depends on LEDS_CLASS && SCx200_GPIO
51 This option enables support for the Soekris net4801 and net4826 error
55 tristate "LED Support for the Freecom FSG-3"
56 depends on LEDS_CLASS && MACH_FSG
58 This option enables support for the LEDs on the Freecom FSG-3.
61 tristate "LED Support for the WRAP series LEDs"
62 depends on LEDS_CLASS && SCx200_GPIO
64 This option enables support for the PCEngines WRAP programmable LEDs.
67 tristate "LED Support for ALIX.2 and ALIX.3 series"
68 depends on LEDS_CLASS && X86 && EXPERIMENTAL
70 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
73 tristate "LED Support for iPAQ H1940 device"
74 depends on LEDS_CLASS && ARCH_H1940
76 This option enables support for the LEDs on the h1940.
78 config LEDS_COBALT_QUBE
79 tristate "LED Support for the Cobalt Qube series front LED"
80 depends on LEDS_CLASS && MIPS_COBALT
82 This option enables support for the front LED on Cobalt Qube series
84 config LEDS_COBALT_RAQ
85 bool "LED Support for the Cobalt Raq series"
86 depends on LEDS_CLASS=y && MIPS_COBALT
89 This option enables support for the Cobalt Raq series LEDs.
92 tristate "LED support for SunFire servers."
93 depends on LEDS_CLASS && SPARC64
96 This option enables support for the Left, Middle, and Right
97 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
100 tristate "LED Support for the HP Jornada 6xx"
101 depends on LEDS_CLASS && SH_HP6XX
103 This option enables LED support for the handheld
104 HP Jornada 620/660/680/690.
107 tristate "LED driver for PCA9532 dimmer"
108 depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
110 This option enables support for NXP pca9532
111 LED controller. It is generally only useful
115 tristate "LED Support for GPIO connected LEDs"
116 depends on LEDS_CLASS && GENERIC_GPIO
118 This option enables support for the LEDs connected to GPIO
119 outputs. To be useful the particular board must have LEDs
120 and they must be connected to the GPIO lines. The LEDs must be
121 defined as platform devices and/or OpenFirmware platform devices.
122 The code to use these bindings can be selected below.
124 config LEDS_GPIO_PLATFORM
125 bool "Platform device bindings for GPIO LEDs"
129 Let the leds-gpio driver drive LEDs which have been defined as
130 platform devices. If you don't know what this means, say yes.
133 bool "OpenFirmware platform device bindings for GPIO LEDs"
134 depends on LEDS_GPIO && OF_DEVICE
137 Let the leds-gpio driver drive LEDs which have been defined as
138 of_platform devices. For instance, LEDs which are listed in a "dts"
141 config LEDS_CLEVO_MAIL
142 tristate "Mail LED on Clevo notebook (EXPERIMENTAL)"
143 depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI && EXPERIMENTAL
145 This driver makes the mail LED accessible from userspace
146 programs through the leds subsystem. This LED have three
147 known mode: off, blink at 0.5Hz and blink at 1Hz.
149 The driver supports two kinds of interface: using ledtrig-timer
150 or through /sys/class/leds/clevo::mail/brightness. As this LED
151 cannot change it's brightness it blinks instead. The brightness
152 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
155 This module can drive the mail LED for the following notebooks:
160 Clevo D400V/D470V (not tested, but might work)
162 Clevo M5x0N (not tested, but might work)
163 Positivo Mobile (Clevo M5x0V)
165 If your model is not listed here you can try the "nodetect"
168 To compile this driver as a module, choose M here: the
169 module will be called leds-clevo-mail.
172 tristate "LED Support for PCA955x I2C chips"
173 depends on LEDS_CLASS && I2C
175 This option enables support for LEDs connected to PCA955x
176 LED driver chips accessed via the I2C bus. Supported
177 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
180 tristate "LED Support for WM8350 AudioPlus PMIC"
181 depends on LEDS_CLASS && MFD_WM8350
183 This option enables support for LEDs driven by the Wolfson
184 Microelectronics WM8350 AudioPlus PMIC.
187 tristate "LED Support for DA9030/DA9034 PMIC"
188 depends on LEDS_CLASS && PMIC_DA903X
190 This option enables support for on-chip LED drivers found
191 on Dialog Semiconductor DA9030/DA9034 PMICs.
193 config LEDS_DAC124S085
194 tristate "LED Support for DAC124S085 SPI DAC"
195 depends on LEDS_CLASS && SPI
197 This option enables support for DAC124S085 SPI DAC from NatSemi,
198 which can be used to control up to four LEDs.
200 comment "LED Triggers"
203 bool "LED Trigger support"
205 This option enables trigger support for the leds class.
206 These triggers allow kernel events to drive the LEDs and can
207 be configured via sysfs. If unsure, say Y.
209 config LEDS_TRIGGER_TIMER
210 tristate "LED Timer Trigger"
211 depends on LEDS_TRIGGERS
213 This allows LEDs to be controlled by a programmable timer
214 via sysfs. Some LED hardware can be programmed to start
215 blinking the LED without any further software interaction.
216 For more details read Documentation/leds-class.txt.
220 config LEDS_TRIGGER_IDE_DISK
221 bool "LED IDE Disk Trigger"
222 depends on LEDS_TRIGGERS && IDE_GD_ATA
224 This allows LEDs to be controlled by IDE disk activity.
227 config LEDS_TRIGGER_HEARTBEAT
228 tristate "LED Heartbeat Trigger"
229 depends on LEDS_TRIGGERS
231 This allows LEDs to be controlled by a CPU load average.
232 The flash frequency is a hyperbolic function of the 1-minute
236 config LEDS_TRIGGER_BACKLIGHT
237 tristate "LED backlight Trigger"
238 depends on LEDS_TRIGGERS
240 This allows LEDs to be controlled as a backlight device: they
241 turn off and on when the display is blanked and unblanked.
245 config LEDS_TRIGGER_DEFAULT_ON
246 tristate "LED Default ON Trigger"
247 depends on LEDS_TRIGGERS
249 This allows LEDs to be initialised in the ON state.
252 comment "iptables trigger is under Netfilter config (LED target)"
253 depends on LEDS_TRIGGERS