xref: /openbmc/linux/drivers/leds/Kconfig (revision e8e0929d)
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	  You have to set leds-alix2.force=1 for boards with Award BIOS.
79
80config LEDS_H1940
81	tristate "LED Support for iPAQ H1940 device"
82	depends on LEDS_CLASS && ARCH_H1940
83	help
84	  This option enables support for the LEDs on the h1940.
85
86config LEDS_COBALT_QUBE
87	tristate "LED Support for the Cobalt Qube series front LED"
88	depends on LEDS_CLASS && MIPS_COBALT
89	help
90	  This option enables support for the front LED on Cobalt Qube series
91
92config LEDS_COBALT_RAQ
93	bool "LED Support for the Cobalt Raq series"
94	depends on LEDS_CLASS=y && MIPS_COBALT
95	select LEDS_TRIGGERS
96	help
97	  This option enables support for the Cobalt Raq series LEDs.
98
99config LEDS_SUNFIRE
100	tristate "LED support for SunFire servers."
101	depends on LEDS_CLASS && SPARC64
102	select LEDS_TRIGGERS
103	help
104	  This option enables support for the Left, Middle, and Right
105	  LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
106
107config LEDS_HP6XX
108	tristate "LED Support for the HP Jornada 6xx"
109	depends on LEDS_CLASS && SH_HP6XX
110	help
111	  This option enables LED support for the handheld
112	  HP Jornada 620/660/680/690.
113
114config LEDS_PCA9532
115	tristate "LED driver for PCA9532 dimmer"
116	depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
117	help
118	  This option enables support for NXP pca9532
119	  LED controller. It is generally only useful
120	  as a platform driver
121
122config LEDS_GPIO
123	tristate "LED Support for GPIO connected LEDs"
124	depends on LEDS_CLASS && GENERIC_GPIO
125	help
126	  This option enables support for the LEDs connected to GPIO
127	  outputs. To be useful the particular board must have LEDs
128	  and they must be connected to the GPIO lines.  The LEDs must be
129	  defined as platform devices and/or OpenFirmware platform devices.
130	  The code to use these bindings can be selected below.
131
132config LEDS_GPIO_PLATFORM
133	bool "Platform device bindings for GPIO LEDs"
134	depends on LEDS_GPIO
135	default y
136	help
137	  Let the leds-gpio driver drive LEDs which have been defined as
138	  platform devices.  If you don't know what this means, say yes.
139
140config LEDS_GPIO_OF
141	bool "OpenFirmware platform device bindings for GPIO LEDs"
142	depends on LEDS_GPIO && OF_DEVICE
143	default y
144	help
145	  Let the leds-gpio driver drive LEDs which have been defined as
146	  of_platform devices.  For instance, LEDs which are listed in a "dts"
147	  file.
148
149config LEDS_LP3944
150	tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
151	depends on LEDS_CLASS && I2C
152	help
153	  This option enables support for LEDs connected to the National
154	  Semiconductor LP3944 Lighting Management Unit (LMU) also known as
155	  Fun Light Chip.
156
157	  To compile this driver as a module, choose M here: the
158	  module will be called leds-lp3944.
159
160config LEDS_CLEVO_MAIL
161	tristate "Mail LED on Clevo notebook"
162	depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
163	help
164	  This driver makes the mail LED accessible from userspace
165	  programs through the leds subsystem. This LED have three
166	  known mode: off, blink at 0.5Hz and blink at 1Hz.
167
168	  The driver supports two kinds of interface: using ledtrig-timer
169	  or through /sys/class/leds/clevo::mail/brightness. As this LED
170	  cannot change it's brightness it blinks instead. The brightness
171	  value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
172	  blink at 1Hz.
173
174	  This module can drive the mail LED for the following notebooks:
175
176	  	Clevo D400P
177	  	Clevo D410J
178	  	Clevo D410V
179	  	Clevo D400V/D470V (not tested, but might work)
180	  	Clevo M540N
181	  	Clevo M5x0N (not tested, but might work)
182	  	Positivo Mobile (Clevo M5x0V)
183
184	  If your model is not listed here you can try the "nodetect"
185	  module parameter.
186
187	  To compile this driver as a module, choose M here: the
188	  module will be called leds-clevo-mail.
189
190config LEDS_PCA955X
191	tristate "LED Support for PCA955x I2C chips"
192	depends on LEDS_CLASS && I2C
193	help
194	  This option enables support for LEDs connected to PCA955x
195	  LED driver chips accessed via the I2C bus.  Supported
196	  devices include PCA9550, PCA9551, PCA9552, and PCA9553.
197
198config LEDS_WM831X_STATUS
199	tristate "LED support for status LEDs on WM831x PMICs"
200	depends on LEDS_CLASS && MFD_WM831X
201	help
202	  This option enables support for the status LEDs of the WM831x
203          series of PMICs.
204
205config LEDS_WM8350
206	tristate "LED Support for WM8350 AudioPlus PMIC"
207	depends on LEDS_CLASS && MFD_WM8350
208	help
209	  This option enables support for LEDs driven by the Wolfson
210	  Microelectronics WM8350 AudioPlus PMIC.
211
212config LEDS_DA903X
213	tristate "LED Support for DA9030/DA9034 PMIC"
214	depends on LEDS_CLASS && PMIC_DA903X
215	help
216	  This option enables support for on-chip LED drivers found
217	  on Dialog Semiconductor DA9030/DA9034 PMICs.
218
219config LEDS_DAC124S085
220	tristate "LED Support for DAC124S085 SPI DAC"
221	depends on LEDS_CLASS && SPI
222	help
223	  This option enables support for DAC124S085 SPI DAC from NatSemi,
224	  which can be used to control up to four LEDs.
225
226config LEDS_PWM
227	tristate "PWM driven LED Support"
228	depends on LEDS_CLASS && HAVE_PWM
229	help
230	  This option enables support for pwm driven LEDs
231
232config LEDS_BD2802
233	tristate "LED driver for BD2802 RGB LED"
234	depends on LEDS_CLASS && I2C
235	help
236	  This option enables support for BD2802GU RGB LED driver chips
237	  accessed via the I2C bus.
238
239comment "LED Triggers"
240
241config LEDS_TRIGGERS
242	bool "LED Trigger support"
243	help
244	  This option enables trigger support for the leds class.
245	  These triggers allow kernel events to drive the LEDs and can
246	  be configured via sysfs. If unsure, say Y.
247
248config LEDS_TRIGGER_TIMER
249	tristate "LED Timer Trigger"
250	depends on LEDS_TRIGGERS
251	help
252	  This allows LEDs to be controlled by a programmable timer
253	  via sysfs. Some LED hardware can be programmed to start
254	  blinking the LED without any further software interaction.
255	  For more details read Documentation/leds-class.txt.
256
257	  If unsure, say Y.
258
259config LEDS_TRIGGER_IDE_DISK
260	bool "LED IDE Disk Trigger"
261	depends on LEDS_TRIGGERS && IDE_GD_ATA
262	help
263	  This allows LEDs to be controlled by IDE disk activity.
264	  If unsure, say Y.
265
266config LEDS_TRIGGER_HEARTBEAT
267	tristate "LED Heartbeat Trigger"
268	depends on LEDS_TRIGGERS
269	help
270	  This allows LEDs to be controlled by a CPU load average.
271	  The flash frequency is a hyperbolic function of the 1-minute
272	  load average.
273	  If unsure, say Y.
274
275config LEDS_TRIGGER_BACKLIGHT
276	tristate "LED backlight Trigger"
277	depends on LEDS_TRIGGERS
278	help
279	  This allows LEDs to be controlled as a backlight device: they
280	  turn off and on when the display is blanked and unblanked.
281
282	  If unsure, say N.
283
284config LEDS_TRIGGER_GPIO
285	tristate "LED GPIO Trigger"
286	depends on LEDS_TRIGGERS
287	depends on GPIOLIB
288	help
289	  This allows LEDs to be controlled by gpio events. It's good
290	  when using gpios as switches and triggering the needed LEDs
291	  from there. One use case is n810's keypad LEDs that could
292	  be triggered by this trigger when user slides up to show
293	  keypad.
294
295	  If unsure, say N.
296
297config LEDS_TRIGGER_DEFAULT_ON
298	tristate "LED Default ON Trigger"
299	depends on LEDS_TRIGGERS
300	help
301	  This allows LEDs to be initialised in the ON state.
302	  If unsure, say Y.
303
304comment "iptables trigger is under Netfilter config (LED target)"
305	depends on LEDS_TRIGGERS
306
307endif # NEW_LEDS
308