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