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