Commit | Line | Data |
---|---|---|
be5ce2f1 UKK |
1 | config LEDS_GPIO_REGISTER |
2 | bool | |
3 | help | |
4 | This option provides the function gpio_led_register_device. | |
5 | As this function is used by arch code it must not be compiled as a | |
6 | module. | |
7 | ||
66242f7e | 8 | menuconfig NEW_LEDS |
c72a1d60 RP |
9 | bool "LED Support" |
10 | help | |
a8d2e7d9 RP |
11 | Say Y to enable Linux LED support. This allows control of supported |
12 | LEDs from both userspace and optionally, by kernel events (triggers). | |
13 | ||
14 | This is not related to standard keyboard LEDs which are controlled | |
15 | via the input system. | |
c72a1d60 | 16 | |
45d16f09 EM |
17 | if NEW_LEDS |
18 | ||
c72a1d60 | 19 | config LEDS_CLASS |
a403d930 | 20 | tristate "LED Class Support" |
c72a1d60 RP |
21 | help |
22 | This option enables the led sysfs class in /sys/class/leds. You'll | |
23 | need this to do anything useful with LEDs. If unsure, say N. | |
24 | ||
24f51e81 | 25 | comment "LED drivers" |
c3bc9956 | 26 | |
0a2f915b HZ |
27 | config LEDS_88PM860X |
28 | tristate "LED Support for Marvell 88PM860x PMIC" | |
0bae35e1 | 29 | depends on LEDS_CLASS |
37814fdc | 30 | depends on MFD_88PM860X |
0a2f915b HZ |
31 | help |
32 | This option enables support for on-chip LED drivers found on Marvell | |
33 | Semiconductor 88PM8606 PMIC. | |
34 | ||
b1e6b706 SKS |
35 | config LEDS_LM3530 |
36 | tristate "LCD Backlight driver for LM3530" | |
37 | depends on LEDS_CLASS | |
38 | depends on I2C | |
39 | help | |
40 | This option enables support for the LCD backlight using | |
41 | LM3530 ambient light sensor chip. This ALS chip can be | |
42 | controlled manually or using PWM input or using ambient | |
43 | light automatically. | |
44 | ||
401dea7f JH |
45 | config LEDS_LM3533 |
46 | tristate "LED support for LM3533" | |
47 | depends on LEDS_CLASS | |
48 | depends on MFD_LM3533 | |
49 | help | |
50 | This option enables support for the LEDs on National Semiconductor / | |
51 | TI LM3533 Lighting Power chips. | |
52 | ||
53 | The LEDs can be controlled directly, through PWM input, or by the | |
54 | ambient-light-sensor interface. The chip supports | |
55 | hardware-accelerated blinking with maximum on and off periods of 9.8 | |
56 | and 77 seconds respectively. | |
57 | ||
8b7cfbec SJ |
58 | config LEDS_LM3642 |
59 | tristate "LED support for LM3642 Chip" | |
60 | depends on LEDS_CLASS && I2C | |
61 | select REGMAP_I2C | |
62 | help | |
63 | This option enables support for LEDs connected to LM3642. | |
64 | The LM3642 is a 4MHz fixed-frequency synchronous boost | |
65 | converter plus 1.5A constant current driver for a high-current | |
66 | white LED. | |
67 | ||
68 | ||
4d3cb354 RP |
69 | config LEDS_LOCOMO |
70 | tristate "LED Support for Locomo device" | |
0bae35e1 | 71 | depends on LEDS_CLASS |
d09e1666 | 72 | depends on SHARP_LOCOMO |
4d3cb354 RP |
73 | help |
74 | This option enables support for the LEDs on Sharp Locomo. | |
75 | Zaurus models SL-5500 and SL-5600. | |
76 | ||
ac67e23b PS |
77 | config LEDS_MIKROTIK_RB532 |
78 | tristate "LED Support for Mikrotik Routerboard 532" | |
0bae35e1 | 79 | depends on LEDS_CLASS |
d09e1666 | 80 | depends on MIKROTIK_RB532 |
ac67e23b PS |
81 | help |
82 | This option enables support for the so called "User LED" of | |
83 | Mikrotik's Routerboard 532. | |
84 | ||
54bdc470 BD |
85 | config LEDS_S3C24XX |
86 | tristate "LED Support for Samsung S3C24XX GPIO LEDs" | |
0bae35e1 | 87 | depends on LEDS_CLASS |
b130d5c2 | 88 | depends on ARCH_S3C24XX |
54bdc470 BD |
89 | help |
90 | This option enables support for LEDs connected to GPIO lines | |
91 | on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440. | |
92 | ||
1a87d942 CB |
93 | config LEDS_NET48XX |
94 | tristate "LED Support for Soekris net48xx series Error LED" | |
0bae35e1 | 95 | depends on LEDS_CLASS |
d09e1666 | 96 | depends on SCx200_GPIO |
1a87d942 CB |
97 | help |
98 | This option enables support for the Soekris net4801 and net4826 error | |
99 | LED. | |
100 | ||
3b2e46f8 RW |
101 | config LEDS_FSG |
102 | tristate "LED Support for the Freecom FSG-3" | |
0bae35e1 | 103 | depends on LEDS_CLASS |
d09e1666 | 104 | depends on MACH_FSG |
3b2e46f8 RW |
105 | help |
106 | This option enables support for the LEDs on the Freecom FSG-3. | |
107 | ||
0d75565f KK |
108 | config LEDS_WRAP |
109 | tristate "LED Support for the WRAP series LEDs" | |
0bae35e1 | 110 | depends on LEDS_CLASS |
d09e1666 | 111 | depends on SCx200_GPIO |
0d75565f KK |
112 | help |
113 | This option enables support for the PCEngines WRAP programmable LEDs. | |
114 | ||
f3b6b6cd YY |
115 | config LEDS_COBALT_QUBE |
116 | tristate "LED Support for the Cobalt Qube series front LED" | |
0bae35e1 | 117 | depends on LEDS_CLASS |
d09e1666 | 118 | depends on MIPS_COBALT |
2fea6f35 | 119 | help |
f3b6b6cd | 120 | This option enables support for the front LED on Cobalt Qube series |
2fea6f35 | 121 | |
97da7aaf YY |
122 | config LEDS_COBALT_RAQ |
123 | bool "LED Support for the Cobalt Raq series" | |
ec149619 | 124 | depends on LEDS_CLASS=y && MIPS_COBALT |
97da7aaf YY |
125 | select LEDS_TRIGGERS |
126 | help | |
127 | This option enables support for the Cobalt Raq series LEDs. | |
128 | ||
5843492c DM |
129 | config LEDS_SUNFIRE |
130 | tristate "LED support for SunFire servers." | |
0bae35e1 | 131 | depends on LEDS_CLASS |
d09e1666 | 132 | depends on SPARC64 |
5843492c DM |
133 | select LEDS_TRIGGERS |
134 | help | |
135 | This option enables support for the Left, Middle, and Right | |
136 | LEDs on the I/O and CPU boards of SunFire UltraSPARC servers. | |
137 | ||
4da498fc LW |
138 | config LEDS_IPAQ_MICRO |
139 | tristate "LED Support for the Compaq iPAQ h3xxx" | |
140 | depends on MFD_IPAQ_MICRO | |
141 | help | |
142 | Choose this option if you want to use the notification LED on | |
143 | Compaq/HP iPAQ h3100 and h3600. | |
144 | ||
d39a7a63 KE |
145 | config LEDS_HP6XX |
146 | tristate "LED Support for the HP Jornada 6xx" | |
0bae35e1 | 147 | depends on LEDS_CLASS |
d09e1666 | 148 | depends on SH_HP6XX |
d39a7a63 | 149 | help |
692105b8 | 150 | This option enables LED support for the handheld |
d39a7a63 KE |
151 | HP Jornada 620/660/680/690. |
152 | ||
e14fa824 RV |
153 | config LEDS_PCA9532 |
154 | tristate "LED driver for PCA9532 dimmer" | |
0bae35e1 | 155 | depends on LEDS_CLASS |
5e0b080d | 156 | depends on I2C && INPUT |
e14fa824 RV |
157 | help |
158 | This option enables support for NXP pca9532 | |
692105b8 | 159 | LED controller. It is generally only useful |
e14fa824 RV |
160 | as a platform driver |
161 | ||
3c1ab50d JE |
162 | config LEDS_PCA9532_GPIO |
163 | bool "Enable GPIO support for PCA9532" | |
164 | depends on LEDS_PCA9532 | |
165 | depends on GPIOLIB | |
166 | help | |
167 | Allow unused pins on PCA9532 to be used as gpio. | |
168 | ||
169 | To use a pin as gpio pca9532_type in pca9532_platform data needs to | |
170 | set to PCA9532_TYPE_GPIO. | |
171 | ||
22e03f3b RA |
172 | config LEDS_GPIO |
173 | tristate "LED Support for GPIO connected LEDs" | |
0bae35e1 | 174 | depends on LEDS_CLASS |
76ec9d18 | 175 | depends on GPIOLIB |
22e03f3b RA |
176 | help |
177 | This option enables support for the LEDs connected to GPIO | |
178 | outputs. To be useful the particular board must have LEDs | |
a7d878af TP |
179 | and they must be connected to the GPIO lines. The LEDs must be |
180 | defined as platform devices and/or OpenFirmware platform devices. | |
181 | The code to use these bindings can be selected below. | |
182 | ||
5054d39e AO |
183 | config LEDS_LP3944 |
184 | tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip" | |
0bae35e1 | 185 | depends on LEDS_CLASS |
d09e1666 | 186 | depends on I2C |
5054d39e | 187 | help |
7f1be819 AO |
188 | This option enables support for LEDs connected to the National |
189 | Semiconductor LP3944 Lighting Management Unit (LMU) also known as | |
190 | Fun Light Chip. | |
5054d39e AO |
191 | |
192 | To compile this driver as a module, choose M here: the | |
193 | module will be called leds-lp3944. | |
194 | ||
c93d08fa | 195 | config LEDS_LP55XX_COMMON |
33b3a561 KM |
196 | tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" |
197 | depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501 | |
10c06d17 | 198 | select FW_LOADER |
c93d08fa | 199 | help |
33b3a561 | 200 | This option supports common operations for LP5521/5523/55231/5562/8501 |
c93d08fa MWK |
201 | devices. |
202 | ||
f4920f67 SO |
203 | config LEDS_LP5521 |
204 | tristate "LED Support for N.S. LP5521 LED driver chip" | |
205 | depends on LEDS_CLASS && I2C | |
c93d08fa | 206 | select LEDS_LP55XX_COMMON |
f4920f67 SO |
207 | help |
208 | If you say yes here you get support for the National Semiconductor | |
209 | LP5521 LED driver. It is 3 channel chip with programmable engines. | |
210 | Driver provides direct control via LED class and interface for | |
211 | programming the engines. | |
212 | ||
213 | config LEDS_LP5523 | |
ca705321 | 214 | tristate "LED Support for TI/National LP5523/55231 LED driver chip" |
f4920f67 | 215 | depends on LEDS_CLASS && I2C |
c93d08fa | 216 | select LEDS_LP55XX_COMMON |
f4920f67 | 217 | help |
ca705321 KM |
218 | If you say yes here you get support for TI/National Semiconductor |
219 | LP5523/55231 LED driver. | |
220 | It is 9 channel chip with programmable engines. | |
f4920f67 SO |
221 | Driver provides direct control via LED class and interface for |
222 | programming the engines. | |
223 | ||
ff45262a KM |
224 | config LEDS_LP5562 |
225 | tristate "LED Support for TI LP5562 LED driver chip" | |
226 | depends on LEDS_CLASS && I2C | |
227 | select LEDS_LP55XX_COMMON | |
228 | help | |
229 | If you say yes here you get support for TI LP5562 LED driver. | |
230 | It is 4 channels chip with programmable engines. | |
231 | Driver provides direct control via LED class and interface for | |
232 | programming the engines. | |
233 | ||
33b3a561 KM |
234 | config LEDS_LP8501 |
235 | tristate "LED Support for TI LP8501 LED driver chip" | |
236 | depends on LEDS_CLASS && I2C | |
237 | select LEDS_LP55XX_COMMON | |
238 | help | |
239 | If you say yes here you get support for TI LP8501 LED driver. | |
240 | It is 9 channel chip with programmable engines. | |
241 | Driver provides direct control via LED class and interface for | |
242 | programming the engines. | |
243 | It is similar as LP5523, but output power selection is available. | |
244 | And register layout and engine program schemes are different. | |
245 | ||
eb80411b KM |
246 | config LEDS_LP8788 |
247 | tristate "LED support for the TI LP8788 PMIC" | |
248 | depends on LEDS_CLASS | |
249 | depends on MFD_LP8788 | |
250 | help | |
251 | This option enables support for the Keyboard LEDs on the LP8788 PMIC. | |
252 | ||
7a8685ac DM |
253 | config LEDS_LP8860 |
254 | tristate "LED support for the TI LP8860 4 channel LED driver" | |
2969bb18 AL |
255 | depends on LEDS_CLASS && I2C |
256 | select REGMAP_I2C | |
7a8685ac DM |
257 | help |
258 | If you say yes here you get support for the TI LP8860 4 channel | |
259 | LED driver. | |
260 | This option enables support for the display cluster LEDs | |
261 | on the LP8860 4 channel LED driver using the I2C communication | |
262 | bus. | |
263 | ||
cec035de | 264 | config LEDS_CLEVO_MAIL |
95dc5768 | 265 | tristate "Mail LED on Clevo notebook" |
0bae35e1 | 266 | depends on LEDS_CLASS |
d09e1666 | 267 | depends on X86 && SERIO_I8042 && DMI |
cec035de MN |
268 | help |
269 | This driver makes the mail LED accessible from userspace | |
270 | programs through the leds subsystem. This LED have three | |
271 | known mode: off, blink at 0.5Hz and blink at 1Hz. | |
272 | ||
92e015cb MN |
273 | The driver supports two kinds of interface: using ledtrig-timer |
274 | or through /sys/class/leds/clevo::mail/brightness. As this LED | |
275 | cannot change it's brightness it blinks instead. The brightness | |
276 | value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means | |
277 | blink at 1Hz. | |
cec035de MN |
278 | |
279 | This module can drive the mail LED for the following notebooks: | |
280 | ||
b3ba31f8 | 281 | Clevo D400P |
cec035de MN |
282 | Clevo D410J |
283 | Clevo D410V | |
284 | Clevo D400V/D470V (not tested, but might work) | |
285 | Clevo M540N | |
286 | Clevo M5x0N (not tested, but might work) | |
287 | Positivo Mobile (Clevo M5x0V) | |
288 | ||
b3ba31f8 | 289 | If your model is not listed here you can try the "nodetect" |
692105b8 | 290 | module parameter. |
b3ba31f8 | 291 | |
cec035de MN |
292 | To compile this driver as a module, choose M here: the |
293 | module will be called leds-clevo-mail. | |
294 | ||
f46e9203 NC |
295 | config LEDS_PCA955X |
296 | tristate "LED Support for PCA955x I2C chips" | |
0bae35e1 | 297 | depends on LEDS_CLASS |
d09e1666 | 298 | depends on I2C |
f46e9203 NC |
299 | help |
300 | This option enables support for LEDs connected to PCA955x | |
301 | LED driver chips accessed via the I2C bus. Supported | |
302 | devices include PCA9550, PCA9551, PCA9552, and PCA9553. | |
303 | ||
56a1740c | 304 | config LEDS_PCA963X |
af67384f | 305 | tristate "LED support for PCA963x I2C chip" |
75cb2e1d PM |
306 | depends on LEDS_CLASS |
307 | depends on I2C | |
308 | help | |
af67384f RRD |
309 | This option enables support for LEDs connected to the PCA963x |
310 | LED driver chip accessed via the I2C bus. Supported | |
311 | devices include PCA9633 and PCA9634 | |
75cb2e1d | 312 | |
c746b551 MB |
313 | config LEDS_WM831X_STATUS |
314 | tristate "LED support for status LEDs on WM831x PMICs" | |
0bae35e1 | 315 | depends on LEDS_CLASS |
d09e1666 | 316 | depends on MFD_WM831X |
c746b551 MB |
317 | help |
318 | This option enables support for the status LEDs of the WM831x | |
319 | series of PMICs. | |
320 | ||
0081e802 MB |
321 | config LEDS_WM8350 |
322 | tristate "LED Support for WM8350 AudioPlus PMIC" | |
0bae35e1 | 323 | depends on LEDS_CLASS |
d09e1666 | 324 | depends on MFD_WM8350 |
0081e802 MB |
325 | help |
326 | This option enables support for LEDs driven by the Wolfson | |
327 | Microelectronics WM8350 AudioPlus PMIC. | |
328 | ||
9e84561c MR |
329 | config LEDS_DA903X |
330 | tristate "LED Support for DA9030/DA9034 PMIC" | |
0bae35e1 | 331 | depends on LEDS_CLASS |
d09e1666 | 332 | depends on PMIC_DA903X |
9e84561c MR |
333 | help |
334 | This option enables support for on-chip LED drivers found | |
335 | on Dialog Semiconductor DA9030/DA9034 PMICs. | |
336 | ||
5ba73631 DDC |
337 | config LEDS_DA9052 |
338 | tristate "Dialog DA9052/DA9053 LEDS" | |
339 | depends on LEDS_CLASS | |
340 | depends on PMIC_DA9052 | |
341 | help | |
342 | This option enables support for on-chip LED drivers found | |
343 | on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs. | |
344 | ||
ac2dd0f1 GL |
345 | config LEDS_DAC124S085 |
346 | tristate "LED Support for DAC124S085 SPI DAC" | |
0bae35e1 | 347 | depends on LEDS_CLASS |
d09e1666 | 348 | depends on SPI |
ac2dd0f1 GL |
349 | help |
350 | This option enables support for DAC124S085 SPI DAC from NatSemi, | |
351 | which can be used to control up to four LEDs. | |
352 | ||
41c42ff5 LF |
353 | config LEDS_PWM |
354 | tristate "PWM driven LED Support" | |
0bae35e1 | 355 | depends on LEDS_CLASS |
ad0ba85f | 356 | depends on PWM |
41c42ff5 LF |
357 | help |
358 | This option enables support for pwm driven LEDs | |
359 | ||
d4cc6a2e AO |
360 | config LEDS_REGULATOR |
361 | tristate "REGULATOR driven LED support" | |
0bae35e1 | 362 | depends on LEDS_CLASS |
d09e1666 | 363 | depends on REGULATOR |
d4cc6a2e AO |
364 | help |
365 | This option enables support for regulator driven LEDs. | |
366 | ||
0b56129b KK |
367 | config LEDS_BD2802 |
368 | tristate "LED driver for BD2802 RGB LED" | |
0bae35e1 | 369 | depends on LEDS_CLASS |
d09e1666 | 370 | depends on I2C |
0b56129b KK |
371 | help |
372 | This option enables support for BD2802GU RGB LED driver chips | |
373 | accessed via the I2C bus. | |
374 | ||
a328e95b DH |
375 | config LEDS_INTEL_SS4200 |
376 | tristate "LED driver for Intel NAS SS4200 series" | |
0bae35e1 | 377 | depends on LEDS_CLASS |
d09e1666 | 378 | depends on PCI && DMI |
a328e95b DH |
379 | help |
380 | This option enables support for the Intel SS4200 series of | |
381 | Network Attached Storage servers. You may control the hard | |
382 | drive or power LEDs on the front panel. Using this driver | |
383 | can stop the front LED from blinking after startup. | |
384 | ||
a8dd18fe DM |
385 | config LEDS_LT3593 |
386 | tristate "LED driver for LT3593 controllers" | |
0bae35e1 | 387 | depends on LEDS_CLASS |
76ec9d18 | 388 | depends on GPIOLIB |
a8dd18fe DM |
389 | help |
390 | This option enables support for LEDs driven by a Linear Technology | |
391 | LT3593 controller. This controller uses a special one-wire pulse | |
392 | coding protocol to set the brightness. | |
393 | ||
ed4a10b4 MH |
394 | config LEDS_ADP5520 |
395 | tristate "LED Support for ADP5520/ADP5501 PMIC" | |
0bae35e1 | 396 | depends on LEDS_CLASS |
d09e1666 | 397 | depends on PMIC_ADP5520 |
ed4a10b4 MH |
398 | help |
399 | This option enables support for on-chip LED drivers found | |
400 | on Analog Devices ADP5520/ADP5501 PMICs. | |
401 | ||
402 | To compile this driver as a module, choose M here: the module will | |
403 | be called leds-adp5520. | |
404 | ||
72dcd8d0 BR |
405 | config LEDS_DELL_NETBOOKS |
406 | tristate "External LED on Dell Business Netbooks" | |
0bae35e1 | 407 | depends on LEDS_CLASS |
72dcd8d0 BR |
408 | depends on X86 && ACPI_WMI |
409 | help | |
410 | This adds support for the Latitude 2100 and similar | |
411 | notebooks that have an external LED. | |
412 | ||
7fdcef8a | 413 | config LEDS_MC13783 |
ae6cdb03 | 414 | tristate "LED Support for MC13XXX PMIC" |
0bae35e1 | 415 | depends on LEDS_CLASS |
ae6cdb03 | 416 | depends on MFD_MC13XXX |
7fdcef8a PR |
417 | help |
418 | This option enable support for on-chip LED drivers found | |
a59ce658 | 419 | on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC. |
7fdcef8a | 420 | |
11efe71f SG |
421 | config LEDS_NS2 |
422 | tristate "LED support for Network Space v2 GPIO LEDs" | |
0bae35e1 | 423 | depends on LEDS_CLASS |
1093d8ca | 424 | depends on MACH_KIRKWOOD |
11efe71f SG |
425 | default y |
426 | help | |
427 | This option enable support for the dual-GPIO LED found on the | |
428 | Network Space v2 board (and parents). This include Internet Space v2, | |
429 | Network Space (Max) v2 and d2 Network v2 boards. | |
430 | ||
24467832 SG |
431 | config LEDS_NETXBIG |
432 | tristate "LED support for Big Network series LEDs" | |
2504f6da | 433 | depends on LEDS_CLASS |
1093d8ca | 434 | depends on MACH_KIRKWOOD |
24467832 SG |
435 | default y |
436 | help | |
437 | This option enable support for LEDs found on the LaCie 2Big | |
438 | and 5Big Network v2 boards. The LEDs are wired to a CPLD and are | |
439 | controlled through a GPIO extension bus. | |
440 | ||
7d9e7e9f PP |
441 | config LEDS_ASIC3 |
442 | bool "LED support for the HTC ASIC3" | |
9473c4c1 | 443 | depends on LEDS_CLASS=y |
7d9e7e9f PP |
444 | depends on MFD_ASIC3 |
445 | default y | |
446 | help | |
447 | This option enables support for the LEDs on the HTC ASIC3. The HTC | |
448 | ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver | |
449 | cannot be used. This driver supports hardware blinking with an on+off | |
450 | period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700. | |
451 | ||
a6d511e5 N |
452 | config LEDS_TCA6507 |
453 | tristate "LED Support for TCA6507 I2C chip" | |
454 | depends on LEDS_CLASS && I2C | |
455 | help | |
456 | This option enables support for LEDs connected to TC6507 | |
457 | LED driver chips accessed via the I2C bus. | |
458 | Driver support brightness control and hardware-assisted blinking. | |
459 | ||
8584cb82 DK |
460 | config LEDS_MAX8997 |
461 | tristate "LED support for MAX8997 PMIC" | |
462 | depends on LEDS_CLASS && MFD_MAX8997 | |
463 | help | |
464 | This option enables support for on-chip LED drivers on | |
465 | MAXIM MAX8997 PMIC. | |
466 | ||
b98d13c7 SJ |
467 | config LEDS_LM355x |
468 | tristate "LED support for LM355x Chips, LM3554 and LM3556" | |
32abb478 SJ |
469 | depends on LEDS_CLASS && I2C |
470 | select REGMAP_I2C | |
471 | help | |
b98d13c7 SJ |
472 | This option enables support for LEDs connected to LM355x. |
473 | LM355x includes Torch, Flash and Indicator functions. | |
32abb478 | 474 | |
e9a4593c SAS |
475 | config LEDS_OT200 |
476 | tristate "LED support for the Bachmann OT200" | |
d9e8928f | 477 | depends on LEDS_CLASS && HAS_IOMEM && (X86_32 || COMPILE_TEST) |
e9a4593c SAS |
478 | help |
479 | This option enables support for the LEDs on the Bachmann OT200. | |
480 | Say Y to enable LEDs on the Bachmann OT200. | |
481 | ||
38433639 AW |
482 | config LEDS_MENF21BMC |
483 | tristate "LED support for the MEN 14F021P00 BMC" | |
484 | depends on LEDS_CLASS && MFD_MENF21BMC | |
485 | help | |
486 | Say Y here to include support for the MEN 14F021P00 BMC LEDs. | |
487 | ||
488 | This driver can also be built as a module. If so the module | |
489 | will be called leds-menf21bmc. | |
490 | ||
f70ed8a6 VD |
491 | comment "LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)" |
492 | ||
b54cf35a JSM |
493 | config LEDS_BLINKM |
494 | tristate "LED support for the BlinkM I2C RGB LED" | |
495 | depends on LEDS_CLASS | |
496 | depends on I2C | |
497 | help | |
498 | This option enables support for the BlinkM RGB LED connected | |
499 | through I2C. Say Y to enable support for the BlinkM LED. | |
500 | ||
535f09cc LW |
501 | config LEDS_SYSCON |
502 | bool "LED support for LEDs on system controllers" | |
503 | depends on LEDS_CLASS=y | |
504 | depends on MFD_SYSCON | |
505 | depends on OF | |
506 | help | |
507 | This option enabled support for the LEDs on syscon type | |
508 | devices. This will only work with device tree enabled | |
509 | devices. | |
510 | ||
1dc7d837 | 511 | config LEDS_VERSATILE |
a501fd37 | 512 | tristate "LED support for the ARM Versatile and RealView" |
1dc7d837 LW |
513 | depends on ARCH_REALVIEW || ARCH_VERSATILE |
514 | depends on LEDS_CLASS | |
515 | help | |
516 | This option enabled support for the LEDs on the ARM Versatile | |
517 | and RealView boards. Say Y to enabled these. | |
518 | ||
d09e1666 | 519 | comment "LED Triggers" |
f07fb521 | 520 | source "drivers/leds/trigger/Kconfig" |
44e1e9f8 | 521 | |
66242f7e | 522 | endif # NEW_LEDS |