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