LXR linux/drivers/leds/Kconfig

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