drivers/leds/Kconfig

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