]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.git/blob - drivers/leds/Kconfig
Merge branch 'irq-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git...
[mirror_ubuntu-bionic-kernel.git] / drivers / leds / Kconfig
1 menuconfig 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
10 if NEW_LEDS
11
12 config 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
18 if LEDS_CLASS
19
20 comment "LED drivers"
21
22 config LEDS_88PM860X
23 tristate "LED Support for Marvell 88PM860x PMIC"
24 depends on LEDS_CLASS && MFD_88PM860X
25 help
26 This option enables support for on-chip LED drivers found on Marvell
27 Semiconductor 88PM8606 PMIC.
28
29 config LEDS_ATMEL_PWM
30 tristate "LED Support using Atmel PWM outputs"
31 depends on ATMEL_PWM
32 help
33 This option enables support for LEDs driven using outputs
34 of the dedicated PWM controller found on newer Atmel SOCs.
35
36 config LEDS_LOCOMO
37 tristate "LED Support for Locomo device"
38 depends on SHARP_LOCOMO
39 help
40 This option enables support for the LEDs on Sharp Locomo.
41 Zaurus models SL-5500 and SL-5600.
42
43 config LEDS_MIKROTIK_RB532
44 tristate "LED Support for Mikrotik Routerboard 532"
45 depends on MIKROTIK_RB532
46 help
47 This option enables support for the so called "User LED" of
48 Mikrotik's Routerboard 532.
49
50 config LEDS_S3C24XX
51 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
52 depends on ARCH_S3C2410
53 help
54 This option enables support for LEDs connected to GPIO lines
55 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
56
57 config LEDS_AMS_DELTA
58 tristate "LED Support for the Amstrad Delta (E3)"
59 depends on MACH_AMS_DELTA
60 help
61 This option enables support for the LEDs on Amstrad Delta (E3).
62
63 config LEDS_NET48XX
64 tristate "LED Support for Soekris net48xx series Error LED"
65 depends on SCx200_GPIO
66 help
67 This option enables support for the Soekris net4801 and net4826 error
68 LED.
69
70 config LEDS_FSG
71 tristate "LED Support for the Freecom FSG-3"
72 depends on MACH_FSG
73 help
74 This option enables support for the LEDs on the Freecom FSG-3.
75
76 config LEDS_WRAP
77 tristate "LED Support for the WRAP series LEDs"
78 depends on SCx200_GPIO
79 help
80 This option enables support for the PCEngines WRAP programmable LEDs.
81
82 config LEDS_ALIX2
83 tristate "LED Support for ALIX.2 and ALIX.3 series"
84 depends on X86 && !GPIO_CS5535 && !CS5535_GPIO
85 help
86 This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
87 You have to set leds-alix2.force=1 for boards with Award BIOS.
88
89 config LEDS_H1940
90 tristate "LED Support for iPAQ H1940 device"
91 depends on ARCH_H1940
92 help
93 This option enables support for the LEDs on the h1940.
94
95 config LEDS_COBALT_QUBE
96 tristate "LED Support for the Cobalt Qube series front LED"
97 depends on MIPS_COBALT
98 help
99 This option enables support for the front LED on Cobalt Qube series
100
101 config LEDS_COBALT_RAQ
102 bool "LED Support for the Cobalt Raq series"
103 depends on LEDS_CLASS=y && MIPS_COBALT
104 select LEDS_TRIGGERS
105 help
106 This option enables support for the Cobalt Raq series LEDs.
107
108 config LEDS_SUNFIRE
109 tristate "LED support for SunFire servers."
110 depends on SPARC64
111 select LEDS_TRIGGERS
112 help
113 This option enables support for the Left, Middle, and Right
114 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
115
116 config LEDS_HP6XX
117 tristate "LED Support for the HP Jornada 6xx"
118 depends on SH_HP6XX
119 help
120 This option enables LED support for the handheld
121 HP Jornada 620/660/680/690.
122
123 config LEDS_PCA9532
124 tristate "LED driver for PCA9532 dimmer"
125 depends on I2C && INPUT && EXPERIMENTAL
126 help
127 This option enables support for NXP pca9532
128 LED controller. It is generally only useful
129 as a platform driver
130
131 config LEDS_GPIO
132 tristate "LED Support for GPIO connected LEDs"
133 depends on GENERIC_GPIO
134 help
135 This option enables support for the LEDs connected to GPIO
136 outputs. To be useful the particular board must have LEDs
137 and they must be connected to the GPIO lines. The LEDs must be
138 defined as platform devices and/or OpenFirmware platform devices.
139 The code to use these bindings can be selected below.
140
141 config LEDS_GPIO_PLATFORM
142 bool "Platform device bindings for GPIO LEDs"
143 depends on LEDS_GPIO
144 default y
145 help
146 Let the leds-gpio driver drive LEDs which have been defined as
147 platform devices. If you don't know what this means, say yes.
148
149 config LEDS_GPIO_OF
150 bool "OpenFirmware platform device bindings for GPIO LEDs"
151 depends on LEDS_GPIO && OF_DEVICE
152 default y
153 help
154 Let the leds-gpio driver drive LEDs which have been defined as
155 of_platform devices. For instance, LEDs which are listed in a "dts"
156 file.
157
158 config LEDS_LP3944
159 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
160 depends on I2C
161 help
162 This option enables support for LEDs connected to the National
163 Semiconductor LP3944 Lighting Management Unit (LMU) also known as
164 Fun Light Chip.
165
166 To compile this driver as a module, choose M here: the
167 module will be called leds-lp3944.
168
169 config LEDS_CLEVO_MAIL
170 tristate "Mail LED on Clevo notebook"
171 depends on X86 && SERIO_I8042 && DMI
172 help
173 This driver makes the mail LED accessible from userspace
174 programs through the leds subsystem. This LED have three
175 known mode: off, blink at 0.5Hz and blink at 1Hz.
176
177 The driver supports two kinds of interface: using ledtrig-timer
178 or through /sys/class/leds/clevo::mail/brightness. As this LED
179 cannot change it's brightness it blinks instead. The brightness
180 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
181 blink at 1Hz.
182
183 This module can drive the mail LED for the following notebooks:
184
185 Clevo D400P
186 Clevo D410J
187 Clevo D410V
188 Clevo D400V/D470V (not tested, but might work)
189 Clevo M540N
190 Clevo M5x0N (not tested, but might work)
191 Positivo Mobile (Clevo M5x0V)
192
193 If your model is not listed here you can try the "nodetect"
194 module parameter.
195
196 To compile this driver as a module, choose M here: the
197 module will be called leds-clevo-mail.
198
199 config LEDS_PCA955X
200 tristate "LED Support for PCA955x I2C chips"
201 depends on I2C
202 help
203 This option enables support for LEDs connected to PCA955x
204 LED driver chips accessed via the I2C bus. Supported
205 devices include PCA9550, PCA9551, PCA9552, and PCA9553.
206
207 config LEDS_WM831X_STATUS
208 tristate "LED support for status LEDs on WM831x PMICs"
209 depends on MFD_WM831X
210 help
211 This option enables support for the status LEDs of the WM831x
212 series of PMICs.
213
214 config LEDS_WM8350
215 tristate "LED Support for WM8350 AudioPlus PMIC"
216 depends on MFD_WM8350
217 help
218 This option enables support for LEDs driven by the Wolfson
219 Microelectronics WM8350 AudioPlus PMIC.
220
221 config LEDS_DA903X
222 tristate "LED Support for DA9030/DA9034 PMIC"
223 depends on PMIC_DA903X
224 help
225 This option enables support for on-chip LED drivers found
226 on Dialog Semiconductor DA9030/DA9034 PMICs.
227
228 config LEDS_DAC124S085
229 tristate "LED Support for DAC124S085 SPI DAC"
230 depends on SPI
231 help
232 This option enables support for DAC124S085 SPI DAC from NatSemi,
233 which can be used to control up to four LEDs.
234
235 config LEDS_PWM
236 tristate "PWM driven LED Support"
237 depends on HAVE_PWM
238 help
239 This option enables support for pwm driven LEDs
240
241 config LEDS_REGULATOR
242 tristate "REGULATOR driven LED support"
243 depends on REGULATOR
244 help
245 This option enables support for regulator driven LEDs.
246
247 config LEDS_BD2802
248 tristate "LED driver for BD2802 RGB LED"
249 depends on I2C
250 help
251 This option enables support for BD2802GU RGB LED driver chips
252 accessed via the I2C bus.
253
254 config LEDS_INTEL_SS4200
255 tristate "LED driver for Intel NAS SS4200 series"
256 depends on PCI && DMI
257 help
258 This option enables support for the Intel SS4200 series of
259 Network Attached Storage servers. You may control the hard
260 drive or power LEDs on the front panel. Using this driver
261 can stop the front LED from blinking after startup.
262
263 config LEDS_LT3593
264 tristate "LED driver for LT3593 controllers"
265 depends on GENERIC_GPIO
266 help
267 This option enables support for LEDs driven by a Linear Technology
268 LT3593 controller. This controller uses a special one-wire pulse
269 coding protocol to set the brightness.
270
271 config LEDS_ADP5520
272 tristate "LED Support for ADP5520/ADP5501 PMIC"
273 depends on PMIC_ADP5520
274 help
275 This option enables support for on-chip LED drivers found
276 on Analog Devices ADP5520/ADP5501 PMICs.
277
278 To compile this driver as a module, choose M here: the module will
279 be called leds-adp5520.
280
281 config LEDS_DELL_NETBOOKS
282 tristate "External LED on Dell Business Netbooks"
283 depends on X86 && ACPI_WMI
284 help
285 This adds support for the Latitude 2100 and similar
286 notebooks that have an external LED.
287
288 config LEDS_TRIGGERS
289 bool "LED Trigger support"
290 help
291 This option enables trigger support for the leds class.
292 These triggers allow kernel events to drive the LEDs and can
293 be configured via sysfs. If unsure, say Y.
294
295 if LEDS_TRIGGERS
296
297 comment "LED Triggers"
298
299 config LEDS_TRIGGER_TIMER
300 tristate "LED Timer Trigger"
301 help
302 This allows LEDs to be controlled by a programmable timer
303 via sysfs. Some LED hardware can be programmed to start
304 blinking the LED without any further software interaction.
305 For more details read Documentation/leds-class.txt.
306
307 If unsure, say Y.
308
309 config LEDS_TRIGGER_IDE_DISK
310 bool "LED IDE Disk Trigger"
311 depends on IDE_GD_ATA
312 help
313 This allows LEDs to be controlled by IDE disk activity.
314 If unsure, say Y.
315
316 config LEDS_TRIGGER_HEARTBEAT
317 tristate "LED Heartbeat Trigger"
318 help
319 This allows LEDs to be controlled by a CPU load average.
320 The flash frequency is a hyperbolic function of the 1-minute
321 load average.
322 If unsure, say Y.
323
324 config LEDS_TRIGGER_BACKLIGHT
325 tristate "LED backlight Trigger"
326 help
327 This allows LEDs to be controlled as a backlight device: they
328 turn off and on when the display is blanked and unblanked.
329
330 If unsure, say N.
331
332 config LEDS_TRIGGER_GPIO
333 tristate "LED GPIO Trigger"
334 depends on GPIOLIB
335 help
336 This allows LEDs to be controlled by gpio events. It's good
337 when using gpios as switches and triggering the needed LEDs
338 from there. One use case is n810's keypad LEDs that could
339 be triggered by this trigger when user slides up to show
340 keypad.
341
342 If unsure, say N.
343
344 config LEDS_TRIGGER_DEFAULT_ON
345 tristate "LED Default ON Trigger"
346 help
347 This allows LEDs to be initialised in the ON state.
348 If unsure, say Y.
349
350 comment "iptables trigger is under Netfilter config (LED target)"
351 depends on LEDS_TRIGGERS
352
353 endif # LEDS_TRIGGERS
354
355 endif # LEDS_CLASS
356
357 endif # NEW_LEDS