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         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
  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_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
  61 config 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
  69 config 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
  77 config 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
  84 config 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
  92 config 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
 102 config 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
 109 config 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
 116 config 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
 123 config 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
 130 config 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
 139 config 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
 147 config 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
 156 config 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
 166 config 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
 177 config 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
 189 config 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
 198 config 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
 207 config 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
 238 config 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
 247 config 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
 255 config 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
 263 config 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
 271 config 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
 279 config 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
 286 config 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
 293 config 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
 301 config 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
 311 config 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
 320 config 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
 331 config 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
 339 config 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
 347 config 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 || \
 351                    MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2
 352         default y
 353         help
 354           This option enable support for the dual-GPIO LED found on the
 355           Network Space v2 board (and parents). This include Internet Space v2,
 356           Network Space (Max) v2 and d2 Network v2 boards.
 357
 358 config LEDS_NETXBIG
 359         tristate "LED support for Big Network series LEDs"
 360         depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
 361         depends on LEDS_CLASS
 362         default y
 363         help
 364           This option enable support for LEDs found on the LaCie 2Big
 365           and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
 366           controlled through a GPIO extension bus.
 367
 368 config LEDS_ASIC3
 369         bool "LED support for the HTC ASIC3"
 370         depends on LEDS_CLASS
 371         depends on MFD_ASIC3
 372         default y
 373         help
 374           This option enables support for the LEDs on the HTC ASIC3. The HTC
 375           ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
 376           cannot be used. This driver supports hardware blinking with an on+off
 377           period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
 378
 379 config LEDS_RENESAS_TPU
 380         bool "LED support for Renesas TPU"
 381         depends on LEDS_CLASS && HAVE_CLK && GENERIC_GPIO
 382         help
 383           This option enables build of the LED TPU platform driver,
 384           suitable to drive any TPU channel on newer Renesas SoCs.
 385           The driver controls the GPIO pin connected to the LED via
 386           the GPIO framework and expects the LED to be connected to
 387           a pin that can be driven in both GPIO mode and using TPU
 388           pin function. The latter to support brightness control.
 389           Brightness control is supported but hardware blinking is not.
 390
 391 config LEDS_TCA6507
 392         tristate "LED Support for TCA6507 I2C chip"
 393         depends on LEDS_CLASS && I2C
 394         help
 395           This option enables support for LEDs connected to TC6507
 396           LED driver chips accessed via the I2C bus.
 397           Driver support brightness control and hardware-assisted blinking.
 398
 399 config LEDS_MAX8997
 400         tristate "LED support for MAX8997 PMIC"
 401         depends on LEDS_CLASS && MFD_MAX8997
 402         help
 403           This option enables support for on-chip LED drivers on
 404           MAXIM MAX8997 PMIC.
 405
 406 config LEDS_OT200
 407         tristate "LED support for the Bachmann OT200"
 408         depends on LEDS_CLASS && HAS_IOMEM
 409         help
 410           This option enables support for the LEDs on the Bachmann OT200.
 411           Say Y to enable LEDs on the Bachmann OT200.
 412
 413 config LEDS_TRIGGERS
 414         bool "LED Trigger support"
 415         depends on LEDS_CLASS
 416         help
 417           This option enables trigger support for the leds class.
 418           These triggers allow kernel events to drive the LEDs and can
 419           be configured via sysfs. If unsure, say Y.
 420
 421 comment "LED Triggers"
 422
 423 config LEDS_TRIGGER_TIMER
 424         tristate "LED Timer Trigger"
 425         depends on LEDS_TRIGGERS
 426         help
 427           This allows LEDs to be controlled by a programmable timer
 428           via sysfs. Some LED hardware can be programmed to start
 429           blinking the LED without any further software interaction.
 430           For more details read Documentation/leds/leds-class.txt.
 431
 432           If unsure, say Y.
 433
 434 config LEDS_TRIGGER_IDE_DISK
 435         bool "LED IDE Disk Trigger"
 436         depends on IDE_GD_ATA
 437         depends on LEDS_TRIGGERS
 438         help
 439           This allows LEDs to be controlled by IDE disk activity.
 440           If unsure, say Y.
 441
 442 config LEDS_TRIGGER_HEARTBEAT
 443         tristate "LED Heartbeat Trigger"
 444         depends on LEDS_TRIGGERS
 445         help
 446           This allows LEDs to be controlled by a CPU load average.
 447           The flash frequency is a hyperbolic function of the 1-minute
 448           load average.
 449           If unsure, say Y.
 450
 451 config LEDS_TRIGGER_BACKLIGHT
 452         tristate "LED backlight Trigger"
 453         depends on LEDS_TRIGGERS
 454         help
 455           This allows LEDs to be controlled as a backlight device: they
 456           turn off and on when the display is blanked and unblanked.
 457
 458           If unsure, say N.
 459
 460 config LEDS_TRIGGER_GPIO
 461         tristate "LED GPIO Trigger"
 462         depends on LEDS_TRIGGERS
 463         depends on GPIOLIB
 464         help
 465           This allows LEDs to be controlled by gpio events. It's good
 466           when using gpios as switches and triggering the needed LEDs
 467           from there. One use case is n810's keypad LEDs that could
 468           be triggered by this trigger when user slides up to show
 469           keypad.
 470
 471           If unsure, say N.
 472
 473 config LEDS_TRIGGER_DEFAULT_ON
 474         tristate "LED Default ON Trigger"
 475         depends on LEDS_TRIGGERS
 476         help
 477           This allows LEDs to be initialised in the ON state.
 478           If unsure, say Y.
 479
 480 comment "iptables trigger is under Netfilter config (LED target)"
 481         depends on LEDS_TRIGGERS
 482
 483 endif # NEW_LEDS