Root/drivers/leds/Kconfig

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

Archive Download this file



interactive