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