4 Say Y to enable Linux LED support. This allows control of supported
5 LEDs from both userspace and optionally, by kernel events (triggers).
7 This is not related to standard keyboard LEDs which are controlled
13 tristate "LED Class Support"
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.
21 tristate "LED Support using Atmel PWM outputs"
22 depends on LEDS_CLASS && ATMEL_PWM
24 This option enables support for LEDs driven using outputs
25 of the dedicated PWM controller found on newer Atmel SOCs.
28 tristate "LED Support for the Sharp SL-C7x0 series"
29 depends on LEDS_CLASS && PXA_SHARP_C7xx
31 This option enables support for the LEDs on Sharp Zaurus
32 SL-C7x0 series (C700, C750, C760, C860).
35 tristate "LED Support for Locomo device"
36 depends on LEDS_CLASS && SHARP_LOCOMO
38 This option enables support for the LEDs on Sharp Locomo.
39 Zaurus models SL-5500 and SL-5600.
42 tristate "LED Support for the Sharp SL-Cxx00 series"
43 depends on LEDS_CLASS && PXA_SHARP_Cxx00
45 This option enables support for the LEDs on Sharp Zaurus
46 SL-Cxx00 series (C1000, C3000, C3100).
49 tristate "LED Support for Samsung S3C24XX GPIO LEDs"
50 depends on LEDS_CLASS && ARCH_S3C2410
52 This option enables support for LEDs connected to GPIO lines
53 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
56 tristate "LED Support for the Amstrad Delta (E3)"
57 depends on LEDS_CLASS && MACH_AMS_DELTA
59 This option enables support for the LEDs on Amstrad Delta (E3).
62 tristate "LED Support for Soekris net48xx series Error LED"
63 depends on LEDS_CLASS && SCx200_GPIO
65 This option enables support for the Soekris net4801 and net4826 error
69 tristate "LED Support for the WRAP series LEDs"
70 depends on LEDS_CLASS && SCx200_GPIO
72 This option enables support for the PCEngines WRAP programmable LEDs.
75 tristate "LED Support for iPAQ H1940 device"
76 depends on LEDS_CLASS && ARCH_H1940
78 This option enables support for the LEDs on the h1940.
80 config LEDS_COBALT_QUBE
81 tristate "LED Support for the Cobalt Qube series front LED"
82 depends on LEDS_CLASS && MIPS_COBALT
84 This option enables support for the front LED on Cobalt Qube series
86 config LEDS_COBALT_RAQ
87 bool "LED Support for the Cobalt Raq series"
88 depends on LEDS_CLASS && MIPS_COBALT
91 This option enables support for the Cobalt Raq series LEDs.
94 tristate "LED Support for the HP Jornada 6xx"
95 depends on LEDS_CLASS && SH_HP6XX
97 This option enables led support for the handheld
98 HP Jornada 620/660/680/690.
101 tristate "LED Support for GPIO connected LEDs"
102 depends on LEDS_CLASS && GENERIC_GPIO
104 This option enables support for the LEDs connected to GPIO
105 outputs. To be useful the particular board must have LEDs
106 and they must be connected to the GPIO lines.
109 tristate "LED Support for the CM-X270 LEDs"
110 depends on LEDS_CLASS && MACH_ARMCORE
112 This option enables support for the CM-X270 LEDs.
114 config LEDS_CLEVO_MAIL
115 tristate "Mail LED on Clevo notebook (EXPERIMENTAL)"
116 depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI && EXPERIMENTAL
118 This driver makes the mail LED accessible from userspace
119 programs through the leds subsystem. This LED have three
120 known mode: off, blink at 0.5Hz and blink at 1Hz.
122 The driver supports two kinds of interface: using ledtrig-timer
123 or through /sys/class/leds/clevo::mail/brightness. As this LED
124 cannot change it's brightness it blinks instead. The brightness
125 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
128 This module can drive the mail LED for the following notebooks:
133 Clevo D400V/D470V (not tested, but might work)
135 Clevo M5x0N (not tested, but might work)
136 Positivo Mobile (Clevo M5x0V)
138 If your model is not listed here you can try the "nodetect"
141 To compile this driver as a module, choose M here: the
142 module will be called leds-clevo-mail.
144 comment "LED Triggers"
147 bool "LED Trigger support"
149 This option enables trigger support for the leds class.
150 These triggers allow kernel events to drive the LEDs and can
151 be configured via sysfs. If unsure, say Y.
153 config LEDS_TRIGGER_TIMER
154 tristate "LED Timer Trigger"
155 depends on LEDS_TRIGGERS
157 This allows LEDs to be controlled by a programmable timer
158 via sysfs. Some LED hardware can be programmed to start
159 blinking the LED without any further software interaction.
160 For more details read Documentation/leds-class.txt.
164 config LEDS_TRIGGER_IDE_DISK
165 bool "LED IDE Disk Trigger"
166 depends on LEDS_TRIGGERS && BLK_DEV_IDEDISK
168 This allows LEDs to be controlled by IDE disk activity.
171 config LEDS_TRIGGER_HEARTBEAT
172 tristate "LED Heartbeat Trigger"
173 depends on LEDS_TRIGGERS
175 This allows LEDs to be controlled by a CPU load average.
176 The flash frequency is a hyperbolic function of the 1-minute