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 Freecom FSG-3"
70 depends on LEDS_CLASS && MACH_FSG
72 This option enables support for the LEDs on the Freecom FSG-3.
75 tristate "LED Support for the WRAP series LEDs"
76 depends on LEDS_CLASS && SCx200_GPIO
78 This option enables support for the PCEngines WRAP programmable LEDs.
80 config LEDS_OMAP_DEBUG
81 boolean "LED Support for OMAP debug board LEDs"
82 depends on LEDS_CLASS=y && ARCH_OMAP
84 Enables support for the LEDs on the debug board used with OMAP
85 reference boards like H2/H3/H4 and Perseus2. Up to six of these
86 may be claimed by the original ARM debug LED API.
89 tristate "LED Support for OMAP GPIO LEDs"
90 depends on LEDS_CLASS && ARCH_OMAP
92 This option enables support for the LEDs on OMAP processors.
95 tristate "LED Support for OMAP PWM-controlled LEDs"
96 depends on LEDS_CLASS && ARCH_OMAP && OMAP_DM_TIMER
98 This options enables support for LEDs connected to GPIO lines
99 controlled by a PWM timer on OMAP CPUs.
102 tristate "LED Support for iPAQ H1940 device"
103 depends on LEDS_CLASS && ARCH_H1940
105 This option enables support for the LEDs on the h1940.
107 config LEDS_COBALT_QUBE
108 tristate "LED Support for the Cobalt Qube series front LED"
109 depends on LEDS_CLASS && MIPS_COBALT
111 This option enables support for the front LED on Cobalt Qube series
113 config LEDS_COBALT_RAQ
114 bool "LED Support for the Cobalt Raq series"
115 depends on LEDS_CLASS && MIPS_COBALT
118 This option enables support for the Cobalt Raq series LEDs.
121 tristate "LED Support for the HP Jornada 6xx"
122 depends on LEDS_CLASS && SH_HP6XX
124 This option enables led support for the handheld
125 HP Jornada 620/660/680/690.
128 tristate "LED Support for GPIO connected LEDs"
129 depends on LEDS_CLASS && GENERIC_GPIO
131 This option enables support for the LEDs connected to GPIO
132 outputs. To be useful the particular board must have LEDs
133 and they must be connected to the GPIO lines.
136 tristate "LED Support for the CM-X270 LEDs"
137 depends on LEDS_CLASS && MACH_ARMCORE
139 This option enables support for the CM-X270 LEDs.
141 config LEDS_CLEVO_MAIL
142 tristate "Mail LED on Clevo notebook (EXPERIMENTAL)"
143 depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI && EXPERIMENTAL
145 This driver makes the mail LED accessible from userspace
146 programs through the leds subsystem. This LED have three
147 known mode: off, blink at 0.5Hz and blink at 1Hz.
149 The driver supports two kinds of interface: using ledtrig-timer
150 or through /sys/class/leds/clevo::mail/brightness. As this LED
151 cannot change it's brightness it blinks instead. The brightness
152 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
155 This module can drive the mail LED for the following notebooks:
160 Clevo D400V/D470V (not tested, but might work)
162 Clevo M5x0N (not tested, but might work)
163 Positivo Mobile (Clevo M5x0V)
165 If your model is not listed here you can try the "nodetect"
168 To compile this driver as a module, choose M here: the
169 module will be called leds-clevo-mail.
171 comment "LED Triggers"
174 bool "LED Trigger support"
176 This option enables trigger support for the leds class.
177 These triggers allow kernel events to drive the LEDs and can
178 be configured via sysfs. If unsure, say Y.
180 config LEDS_TRIGGER_TIMER
181 tristate "LED Timer Trigger"
182 depends on LEDS_TRIGGERS
184 This allows LEDs to be controlled by a programmable timer
185 via sysfs. Some LED hardware can be programmed to start
186 blinking the LED without any further software interaction.
187 For more details read Documentation/leds-class.txt.
191 config LEDS_TRIGGER_IDE_DISK
192 bool "LED IDE Disk Trigger"
193 depends on LEDS_TRIGGERS && BLK_DEV_IDEDISK
195 This allows LEDs to be controlled by IDE disk activity.
198 config LEDS_TRIGGER_HEARTBEAT
199 tristate "LED Heartbeat Trigger"
200 depends on LEDS_TRIGGERS
202 This allows LEDs to be controlled by a CPU load average.
203 The flash frequency is a hyperbolic function of the 1-minute
207 config LEDS_TRIGGER_DEFAULT_ON
208 tristate "LED Default ON Trigger"
209 depends on LEDS_TRIGGERS
211 This allows LEDs to be initialised in the ON state.