drivers/leds/Kconfig

   1 config 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
   8 menuconfig 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
  17 if NEW_LEDS
  18
  19 config LEDS_CLASS
  20         tristate "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
  25 comment "LED drivers"
  26
  27 config 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
  35 config 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
  43 config 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
  53 config LEDS_LM3533
  54         tristate "LED support for LM3533"
  55         depends on LEDS_CLASS
  56         depends on MFD_LM3533
  57         help
  58           This option enables support for the LEDs on National Semiconductor /
  59           TI LM3533 Lighting Power chips.
  60
  61           The LEDs can be controlled directly, through PWM input, or by the
  62           ambient-light-sensor interface. The chip supports
  63           hardware-accelerated blinking with maximum on and off periods of 9.8
  64           and 77 seconds respectively.
  65
  66 config LEDS_LM3642
  67         tristate "LED support for LM3642 Chip"
  68         depends on LEDS_CLASS && I2C
  69         select REGMAP_I2C
  70         help
  71           This option enables support for LEDs connected to LM3642.
  72           The LM3642 is a 4MHz fixed-frequency synchronous boost
  73           converter plus 1.5A constant current driver for a high-current
  74           white LED.
  75
  76
  77 config LEDS_LOCOMO
  78         tristate "LED Support for Locomo device"
  79         depends on LEDS_CLASS
  80         depends on SHARP_LOCOMO
  81         help
  82           This option enables support for the LEDs on Sharp Locomo.
  83           Zaurus models SL-5500 and SL-5600.
  84
  85 config LEDS_MIKROTIK_RB532
  86         tristate "LED Support for Mikrotik Routerboard 532"
  87         depends on LEDS_CLASS
  88         depends on MIKROTIK_RB532
  89         help
  90           This option enables support for the so called "User LED" of
  91           Mikrotik's Routerboard 532.
  92
  93 config LEDS_S3C24XX
  94         tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  95         depends on LEDS_CLASS
  96         depends on ARCH_S3C24XX
  97         help
  98           This option enables support for LEDs connected to GPIO lines
  99           on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
 100
 101 config LEDS_NET48XX
 102         tristate "LED Support for Soekris net48xx series Error LED"
 103         depends on LEDS_CLASS
 104         depends on SCx200_GPIO
 105         help
 106           This option enables support for the Soekris net4801 and net4826 error
 107           LED.
 108
 109 config LEDS_FSG
 110         tristate "LED Support for the Freecom FSG-3"
 111         depends on LEDS_CLASS
 112         depends on MACH_FSG
 113         help
 114           This option enables support for the LEDs on the Freecom FSG-3.
 115
 116 config LEDS_WRAP
 117         tristate "LED Support for the WRAP series LEDs"
 118         depends on LEDS_CLASS
 119         depends on SCx200_GPIO
 120         help
 121           This option enables support for the PCEngines WRAP programmable LEDs.
 122
 123 config LEDS_COBALT_QUBE
 124         tristate "LED Support for the Cobalt Qube series front LED"
 125         depends on LEDS_CLASS
 126         depends on MIPS_COBALT
 127         help
 128           This option enables support for the front LED on Cobalt Qube series
 129
 130 config LEDS_COBALT_RAQ
 131         bool "LED Support for the Cobalt Raq series"
 132         depends on LEDS_CLASS=y && MIPS_COBALT
 133         select LEDS_TRIGGERS
 134         help
 135           This option enables support for the Cobalt Raq series LEDs.
 136
 137 config LEDS_SUNFIRE
 138         tristate "LED support for SunFire servers."
 139         depends on LEDS_CLASS
 140         depends on SPARC64
 141         select LEDS_TRIGGERS
 142         help
 143           This option enables support for the Left, Middle, and Right
 144           LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
 145
 146 config LEDS_HP6XX
 147         tristate "LED Support for the HP Jornada 6xx"
 148         depends on LEDS_CLASS
 149         depends on SH_HP6XX
 150         help
 151           This option enables LED support for the handheld
 152           HP Jornada 620/660/680/690.
 153
 154 config LEDS_PCA9532
 155         tristate "LED driver for PCA9532 dimmer"
 156         depends on LEDS_CLASS
 157         depends on I2C && INPUT
 158         help
 159           This option enables support for NXP pca9532
 160           LED controller. It is generally only useful
 161           as a platform driver
 162
 163 config LEDS_PCA9532_GPIO
 164         bool "Enable GPIO support for PCA9532"
 165         depends on LEDS_PCA9532
 166         depends on GPIOLIB
 167         help
 168           Allow unused pins on PCA9532 to be used as gpio.
 169
 170           To use a pin as gpio pca9532_type in pca9532_platform data needs to
 171           set to PCA9532_TYPE_GPIO.
 172
 173 config LEDS_GPIO
 174         tristate "LED Support for GPIO connected LEDs"
 175         depends on LEDS_CLASS
 176         depends on GENERIC_GPIO
 177         help
 178           This option enables support for the LEDs connected to GPIO
 179           outputs. To be useful the particular board must have LEDs
 180           and they must be connected to the GPIO lines.  The LEDs must be
 181           defined as platform devices and/or OpenFirmware platform devices.
 182           The code to use these bindings can be selected below.
 183
 184 config LEDS_LP3944
 185         tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
 186         depends on LEDS_CLASS
 187         depends on I2C
 188         help
 189           This option enables support for LEDs connected to the National
 190           Semiconductor LP3944 Lighting Management Unit (LMU) also known as
 191           Fun Light Chip.
 192
 193           To compile this driver as a module, choose M here: the
 194           module will be called leds-lp3944.
 195
 196 config LEDS_LP55XX_COMMON
 197         tristate "Common Driver for TI/National LP5521 and LP5523/55231"
 198         depends on LEDS_LP5521 || LEDS_LP5523
 199         select FW_LOADER
 200         help
 201           This option supports common operations for LP5521 and LP5523/55231
 202           devices.
 203
 204 config LEDS_LP5521
 205         tristate "LED Support for N.S. LP5521 LED driver chip"
 206         depends on LEDS_CLASS && I2C
 207         select LEDS_LP55XX_COMMON
 208         help
 209           If you say yes here you get support for the National Semiconductor
 210           LP5521 LED driver. It is 3 channel chip with programmable engines.
 211           Driver provides direct control via LED class and interface for
 212           programming the engines.
 213
 214 config LEDS_LP5523
 215         tristate "LED Support for TI/National LP5523/55231 LED driver chip"
 216         depends on LEDS_CLASS && I2C
 217         select LEDS_LP55XX_COMMON
 218         help
 219           If you say yes here you get support for TI/National Semiconductor
 220           LP5523/55231 LED driver.
 221           It is 9 channel chip with programmable engines.
 222           Driver provides direct control via LED class and interface for
 223           programming the engines.
 224
 225 config LEDS_LP8788
 226         tristate "LED support for the TI LP8788 PMIC"
 227         depends on LEDS_CLASS
 228         depends on MFD_LP8788
 229         help
 230           This option enables support for the Keyboard LEDs on the LP8788 PMIC.
 231
 232 config 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
 263 config 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
 272 config LEDS_PCA9633
 273         tristate "LED support for PCA9633 I2C chip"
 274         depends on LEDS_CLASS
 275         depends on I2C
 276         help
 277           This option enables support for LEDs connected to the PCA9633
 278           LED driver chip accessed via the I2C bus.
 279
 280 config LEDS_WM831X_STATUS
 281         tristate "LED support for status LEDs on WM831x PMICs"
 282         depends on LEDS_CLASS
 283         depends on MFD_WM831X
 284         help
 285           This option enables support for the status LEDs of the WM831x
 286           series of PMICs.
 287
 288 config LEDS_WM8350
 289         tristate "LED Support for WM8350 AudioPlus PMIC"
 290         depends on LEDS_CLASS
 291         depends on MFD_WM8350
 292         help
 293           This option enables support for LEDs driven by the Wolfson
 294           Microelectronics WM8350 AudioPlus PMIC.
 295
 296 config LEDS_DA903X
 297         tristate "LED Support for DA9030/DA9034 PMIC"
 298         depends on LEDS_CLASS
 299         depends on PMIC_DA903X
 300         help
 301           This option enables support for on-chip LED drivers found
 302           on Dialog Semiconductor DA9030/DA9034 PMICs.
 303
 304 config LEDS_DA9052
 305         tristate "Dialog DA9052/DA9053 LEDS"
 306         depends on LEDS_CLASS
 307         depends on PMIC_DA9052
 308         help
 309           This option enables support for on-chip LED drivers found
 310           on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
 311
 312 config LEDS_DAC124S085
 313         tristate "LED Support for DAC124S085 SPI DAC"
 314         depends on LEDS_CLASS
 315         depends on SPI
 316         help
 317           This option enables support for DAC124S085 SPI DAC from NatSemi,
 318           which can be used to control up to four LEDs.
 319
 320 config LEDS_PWM
 321         tristate "PWM driven LED Support"
 322         depends on LEDS_CLASS
 323         depends on PWM
 324         help
 325           This option enables support for pwm driven LEDs
 326
 327 config LEDS_REGULATOR
 328         tristate "REGULATOR driven LED support"
 329         depends on LEDS_CLASS
 330         depends on REGULATOR
 331         help
 332           This option enables support for regulator driven LEDs.
 333
 334 config LEDS_BD2802
 335         tristate "LED driver for BD2802 RGB LED"
 336         depends on LEDS_CLASS
 337         depends on I2C
 338         help
 339           This option enables support for BD2802GU RGB LED driver chips
 340           accessed via the I2C bus.
 341
 342 config LEDS_INTEL_SS4200
 343         tristate "LED driver for Intel NAS SS4200 series"
 344         depends on LEDS_CLASS
 345         depends on PCI && DMI
 346         help
 347           This option enables support for the Intel SS4200 series of
 348           Network Attached Storage servers.  You may control the hard
 349           drive or power LEDs on the front panel.  Using this driver
 350           can stop the front LED from blinking after startup.
 351
 352 config LEDS_LT3593
 353         tristate "LED driver for LT3593 controllers"
 354         depends on LEDS_CLASS
 355         depends on GENERIC_GPIO
 356         help
 357           This option enables support for LEDs driven by a Linear Technology
 358           LT3593 controller. This controller uses a special one-wire pulse
 359           coding protocol to set the brightness.
 360
 361 config LEDS_ADP5520
 362         tristate "LED Support for ADP5520/ADP5501 PMIC"
 363         depends on LEDS_CLASS
 364         depends on PMIC_ADP5520
 365         help
 366           This option enables support for on-chip LED drivers found
 367           on Analog Devices ADP5520/ADP5501 PMICs.
 368
 369           To compile this driver as a module, choose M here: the module will
 370           be called leds-adp5520.
 371
 372 config LEDS_DELL_NETBOOKS
 373         tristate "External LED on Dell Business Netbooks"
 374         depends on LEDS_CLASS
 375         depends on X86 && ACPI_WMI
 376         help
 377           This adds support for the Latitude 2100 and similar
 378           notebooks that have an external LED.
 379
 380 config LEDS_MC13783
 381         tristate "LED Support for MC13783 PMIC"
 382         depends on LEDS_CLASS
 383         depends on MFD_MC13783
 384         help
 385           This option enable support for on-chip LED drivers found
 386           on Freescale Semiconductor MC13783 PMIC.
 387
 388 config LEDS_NS2
 389         tristate "LED support for Network Space v2 GPIO LEDs"
 390         depends on LEDS_CLASS
 391         depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
 392                    MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2 || \
 393                    MACH_NETSPACE_V2_DT || MACH_INETSPACE_V2_DT || \
 394                    MACH_NETSPACE_MAX_V2_DT || MACH_NETSPACE_MINI_V2_DT
 395         default y
 396         help
 397           This option enable support for the dual-GPIO LED found on the
 398           Network Space v2 board (and parents). This include Internet Space v2,
 399           Network Space (Max) v2 and d2 Network v2 boards.
 400
 401 config LEDS_NETXBIG
 402         tristate "LED support for Big Network series LEDs"
 403         depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
 404         depends on LEDS_CLASS
 405         default y
 406         help
 407           This option enable support for LEDs found on the LaCie 2Big
 408           and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
 409           controlled through a GPIO extension bus.
 410
 411 config LEDS_ASIC3
 412         bool "LED support for the HTC ASIC3"
 413         depends on LEDS_CLASS=y
 414         depends on MFD_ASIC3
 415         default y
 416         help
 417           This option enables support for the LEDs on the HTC ASIC3. The HTC
 418           ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
 419           cannot be used. This driver supports hardware blinking with an on+off
 420           period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
 421
 422 config LEDS_RENESAS_TPU
 423         bool "LED support for Renesas TPU"
 424         depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO
 425         help
 426           This option enables build of the LED TPU platform driver,
 427           suitable to drive any TPU channel on newer Renesas SoCs.
 428           The driver controls the GPIO pin connected to the LED via
 429           the GPIO framework and expects the LED to be connected to
 430           a pin that can be driven in both GPIO mode and using TPU
 431           pin function. The latter to support brightness control.
 432           Brightness control is supported but hardware blinking is not.
 433
 434 config LEDS_TCA6507
 435         tristate "LED Support for TCA6507 I2C chip"
 436         depends on LEDS_CLASS && I2C
 437         help
 438           This option enables support for LEDs connected to TC6507
 439           LED driver chips accessed via the I2C bus.
 440           Driver support brightness control and hardware-assisted blinking.
 441
 442 config LEDS_MAX8997
 443         tristate "LED support for MAX8997 PMIC"
 444         depends on LEDS_CLASS && MFD_MAX8997
 445         help
 446           This option enables support for on-chip LED drivers on
 447           MAXIM MAX8997 PMIC.
 448
 449 config LEDS_LM355x
 450         tristate "LED support for LM355x Chips, LM3554 and LM3556"
 451         depends on LEDS_CLASS && I2C
 452         select REGMAP_I2C
 453         help
 454           This option enables support for LEDs connected to LM355x.
 455           LM355x includes Torch, Flash and Indicator functions.
 456
 457 config LEDS_OT200
 458         tristate "LED support for the Bachmann OT200"
 459         depends on LEDS_CLASS && HAS_IOMEM
 460         help
 461           This option enables support for the LEDs on the Bachmann OT200.
 462           Say Y to enable LEDs on the Bachmann OT200.
 463
 464 config LEDS_BLINKM
 465         tristate "LED support for the BlinkM I2C RGB LED"
 466         depends on LEDS_CLASS
 467         depends on I2C
 468         help
 469           This option enables support for the BlinkM RGB LED connected
 470           through I2C. Say Y to enable support for the BlinkM LED.
 471
 472 config LEDS_TRIGGERS
 473         bool "LED Trigger support"
 474         depends on LEDS_CLASS
 475         help
 476           This option enables trigger support for the leds class.
 477           These triggers allow kernel events to drive the LEDs and can
 478           be configured via sysfs. If unsure, say Y.
 479
 480 comment "LED Triggers"
 481
 482 config LEDS_TRIGGER_TIMER
 483         tristate "LED Timer Trigger"
 484         depends on LEDS_TRIGGERS
 485         help
 486           This allows LEDs to be controlled by a programmable timer
 487           via sysfs. Some LED hardware can be programmed to start
 488           blinking the LED without any further software interaction.
 489           For more details read Documentation/leds/leds-class.txt.
 490
 491           If unsure, say Y.
 492
 493 config LEDS_TRIGGER_ONESHOT
 494         tristate "LED One-shot Trigger"
 495         depends on LEDS_TRIGGERS
 496         help
 497           This allows LEDs to blink in one-shot pulses with parameters
 498           controlled via sysfs.  It's useful to notify the user on
 499           sporadic events, when there are no clear begin and end trap points,
 500           or on dense events, where this blinks the LED at constant rate if
 501           rearmed continuously.
 502
 503           It also shows how to use the led_blink_set_oneshot() function.
 504
 505           If unsure, say Y.
 506
 507 config LEDS_TRIGGER_IDE_DISK
 508         bool "LED IDE Disk Trigger"
 509         depends on IDE_GD_ATA
 510         depends on LEDS_TRIGGERS
 511         help
 512           This allows LEDs to be controlled by IDE disk activity.
 513           If unsure, say Y.
 514
 515 config LEDS_TRIGGER_HEARTBEAT
 516         tristate "LED Heartbeat Trigger"
 517         depends on LEDS_TRIGGERS
 518         help
 519           This allows LEDs to be controlled by a CPU load average.
 520           The flash frequency is a hyperbolic function of the 1-minute
 521           load average.
 522           If unsure, say Y.
 523
 524 config LEDS_TRIGGER_BACKLIGHT
 525         tristate "LED backlight Trigger"
 526         depends on LEDS_TRIGGERS
 527         help
 528           This allows LEDs to be controlled as a backlight device: they
 529           turn off and on when the display is blanked and unblanked.
 530
 531           If unsure, say N.
 532
 533 config LEDS_TRIGGER_CPU
 534         bool "LED CPU Trigger"
 535         depends on LEDS_TRIGGERS
 536         help
 537           This allows LEDs to be controlled by active CPUs. This shows
 538           the active CPUs across an array of LEDs so you can see which
 539           CPUs are active on the system at any given moment.
 540
 541           If unsure, say N.
 542
 543 config LEDS_TRIGGER_GPIO
 544         tristate "LED GPIO Trigger"
 545         depends on LEDS_TRIGGERS
 546         depends on GPIOLIB
 547         help
 548           This allows LEDs to be controlled by gpio events. It's good
 549           when using gpios as switches and triggering the needed LEDs
 550           from there. One use case is n810's keypad LEDs that could
 551           be triggered by this trigger when user slides up to show
 552           keypad.
 553
 554           If unsure, say N.
 555
 556 config LEDS_TRIGGER_DEFAULT_ON
 557         tristate "LED Default ON Trigger"
 558         depends on LEDS_TRIGGERS
 559         help
 560           This allows LEDs to be initialised in the ON state.
 561           If unsure, say Y.
 562
 563 comment "iptables trigger is under Netfilter config (LED target)"
 564         depends on LEDS_TRIGGERS
 565
 566 config LEDS_TRIGGER_TRANSIENT
 567         tristate "LED Transient Trigger"
 568         depends on LEDS_TRIGGERS
 569         help
 570           This allows one time activation of a transient state on
 571           GPIO/PWM based hardware.
 572           If unsure, say Y.
 573
 574 endif # NEW_LEDS