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