xref: /openbmc/linux/drivers/leds/Kconfig (revision 81d67439)
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	bool "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_LOCOMO
54	tristate "LED Support for Locomo device"
55	depends on LEDS_CLASS
56	depends on SHARP_LOCOMO
57	help
58	  This option enables support for the LEDs on Sharp Locomo.
59	  Zaurus models SL-5500 and SL-5600.
60
61config LEDS_MIKROTIK_RB532
62	tristate "LED Support for Mikrotik Routerboard 532"
63	depends on LEDS_CLASS
64	depends on MIKROTIK_RB532
65	help
66	  This option enables support for the so called "User LED" of
67	  Mikrotik's Routerboard 532.
68
69config LEDS_S3C24XX
70	tristate "LED Support for Samsung S3C24XX GPIO LEDs"
71	depends on LEDS_CLASS
72	depends on ARCH_S3C2410
73	help
74	  This option enables support for LEDs connected to GPIO lines
75	  on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
76
77config LEDS_AMS_DELTA
78	tristate "LED Support for the Amstrad Delta (E3)"
79	depends on LEDS_CLASS
80	depends on MACH_AMS_DELTA
81	help
82	  This option enables support for the LEDs on Amstrad Delta (E3).
83
84config LEDS_NET48XX
85	tristate "LED Support for Soekris net48xx series Error LED"
86	depends on LEDS_CLASS
87	depends on SCx200_GPIO
88	help
89	  This option enables support for the Soekris net4801 and net4826 error
90	  LED.
91
92config LEDS_NET5501
93	tristate "LED Support for Soekris net5501 series Error LED"
94	depends on LEDS_TRIGGERS
95	depends on X86 && GPIO_CS5535
96	select LEDS_TRIGGER_DEFAULT_ON
97	default n
98	help
99	  Add support for the Soekris net5501 board (detection, error led
100	  and GPIO).
101
102config LEDS_FSG
103	tristate "LED Support for the Freecom FSG-3"
104	depends on LEDS_CLASS
105	depends on MACH_FSG
106	help
107	  This option enables support for the LEDs on the Freecom FSG-3.
108
109config LEDS_WRAP
110	tristate "LED Support for the WRAP series LEDs"
111	depends on LEDS_CLASS
112	depends on SCx200_GPIO
113	help
114	  This option enables support for the PCEngines WRAP programmable LEDs.
115
116config LEDS_ALIX2
117	tristate "LED Support for ALIX.2 and ALIX.3 series"
118	depends on LEDS_CLASS
119	depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
120	help
121	  This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
122	  You have to set leds-alix2.force=1 for boards with Award BIOS.
123
124config LEDS_COBALT_QUBE
125	tristate "LED Support for the Cobalt Qube series front LED"
126	depends on LEDS_CLASS
127	depends on MIPS_COBALT
128	help
129	  This option enables support for the front LED on Cobalt Qube series
130
131config LEDS_COBALT_RAQ
132	bool "LED Support for the Cobalt Raq series"
133	depends on LEDS_CLASS=y && MIPS_COBALT
134	select LEDS_TRIGGERS
135	help
136	  This option enables support for the Cobalt Raq series LEDs.
137
138config LEDS_SUNFIRE
139	tristate "LED support for SunFire servers."
140	depends on LEDS_CLASS
141	depends on SPARC64
142	select LEDS_TRIGGERS
143	help
144	  This option enables support for the Left, Middle, and Right
145	  LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
146
147config LEDS_HP6XX
148	tristate "LED Support for the HP Jornada 6xx"
149	depends on LEDS_CLASS
150	depends on SH_HP6XX
151	help
152	  This option enables LED support for the handheld
153	  HP Jornada 620/660/680/690.
154
155config LEDS_PCA9532
156	tristate "LED driver for PCA9532 dimmer"
157	depends on LEDS_CLASS
158	depends on I2C && INPUT && EXPERIMENTAL
159	help
160	  This option enables support for NXP pca9532
161	  LED controller. It is generally only useful
162	  as a platform driver
163
164config LEDS_PCA9532_GPIO
165	bool "Enable GPIO support for PCA9532"
166	depends on LEDS_PCA9532
167	depends on GPIOLIB
168	help
169	  Allow unused pins on PCA9532 to be used as gpio.
170
171	  To use a pin as gpio pca9532_type in pca9532_platform data needs to
172	  set to PCA9532_TYPE_GPIO.
173
174config LEDS_GPIO
175	tristate "LED Support for GPIO connected LEDs"
176	depends on LEDS_CLASS
177	depends on GENERIC_GPIO
178	help
179	  This option enables support for the LEDs connected to GPIO
180	  outputs. To be useful the particular board must have LEDs
181	  and they must be connected to the GPIO lines.  The LEDs must be
182	  defined as platform devices and/or OpenFirmware platform devices.
183	  The code to use these bindings can be selected below.
184
185config LEDS_LP3944
186	tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
187	depends on LEDS_CLASS
188	depends on I2C
189	help
190	  This option enables support for LEDs connected to the National
191	  Semiconductor LP3944 Lighting Management Unit (LMU) also known as
192	  Fun Light Chip.
193
194	  To compile this driver as a module, choose M here: the
195	  module will be called leds-lp3944.
196
197config LEDS_LP5521
198	tristate "LED Support for N.S. LP5521 LED driver chip"
199	depends on LEDS_CLASS && I2C
200	help
201	  If you say yes here you get support for the National Semiconductor
202	  LP5521 LED driver. It is 3 channel chip with programmable engines.
203	  Driver provides direct control via LED class and interface for
204	  programming the engines.
205
206config LEDS_LP5523
207	tristate "LED Support for N.S. LP5523 LED driver chip"
208	depends on LEDS_CLASS && I2C
209	help
210	  If you say yes here you get support for the National Semiconductor
211	  LP5523 LED driver. It is 9 channel chip with programmable engines.
212	  Driver provides direct control via LED class and interface for
213	  programming the engines.
214
215config LEDS_CLEVO_MAIL
216	tristate "Mail LED on Clevo notebook"
217	depends on LEDS_CLASS
218	depends on X86 && SERIO_I8042 && DMI
219	help
220	  This driver makes the mail LED accessible from userspace
221	  programs through the leds subsystem. This LED have three
222	  known mode: off, blink at 0.5Hz and blink at 1Hz.
223
224	  The driver supports two kinds of interface: using ledtrig-timer
225	  or through /sys/class/leds/clevo::mail/brightness. As this LED
226	  cannot change it's brightness it blinks instead. The brightness
227	  value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
228	  blink at 1Hz.
229
230	  This module can drive the mail LED for the following notebooks:
231
232	  	Clevo D400P
233	  	Clevo D410J
234	  	Clevo D410V
235	  	Clevo D400V/D470V (not tested, but might work)
236	  	Clevo M540N
237	  	Clevo M5x0N (not tested, but might work)
238	  	Positivo Mobile (Clevo M5x0V)
239
240	  If your model is not listed here you can try the "nodetect"
241	  module parameter.
242
243	  To compile this driver as a module, choose M here: the
244	  module will be called leds-clevo-mail.
245
246config LEDS_PCA955X
247	tristate "LED Support for PCA955x I2C chips"
248	depends on LEDS_CLASS
249	depends on I2C
250	help
251	  This option enables support for LEDs connected to PCA955x
252	  LED driver chips accessed via the I2C bus.  Supported
253	  devices include PCA9550, PCA9551, PCA9552, and PCA9553.
254
255config LEDS_WM831X_STATUS
256	tristate "LED support for status LEDs on WM831x PMICs"
257	depends on LEDS_CLASS
258	depends on MFD_WM831X
259	help
260	  This option enables support for the status LEDs of the WM831x
261          series of PMICs.
262
263config LEDS_WM8350
264	tristate "LED Support for WM8350 AudioPlus PMIC"
265	depends on LEDS_CLASS
266	depends on MFD_WM8350
267	help
268	  This option enables support for LEDs driven by the Wolfson
269	  Microelectronics WM8350 AudioPlus PMIC.
270
271config LEDS_DA903X
272	tristate "LED Support for DA9030/DA9034 PMIC"
273	depends on LEDS_CLASS
274	depends on PMIC_DA903X
275	help
276	  This option enables support for on-chip LED drivers found
277	  on Dialog Semiconductor DA9030/DA9034 PMICs.
278
279config LEDS_DAC124S085
280	tristate "LED Support for DAC124S085 SPI DAC"
281	depends on LEDS_CLASS
282	depends on SPI
283	help
284	  This option enables support for DAC124S085 SPI DAC from NatSemi,
285	  which can be used to control up to four LEDs.
286
287config LEDS_PWM
288	tristate "PWM driven LED Support"
289	depends on LEDS_CLASS
290	depends on HAVE_PWM
291	help
292	  This option enables support for pwm driven LEDs
293
294config LEDS_REGULATOR
295	tristate "REGULATOR driven LED support"
296	depends on LEDS_CLASS
297	depends on REGULATOR
298	help
299	  This option enables support for regulator driven LEDs.
300
301config LEDS_BD2802
302	tristate "LED driver for BD2802 RGB LED"
303	depends on LEDS_CLASS
304	depends on I2C
305	help
306	  This option enables support for BD2802GU RGB LED driver chips
307	  accessed via the I2C bus.
308
309config LEDS_INTEL_SS4200
310	tristate "LED driver for Intel NAS SS4200 series"
311	depends on LEDS_CLASS
312	depends on PCI && DMI
313	help
314	  This option enables support for the Intel SS4200 series of
315	  Network Attached Storage servers.  You may control the hard
316	  drive or power LEDs on the front panel.  Using this driver
317	  can stop the front LED from blinking after startup.
318
319config LEDS_LT3593
320	tristate "LED driver for LT3593 controllers"
321	depends on LEDS_CLASS
322	depends on GENERIC_GPIO
323	help
324	  This option enables support for LEDs driven by a Linear Technology
325	  LT3593 controller. This controller uses a special one-wire pulse
326	  coding protocol to set the brightness.
327
328config LEDS_ADP5520
329	tristate "LED Support for ADP5520/ADP5501 PMIC"
330	depends on LEDS_CLASS
331	depends on PMIC_ADP5520
332	help
333	  This option enables support for on-chip LED drivers found
334	  on Analog Devices ADP5520/ADP5501 PMICs.
335
336	  To compile this driver as a module, choose M here: the module will
337	  be called leds-adp5520.
338
339config LEDS_DELL_NETBOOKS
340	tristate "External LED on Dell Business Netbooks"
341	depends on LEDS_CLASS
342	depends on X86 && ACPI_WMI
343	help
344	  This adds support for the Latitude 2100 and similar
345	  notebooks that have an external LED.
346
347config LEDS_MC13783
348	tristate "LED Support for MC13783 PMIC"
349	depends on LEDS_CLASS
350	depends on MFD_MC13783
351	help
352	  This option enable support for on-chip LED drivers found
353	  on Freescale Semiconductor MC13783 PMIC.
354
355config LEDS_NS2
356	tristate "LED support for Network Space v2 GPIO LEDs"
357	depends on LEDS_CLASS
358	depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || MACH_NETSPACE_MAX_V2 || D2NET_V2
359	default y
360	help
361	  This option enable support for the dual-GPIO LED found on the
362	  Network Space v2 board (and parents). This include Internet Space v2,
363	  Network Space (Max) v2 and d2 Network v2 boards.
364
365config LEDS_NETXBIG
366	tristate "LED support for Big Network series LEDs"
367	depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
368	default y
369	help
370	  This option enable support for LEDs found on the LaCie 2Big
371	  and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
372	  controlled through a GPIO extension bus.
373
374config LEDS_ASIC3
375	bool "LED support for the HTC ASIC3"
376	depends on LEDS_CLASS
377	depends on MFD_ASIC3
378	default y
379	help
380	  This option enables support for the LEDs on the HTC ASIC3. The HTC
381	  ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
382	  cannot be used. This driver supports hardware blinking with an on+off
383	  period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
384
385config LEDS_TRIGGERS
386	bool "LED Trigger support"
387	depends on LEDS_CLASS
388	help
389	  This option enables trigger support for the leds class.
390	  These triggers allow kernel events to drive the LEDs and can
391	  be configured via sysfs. If unsure, say Y.
392
393comment "LED Triggers"
394
395config LEDS_TRIGGER_TIMER
396	tristate "LED Timer Trigger"
397	depends on LEDS_TRIGGERS
398	help
399	  This allows LEDs to be controlled by a programmable timer
400	  via sysfs. Some LED hardware can be programmed to start
401	  blinking the LED without any further software interaction.
402	  For more details read Documentation/leds-class.txt.
403
404	  If unsure, say Y.
405
406config LEDS_TRIGGER_IDE_DISK
407	bool "LED IDE Disk Trigger"
408	depends on IDE_GD_ATA
409	depends on LEDS_TRIGGERS
410	help
411	  This allows LEDs to be controlled by IDE disk activity.
412	  If unsure, say Y.
413
414config LEDS_TRIGGER_HEARTBEAT
415	tristate "LED Heartbeat Trigger"
416	depends on LEDS_TRIGGERS
417	help
418	  This allows LEDs to be controlled by a CPU load average.
419	  The flash frequency is a hyperbolic function of the 1-minute
420	  load average.
421	  If unsure, say Y.
422
423config LEDS_TRIGGER_BACKLIGHT
424	tristate "LED backlight Trigger"
425	depends on LEDS_TRIGGERS
426	help
427	  This allows LEDs to be controlled as a backlight device: they
428	  turn off and on when the display is blanked and unblanked.
429
430	  If unsure, say N.
431
432config LEDS_TRIGGER_GPIO
433	tristate "LED GPIO Trigger"
434	depends on LEDS_TRIGGERS
435	depends on GPIOLIB
436	help
437	  This allows LEDs to be controlled by gpio events. It's good
438	  when using gpios as switches and triggering the needed LEDs
439	  from there. One use case is n810's keypad LEDs that could
440	  be triggered by this trigger when user slides up to show
441	  keypad.
442
443	  If unsure, say N.
444
445config LEDS_TRIGGER_DEFAULT_ON
446	tristate "LED Default ON Trigger"
447	depends on LEDS_TRIGGERS
448	help
449	  This allows LEDs to be initialised in the ON state.
450	  If unsure, say Y.
451
452comment "iptables trigger is under Netfilter config (LED target)"
453	depends on LEDS_TRIGGERS
454
455endif # NEW_LEDS
456