xref: /openbmc/linux/drivers/leds/Kconfig (revision 8db70d3d) 
1menuconfig NEW_LEDS
2	bool "LED Support"
3	help
4	  Say Y to enable Linux LED support.  This allows control of supported
5	  LEDs from both userspace and optionally, by kernel events (triggers).
6
7	  This is not related to standard keyboard LEDs which are controlled
8	  via the input system.
9
10if NEW_LEDS
11
12config LEDS_CLASS
13	tristate "LED Class Support"
14	help
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.
17
18comment "LED drivers"
19
20config LEDS_ATMEL_PWM
21	tristate "LED Support using Atmel PWM outputs"
22	depends on LEDS_CLASS && ATMEL_PWM
23	help
24	  This option enables support for LEDs driven using outputs
25	  of the dedicated PWM controller found on newer Atmel SOCs.
26
27config LEDS_LOCOMO
28	tristate "LED Support for Locomo device"
29	depends on LEDS_CLASS && SHARP_LOCOMO
30	help
31	  This option enables support for the LEDs on Sharp Locomo.
32	  Zaurus models SL-5500 and SL-5600.
33
34config LEDS_MIKROTIK_RB532
35	tristate "LED Support for Mikrotik Routerboard 532"
36	depends on LEDS_CLASS && MIKROTIK_RB532
37	help
38	  This option enables support for the so called "User LED" of
39	  Mikrotik's Routerboard 532.
40
41config LEDS_S3C24XX
42	tristate "LED Support for Samsung S3C24XX GPIO LEDs"
43	depends on LEDS_CLASS && ARCH_S3C2410
44	help
45	  This option enables support for LEDs connected to GPIO lines
46	  on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
47
48config LEDS_AMS_DELTA
49	tristate "LED Support for the Amstrad Delta (E3)"
50	depends on LEDS_CLASS && MACH_AMS_DELTA
51	help
52	  This option enables support for the LEDs on Amstrad Delta (E3).
53
54config LEDS_NET48XX
55	tristate "LED Support for Soekris net48xx series Error LED"
56	depends on LEDS_CLASS && SCx200_GPIO
57	help
58	  This option enables support for the Soekris net4801 and net4826 error
59	  LED.
60
61config LEDS_FSG
62	tristate "LED Support for the Freecom FSG-3"
63	depends on LEDS_CLASS && MACH_FSG
64	help
65	  This option enables support for the LEDs on the Freecom FSG-3.
66
67config LEDS_WRAP
68	tristate "LED Support for the WRAP series LEDs"
69	depends on LEDS_CLASS && SCx200_GPIO
70	help
71	  This option enables support for the PCEngines WRAP programmable LEDs.
72
73config LEDS_ALIX2
74	tristate "LED Support for ALIX.2 and ALIX.3 series"
75	depends on LEDS_CLASS && X86 && EXPERIMENTAL
76	help
77	  This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
78
79config LEDS_H1940
80	tristate "LED Support for iPAQ H1940 device"
81	depends on LEDS_CLASS && ARCH_H1940
82	help
83	  This option enables support for the LEDs on the h1940.
84
85config LEDS_COBALT_QUBE
86	tristate "LED Support for the Cobalt Qube series front LED"
87	depends on LEDS_CLASS && MIPS_COBALT
88	help
89	  This option enables support for the front LED on Cobalt Qube series
90
91config LEDS_COBALT_RAQ
92	bool "LED Support for the Cobalt Raq series"
93	depends on LEDS_CLASS=y && MIPS_COBALT
94	select LEDS_TRIGGERS
95	help
96	  This option enables support for the Cobalt Raq series LEDs.
97
98config LEDS_SUNFIRE
99	tristate "LED support for SunFire servers."
100	depends on LEDS_CLASS && SPARC64
101	select LEDS_TRIGGERS
102	help
103	  This option enables support for the Left, Middle, and Right
104	  LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
105
106config LEDS_HP6XX
107	tristate "LED Support for the HP Jornada 6xx"
108	depends on LEDS_CLASS && SH_HP6XX
109	help
110	  This option enables LED support for the handheld
111	  HP Jornada 620/660/680/690.
112
113config LEDS_PCA9532
114	tristate "LED driver for PCA9532 dimmer"
115	depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
116	help
117	  This option enables support for NXP pca9532
118	  LED controller. It is generally only useful
119	  as a platform driver
120
121config LEDS_GPIO
122	tristate "LED Support for GPIO connected LEDs"
123	depends on LEDS_CLASS && GENERIC_GPIO
124	help
125	  This option enables support for the LEDs connected to GPIO
126	  outputs. To be useful the particular board must have LEDs
127	  and they must be connected to the GPIO lines.  The LEDs must be
128	  defined as platform devices and/or OpenFirmware platform devices.
129	  The code to use these bindings can be selected below.
130
131config LEDS_GPIO_PLATFORM
132	bool "Platform device bindings for GPIO LEDs"
133	depends on LEDS_GPIO
134	default y
135	help
136	  Let the leds-gpio driver drive LEDs which have been defined as
137	  platform devices.  If you don't know what this means, say yes.
138
139config LEDS_GPIO_OF
140	bool "OpenFirmware platform device bindings for GPIO LEDs"
141	depends on LEDS_GPIO && OF_DEVICE
142	default y
143	help
144	  Let the leds-gpio driver drive LEDs which have been defined as
145	  of_platform devices.  For instance, LEDs which are listed in a "dts"
146	  file.
147
148config LEDS_LP5521
149	tristate "LED Support for the LP5521 LEDs"
150	depends on LEDS_CLASS && I2C
151	help
152	  If you say 'Y' here you get support for the National Semiconductor
153	  LP5521 LED driver used in n8x0 boards.
154
155	  This driver can be built as a module by choosing 'M'. The module
156	  will be called leds-lp5521.
157
158config LEDS_CLEVO_MAIL
159	tristate "Mail LED on Clevo notebook"
160	depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
161	help
162	  This driver makes the mail LED accessible from userspace
163	  programs through the leds subsystem. This LED have three
164	  known mode: off, blink at 0.5Hz and blink at 1Hz.
165
166	  The driver supports two kinds of interface: using ledtrig-timer
167	  or through /sys/class/leds/clevo::mail/brightness. As this LED
168	  cannot change it's brightness it blinks instead. The brightness
169	  value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
170	  blink at 1Hz.
171
172	  This module can drive the mail LED for the following notebooks:
173
174	  	Clevo D400P
175	  	Clevo D410J
176	  	Clevo D410V
177	  	Clevo D400V/D470V (not tested, but might work)
178	  	Clevo M540N
179	  	Clevo M5x0N (not tested, but might work)
180	  	Positivo Mobile (Clevo M5x0V)
181
182	  If your model is not listed here you can try the "nodetect"
183	  module parameter.
184
185	  To compile this driver as a module, choose M here: the
186	  module will be called leds-clevo-mail.
187
188config LEDS_PCA955X
189	tristate "LED Support for PCA955x I2C chips"
190	depends on LEDS_CLASS && I2C
191	help
192	  This option enables support for LEDs connected to PCA955x
193	  LED driver chips accessed via the I2C bus.  Supported
194	  devices include PCA9550, PCA9551, PCA9552, and PCA9553.
195
196config LEDS_WM8350
197	tristate "LED Support for WM8350 AudioPlus PMIC"
198	depends on LEDS_CLASS && MFD_WM8350
199	help
200	  This option enables support for LEDs driven by the Wolfson
201	  Microelectronics WM8350 AudioPlus PMIC.
202
203config LEDS_DA903X
204	tristate "LED Support for DA9030/DA9034 PMIC"
205	depends on LEDS_CLASS && PMIC_DA903X
206	help
207	  This option enables support for on-chip LED drivers found
208	  on Dialog Semiconductor DA9030/DA9034 PMICs.
209
210config LEDS_DAC124S085
211	tristate "LED Support for DAC124S085 SPI DAC"
212	depends on LEDS_CLASS && SPI
213	help
214	  This option enables support for DAC124S085 SPI DAC from NatSemi,
215	  which can be used to control up to four LEDs.
216
217config LEDS_PWM
218	tristate "PWM driven LED Support"
219	depends on LEDS_CLASS && HAVE_PWM
220	help
221	  This option enables support for pwm driven LEDs
222
223config LEDS_BD2802
224	tristate "LED driver for BD2802 RGB LED"
225	depends on LEDS_CLASS && I2C
226	help
227	  This option enables support for BD2802GU RGB LED driver chips
228	  accessed via the I2C bus.
229
230comment "LED Triggers"
231
232config LEDS_TRIGGERS
233	bool "LED Trigger support"
234	help
235	  This option enables trigger support for the leds class.
236	  These triggers allow kernel events to drive the LEDs and can
237	  be configured via sysfs. If unsure, say Y.
238
239config LEDS_TRIGGER_TIMER
240	tristate "LED Timer Trigger"
241	depends on LEDS_TRIGGERS
242	help
243	  This allows LEDs to be controlled by a programmable timer
244	  via sysfs. Some LED hardware can be programmed to start
245	  blinking the LED without any further software interaction.
246	  For more details read Documentation/leds-class.txt.
247
248	  If unsure, say Y.
249
250config LEDS_TRIGGER_IDE_DISK
251	bool "LED IDE Disk Trigger"
252	depends on LEDS_TRIGGERS && IDE_GD_ATA
253	help
254	  This allows LEDs to be controlled by IDE disk activity.
255	  If unsure, say Y.
256
257config LEDS_TRIGGER_HEARTBEAT
258	tristate "LED Heartbeat Trigger"
259	depends on LEDS_TRIGGERS
260	help
261	  This allows LEDs to be controlled by a CPU load average.
262	  The flash frequency is a hyperbolic function of the 1-minute
263	  load average.
264	  If unsure, say Y.
265
266config LEDS_TRIGGER_BACKLIGHT
267	tristate "LED backlight Trigger"
268	depends on LEDS_TRIGGERS
269	help
270	  This allows LEDs to be controlled as a backlight device: they
271	  turn off and on when the display is blanked and unblanked.
272
273	  If unsure, say N.
274
275config LEDS_TRIGGER_GPIO
276	tristate "LED GPIO Trigger"
277	depends on LEDS_TRIGGERS
278	depends on GPIOLIB
279	help
280	  This allows LEDs to be controlled by gpio events. It's good
281	  when using gpios as switches and triggering the needed LEDs
282	  from there. One use case is n810's keypad LEDs that could
283	  be triggered by this trigger when user slides up to show
284	  keypad.
285
286	  If unsure, say N.
287
288config LEDS_TRIGGER_DEFAULT_ON
289	tristate "LED Default ON Trigger"
290	depends on LEDS_TRIGGERS
291	help
292	  This allows LEDs to be initialised in the ON state.
293	  If unsure, say Y.
294
295comment "iptables trigger is under Netfilter config (LED target)"
296	depends on LEDS_TRIGGERS
297
298endif # NEW_LEDS
299