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 14if NEW_LEDS 15 16config LEDS_CLASS 17 tristate "LED Class Support" 18 help 19 This option enables the led sysfs class in /sys/class/leds. You'll 20 need this to do anything useful with LEDs. If unsure, say N. 21 22config LEDS_CLASS_FLASH 23 tristate "LED Flash Class Support" 24 depends on LEDS_CLASS 25 help 26 This option enables the flash led sysfs class in /sys/class/leds. 27 It wrapps LED Class and adds flash LEDs specific sysfs attributes 28 and kernel internal API to it. You'll need this to provide support 29 for the flash related features of a LED device. It can be built 30 as a module. 31 32config LEDS_BRIGHTNESS_HW_CHANGED 33 bool "LED Class brightness_hw_changed attribute support" 34 depends on LEDS_CLASS 35 help 36 This option enables support for the brightness_hw_changed attribute 37 for led sysfs class devices under /sys/class/leds. 38 39 See Documentation/ABI/testing/sysfs-class-led for details. 40 41comment "LED drivers" 42 43config LEDS_88PM860X 44 tristate "LED Support for Marvell 88PM860x PMIC" 45 depends on LEDS_CLASS 46 depends on MFD_88PM860X 47 help 48 This option enables support for on-chip LED drivers found on Marvell 49 Semiconductor 88PM8606 PMIC. 50 51config LEDS_AAT1290 52 tristate "LED support for the AAT1290" 53 depends on LEDS_CLASS_FLASH 54 depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS 55 depends on GPIOLIB || COMPILE_TEST 56 depends on OF 57 depends on PINCTRL 58 help 59 This option enables support for the LEDs on the AAT1290. 60 61config LEDS_BCM6328 62 tristate "LED Support for Broadcom BCM6328" 63 depends on LEDS_CLASS 64 depends on HAS_IOMEM 65 depends on OF 66 help 67 This option enables support for LEDs connected to the BCM6328 68 LED HW controller accessed via MMIO registers. 69 70config LEDS_BCM6358 71 tristate "LED Support for Broadcom BCM6358" 72 depends on LEDS_CLASS 73 depends on HAS_IOMEM 74 depends on OF 75 help 76 This option enables support for LEDs connected to the BCM6358 77 LED HW controller accessed via MMIO registers. 78 79config LEDS_CPCAP 80 tristate "LED Support for Motorola CPCAP" 81 depends on LEDS_CLASS 82 depends on MFD_CPCAP 83 depends on OF 84 help 85 This option enables support for LEDs offered by Motorola's 86 CPCAP PMIC. 87 88config LEDS_LM3530 89 tristate "LCD Backlight driver for LM3530" 90 depends on LEDS_CLASS 91 depends on I2C 92 help 93 This option enables support for the LCD backlight using 94 LM3530 ambient light sensor chip. This ALS chip can be 95 controlled manually or using PWM input or using ambient 96 light automatically. 97 98config LEDS_LM3533 99 tristate "LED support for LM3533" 100 depends on LEDS_CLASS 101 depends on MFD_LM3533 102 help 103 This option enables support for the LEDs on National Semiconductor / 104 TI LM3533 Lighting Power chips. 105 106 The LEDs can be controlled directly, through PWM input, or by the 107 ambient-light-sensor interface. The chip supports 108 hardware-accelerated blinking with maximum on and off periods of 9.8 109 and 77 seconds respectively. 110 111config LEDS_LM3642 112 tristate "LED support for LM3642 Chip" 113 depends on LEDS_CLASS && I2C 114 select REGMAP_I2C 115 help 116 This option enables support for LEDs connected to LM3642. 117 The LM3642 is a 4MHz fixed-frequency synchronous boost 118 converter plus 1.5A constant current driver for a high-current 119 white LED. 120 121 122config LEDS_LOCOMO 123 tristate "LED Support for Locomo device" 124 depends on LEDS_CLASS 125 depends on SHARP_LOCOMO 126 help 127 This option enables support for the LEDs on Sharp Locomo. 128 Zaurus models SL-5500 and SL-5600. 129 130config LEDS_MIKROTIK_RB532 131 tristate "LED Support for Mikrotik Routerboard 532" 132 depends on LEDS_CLASS 133 depends on MIKROTIK_RB532 134 help 135 This option enables support for the so called "User LED" of 136 Mikrotik's Routerboard 532. 137 138config LEDS_MT6323 139 tristate "LED Support for Mediatek MT6323 PMIC" 140 depends on LEDS_CLASS 141 depends on MFD_MT6397 142 help 143 This option enables support for on-chip LED drivers found on 144 Mediatek MT6323 PMIC. 145 146config LEDS_S3C24XX 147 tristate "LED Support for Samsung S3C24XX GPIO LEDs" 148 depends on LEDS_CLASS 149 depends on ARCH_S3C24XX 150 help 151 This option enables support for LEDs connected to GPIO lines 152 on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440. 153 154config LEDS_NET48XX 155 tristate "LED Support for Soekris net48xx series Error LED" 156 depends on LEDS_CLASS 157 depends on SCx200_GPIO 158 help 159 This option enables support for the Soekris net4801 and net4826 error 160 LED. 161 162config LEDS_FSG 163 tristate "LED Support for the Freecom FSG-3" 164 depends on LEDS_CLASS 165 depends on MACH_FSG 166 help 167 This option enables support for the LEDs on the Freecom FSG-3. 168 169config LEDS_WRAP 170 tristate "LED Support for the WRAP series LEDs" 171 depends on LEDS_CLASS 172 depends on SCx200_GPIO 173 help 174 This option enables support for the PCEngines WRAP programmable LEDs. 175 176config LEDS_COBALT_QUBE 177 tristate "LED Support for the Cobalt Qube series front LED" 178 depends on LEDS_CLASS 179 depends on MIPS_COBALT 180 help 181 This option enables support for the front LED on Cobalt Qube series 182 183config LEDS_COBALT_RAQ 184 bool "LED Support for the Cobalt Raq series" 185 depends on LEDS_CLASS=y && MIPS_COBALT 186 select LEDS_TRIGGERS 187 help 188 This option enables support for the Cobalt Raq series LEDs. 189 190config LEDS_SUNFIRE 191 tristate "LED support for SunFire servers." 192 depends on LEDS_CLASS 193 depends on SPARC64 194 select LEDS_TRIGGERS 195 help 196 This option enables support for the Left, Middle, and Right 197 LEDs on the I/O and CPU boards of SunFire UltraSPARC servers. 198 199config LEDS_IPAQ_MICRO 200 tristate "LED Support for the Compaq iPAQ h3xxx" 201 depends on LEDS_CLASS 202 depends on MFD_IPAQ_MICRO 203 help 204 Choose this option if you want to use the notification LED on 205 Compaq/HP iPAQ h3100 and h3600. 206 207config LEDS_HP6XX 208 tristate "LED Support for the HP Jornada 6xx" 209 depends on LEDS_CLASS 210 depends on SH_HP6XX 211 help 212 This option enables LED support for the handheld 213 HP Jornada 620/660/680/690. 214 215config LEDS_PCA9532 216 tristate "LED driver for PCA9532 dimmer" 217 depends on LEDS_CLASS 218 depends on I2C && INPUT 219 help 220 This option enables support for NXP pca9532 221 LED controller. It is generally only useful 222 as a platform driver 223 224config LEDS_PCA9532_GPIO 225 bool "Enable GPIO support for PCA9532" 226 depends on LEDS_PCA9532 227 depends on GPIOLIB 228 help 229 Allow unused pins on PCA9532 to be used as gpio. 230 231 To use a pin as gpio pca9532_type in pca9532_platform data needs to 232 set to PCA9532_TYPE_GPIO. 233 234config LEDS_GPIO 235 tristate "LED Support for GPIO connected LEDs" 236 depends on LEDS_CLASS 237 depends on GPIOLIB || COMPILE_TEST 238 help 239 This option enables support for the LEDs connected to GPIO 240 outputs. To be useful the particular board must have LEDs 241 and they must be connected to the GPIO lines. The LEDs must be 242 defined as platform devices and/or OpenFirmware platform devices. 243 The code to use these bindings can be selected below. 244 245config LEDS_LP3944 246 tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip" 247 depends on LEDS_CLASS 248 depends on I2C 249 help 250 This option enables support for LEDs connected to the National 251 Semiconductor LP3944 Lighting Management Unit (LMU) also known as 252 Fun Light Chip. 253 254 To compile this driver as a module, choose M here: the 255 module will be called leds-lp3944. 256 257config LEDS_LP3952 258 tristate "LED Support for TI LP3952 2 channel LED driver" 259 depends on LEDS_CLASS 260 depends on I2C 261 depends on GPIOLIB 262 select REGMAP_I2C 263 help 264 This option enables support for LEDs connected to the Texas 265 Instruments LP3952 LED driver. 266 267 To compile this driver as a module, choose M here: the 268 module will be called leds-lp3952. 269 270config LEDS_LP55XX_COMMON 271 tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" 272 depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501 273 select FW_LOADER 274 select FW_LOADER_USER_HELPER 275 help 276 This option supports common operations for LP5521/5523/55231/5562/8501 277 devices. 278 279config LEDS_LP5521 280 tristate "LED Support for N.S. LP5521 LED driver chip" 281 depends on LEDS_CLASS && I2C 282 select LEDS_LP55XX_COMMON 283 help 284 If you say yes here you get support for the National Semiconductor 285 LP5521 LED driver. It is 3 channel chip with programmable engines. 286 Driver provides direct control via LED class and interface for 287 programming the engines. 288 289config LEDS_LP5523 290 tristate "LED Support for TI/National LP5523/55231 LED driver chip" 291 depends on LEDS_CLASS && I2C 292 select LEDS_LP55XX_COMMON 293 help 294 If you say yes here you get support for TI/National Semiconductor 295 LP5523/55231 LED driver. 296 It is 9 channel chip with programmable engines. 297 Driver provides direct control via LED class and interface for 298 programming the engines. 299 300config LEDS_LP5562 301 tristate "LED Support for TI LP5562 LED driver chip" 302 depends on LEDS_CLASS && I2C 303 select LEDS_LP55XX_COMMON 304 help 305 If you say yes here you get support for TI LP5562 LED driver. 306 It is 4 channels chip with programmable engines. 307 Driver provides direct control via LED class and interface for 308 programming the engines. 309 310config LEDS_LP8501 311 tristate "LED Support for TI LP8501 LED driver chip" 312 depends on LEDS_CLASS && I2C 313 select LEDS_LP55XX_COMMON 314 help 315 If you say yes here you get support for TI LP8501 LED driver. 316 It is 9 channel chip with programmable engines. 317 Driver provides direct control via LED class and interface for 318 programming the engines. 319 It is similar as LP5523, but output power selection is available. 320 And register layout and engine program schemes are different. 321 322config LEDS_LP8788 323 tristate "LED support for the TI LP8788 PMIC" 324 depends on LEDS_CLASS 325 depends on MFD_LP8788 326 help 327 This option enables support for the Keyboard LEDs on the LP8788 PMIC. 328 329config LEDS_LP8860 330 tristate "LED support for the TI LP8860 4 channel LED driver" 331 depends on LEDS_CLASS && I2C 332 select REGMAP_I2C 333 help 334 If you say yes here you get support for the TI LP8860 4 channel 335 LED driver. 336 This option enables support for the display cluster LEDs 337 on the LP8860 4 channel LED driver using the I2C communication 338 bus. 339 340config LEDS_CLEVO_MAIL 341 tristate "Mail LED on Clevo notebook" 342 depends on LEDS_CLASS 343 depends on X86 && SERIO_I8042 && DMI 344 help 345 This driver makes the mail LED accessible from userspace 346 programs through the leds subsystem. This LED have three 347 known mode: off, blink at 0.5Hz and blink at 1Hz. 348 349 The driver supports two kinds of interface: using ledtrig-timer 350 or through /sys/class/leds/clevo::mail/brightness. As this LED 351 cannot change it's brightness it blinks instead. The brightness 352 value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means 353 blink at 1Hz. 354 355 This module can drive the mail LED for the following notebooks: 356 357 Clevo D400P 358 Clevo D410J 359 Clevo D410V 360 Clevo D400V/D470V (not tested, but might work) 361 Clevo M540N 362 Clevo M5x0N (not tested, but might work) 363 Positivo Mobile (Clevo M5x0V) 364 365 If your model is not listed here you can try the "nodetect" 366 module parameter. 367 368 To compile this driver as a module, choose M here: the 369 module will be called leds-clevo-mail. 370 371config LEDS_PCA955X 372 tristate "LED Support for PCA955x I2C chips" 373 depends on LEDS_CLASS 374 depends on I2C 375 help 376 This option enables support for LEDs connected to PCA955x 377 LED driver chips accessed via the I2C bus. Supported 378 devices include PCA9550, PCA9551, PCA9552, and PCA9553. 379 380config LEDS_PCA963X 381 tristate "LED support for PCA963x I2C chip" 382 depends on LEDS_CLASS 383 depends on I2C 384 help 385 This option enables support for LEDs connected to the PCA963x 386 LED driver chip accessed via the I2C bus. Supported 387 devices include PCA9633 and PCA9634 388 389config LEDS_WM831X_STATUS 390 tristate "LED support for status LEDs on WM831x PMICs" 391 depends on LEDS_CLASS 392 depends on MFD_WM831X 393 help 394 This option enables support for the status LEDs of the WM831x 395 series of PMICs. 396 397config LEDS_WM8350 398 tristate "LED Support for WM8350 AudioPlus PMIC" 399 depends on LEDS_CLASS 400 depends on MFD_WM8350 401 help 402 This option enables support for LEDs driven by the Wolfson 403 Microelectronics WM8350 AudioPlus PMIC. 404 405config LEDS_DA903X 406 tristate "LED Support for DA9030/DA9034 PMIC" 407 depends on LEDS_CLASS 408 depends on PMIC_DA903X 409 help 410 This option enables support for on-chip LED drivers found 411 on Dialog Semiconductor DA9030/DA9034 PMICs. 412 413config LEDS_DA9052 414 tristate "Dialog DA9052/DA9053 LEDS" 415 depends on LEDS_CLASS 416 depends on PMIC_DA9052 417 help 418 This option enables support for on-chip LED drivers found 419 on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs. 420 421config LEDS_DAC124S085 422 tristate "LED Support for DAC124S085 SPI DAC" 423 depends on LEDS_CLASS 424 depends on SPI 425 help 426 This option enables support for DAC124S085 SPI DAC from NatSemi, 427 which can be used to control up to four LEDs. 428 429config LEDS_PWM 430 tristate "PWM driven LED Support" 431 depends on LEDS_CLASS 432 depends on PWM 433 help 434 This option enables support for pwm driven LEDs 435 436config LEDS_REGULATOR 437 tristate "REGULATOR driven LED support" 438 depends on LEDS_CLASS 439 depends on REGULATOR 440 help 441 This option enables support for regulator driven LEDs. 442 443config LEDS_BD2802 444 tristate "LED driver for BD2802 RGB LED" 445 depends on LEDS_CLASS 446 depends on I2C 447 help 448 This option enables support for BD2802GU RGB LED driver chips 449 accessed via the I2C bus. 450 451config LEDS_INTEL_SS4200 452 tristate "LED driver for Intel NAS SS4200 series" 453 depends on LEDS_CLASS 454 depends on PCI && DMI 455 depends on X86 456 help 457 This option enables support for the Intel SS4200 series of 458 Network Attached Storage servers. You may control the hard 459 drive or power LEDs on the front panel. Using this driver 460 can stop the front LED from blinking after startup. 461 462config LEDS_LT3593 463 tristate "LED driver for LT3593 controllers" 464 depends on LEDS_CLASS 465 depends on GPIOLIB || COMPILE_TEST 466 help 467 This option enables support for LEDs driven by a Linear Technology 468 LT3593 controller. This controller uses a special one-wire pulse 469 coding protocol to set the brightness. 470 471config LEDS_ADP5520 472 tristate "LED Support for ADP5520/ADP5501 PMIC" 473 depends on LEDS_CLASS 474 depends on PMIC_ADP5520 475 help 476 This option enables support for on-chip LED drivers found 477 on Analog Devices ADP5520/ADP5501 PMICs. 478 479 To compile this driver as a module, choose M here: the module will 480 be called leds-adp5520. 481 482config LEDS_MC13783 483 tristate "LED Support for MC13XXX PMIC" 484 depends on LEDS_CLASS 485 depends on MFD_MC13XXX 486 help 487 This option enable support for on-chip LED drivers found 488 on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC. 489 490config LEDS_NS2 491 tristate "LED support for Network Space v2 GPIO LEDs" 492 depends on LEDS_CLASS 493 depends on MACH_KIRKWOOD || MACH_ARMADA_370 494 default y 495 help 496 This option enables support for the dual-GPIO LEDs found on the 497 following LaCie/Seagate boards: 498 499 Network Space v2 (and parents: Max, Mini) 500 Internet Space v2 501 d2 Network v2 502 n090401 (Seagate NAS 4-Bay) 503 504config LEDS_NETXBIG 505 tristate "LED support for Big Network series LEDs" 506 depends on LEDS_CLASS 507 depends on MACH_KIRKWOOD 508 default y 509 help 510 This option enable support for LEDs found on the LaCie 2Big 511 and 5Big Network v2 boards. The LEDs are wired to a CPLD and are 512 controlled through a GPIO extension bus. 513 514config LEDS_ASIC3 515 bool "LED support for the HTC ASIC3" 516 depends on LEDS_CLASS=y 517 depends on MFD_ASIC3 518 default y 519 help 520 This option enables support for the LEDs on the HTC ASIC3. The HTC 521 ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver 522 cannot be used. This driver supports hardware blinking with an on+off 523 period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700. 524 525config LEDS_TCA6507 526 tristate "LED Support for TCA6507 I2C chip" 527 depends on LEDS_CLASS && I2C 528 help 529 This option enables support for LEDs connected to TC6507 530 LED driver chips accessed via the I2C bus. 531 Driver support brightness control and hardware-assisted blinking. 532 533config LEDS_TLC591XX 534 tristate "LED driver for TLC59108 and TLC59116 controllers" 535 depends on LEDS_CLASS && I2C 536 select REGMAP_I2C 537 help 538 This option enables support for Texas Instruments TLC59108 539 and TLC59116 LED controllers. 540 541config LEDS_MAX77693 542 tristate "LED support for MAX77693 Flash" 543 depends on LEDS_CLASS_FLASH 544 depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS 545 depends on MFD_MAX77693 546 depends on OF 547 help 548 This option enables support for the flash part of the MAX77693 549 multifunction device. It has build in control for two leds in flash 550 and torch mode. 551 552config LEDS_MAX8997 553 tristate "LED support for MAX8997 PMIC" 554 depends on LEDS_CLASS && MFD_MAX8997 555 help 556 This option enables support for on-chip LED drivers on 557 MAXIM MAX8997 PMIC. 558 559config LEDS_LM355x 560 tristate "LED support for LM355x Chips, LM3554 and LM3556" 561 depends on LEDS_CLASS && I2C 562 select REGMAP_I2C 563 help 564 This option enables support for LEDs connected to LM355x. 565 LM355x includes Torch, Flash and Indicator functions. 566 567config LEDS_OT200 568 tristate "LED support for the Bachmann OT200" 569 depends on LEDS_CLASS && HAS_IOMEM && (X86_32 || COMPILE_TEST) 570 help 571 This option enables support for the LEDs on the Bachmann OT200. 572 Say Y to enable LEDs on the Bachmann OT200. 573 574config LEDS_MENF21BMC 575 tristate "LED support for the MEN 14F021P00 BMC" 576 depends on LEDS_CLASS && MFD_MENF21BMC 577 help 578 Say Y here to include support for the MEN 14F021P00 BMC LEDs. 579 580 This driver can also be built as a module. If so the module 581 will be called leds-menf21bmc. 582 583config LEDS_KTD2692 584 tristate "LED support for KTD2692 flash LED controller" 585 depends on LEDS_CLASS_FLASH && OF 586 depends on GPIOLIB || COMPILE_TEST 587 help 588 This option enables support for KTD2692 LED flash connected 589 through ExpressWire interface. 590 591 Say Y to enable this driver. 592 593config LEDS_IS31FL319X 594 tristate "LED Support for ISSI IS31FL319x I2C LED controller family" 595 depends on LEDS_CLASS && I2C && OF 596 select REGMAP_I2C 597 help 598 This option enables support for LEDs connected to ISSI IS31FL319x 599 fancy LED driver chips accessed via the I2C bus. 600 Driver supports individual PWM brightness control for each channel. 601 602 This driver can also be built as a module. If so the module will be 603 called leds-is31fl319x. 604 605config LEDS_IS31FL32XX 606 tristate "LED support for ISSI IS31FL32XX I2C LED controller family" 607 depends on LEDS_CLASS && I2C && OF 608 help 609 Say Y here to include support for ISSI IS31FL32XX and Si-En SN32xx 610 LED controllers. They are I2C devices with multiple constant-current 611 channels, each with independent 256-level PWM control. 612 613comment "LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)" 614 615config LEDS_BLINKM 616 tristate "LED support for the BlinkM I2C RGB LED" 617 depends on LEDS_CLASS 618 depends on I2C 619 help 620 This option enables support for the BlinkM RGB LED connected 621 through I2C. Say Y to enable support for the BlinkM LED. 622 623config LEDS_POWERNV 624 tristate "LED support for PowerNV Platform" 625 depends on LEDS_CLASS 626 depends on PPC_POWERNV 627 depends on OF 628 help 629 This option enables support for the system LEDs present on 630 PowerNV platforms. Say 'y' to enable this support in kernel. 631 To compile this driver as a module, choose 'm' here: the module 632 will be called leds-powernv. 633 634config LEDS_SYSCON 635 bool "LED support for LEDs on system controllers" 636 depends on LEDS_CLASS=y 637 depends on MFD_SYSCON 638 depends on OF 639 help 640 This option enabled support for the LEDs on syscon type 641 devices. This will only work with device tree enabled 642 devices. 643 644config LEDS_PM8058 645 tristate "LED Support for the Qualcomm PM8058 PMIC" 646 depends on MFD_PM8XXX 647 depends on LEDS_CLASS 648 help 649 Choose this option if you want to use the LED drivers in 650 the Qualcomm PM8058 PMIC. 651 652config LEDS_MLXCPLD 653 tristate "LED support for the Mellanox boards" 654 depends on X86_64 && DMI 655 depends on LEDS_CLASS 656 help 657 This option enabled support for the LEDs on the Mellanox 658 boards. Say Y to enabled these. 659 660config LEDS_USER 661 tristate "Userspace LED support" 662 depends on LEDS_CLASS 663 help 664 This option enables support for userspace LEDs. Say 'y' to enable this 665 support in kernel. To compile this driver as a module, choose 'm' here: 666 the module will be called uleds. 667 668config LEDS_NIC78BX 669 tristate "LED support for NI PXI NIC78bx devices" 670 depends on LEDS_CLASS 671 depends on X86 && ACPI 672 help 673 This option enables support for the User1 and User2 LEDs on NI 674 PXI NIC78bx devices. 675 676 To compile this driver as a module, choose M here: the module 677 will be called leds-nic78bx. 678 679comment "LED Triggers" 680source "drivers/leds/trigger/Kconfig" 681 682endif # NEW_LEDS 683