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.
   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).
  14          This is not related to standard keyboard LEDs which are controlled
  15          via the input system.
  17if NEW_LEDS
  19config 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.
  25comment "LED drivers"
  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.
  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.
  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.
  53config 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.
  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.
  66config 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.
  77config 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.
  85config 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.
  93config 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.
 101config 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.
 109config 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.
 116config 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.
 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
 130config 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.
 137config 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.
 146config 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.
 154config LEDS_PCA9532
 155        tristate "LED driver for PCA9532 dimmer"
 156        depends on LEDS_CLASS
 157        depends on I2C && INPUT && EXPERIMENTAL
 158        help
 159          This option enables support for NXP pca9532
 160          LED controller. It is generally only useful
 161          as a platform driver
 163config 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.
 170          To use a pin as gpio pca9532_type in pca9532_platform data needs to
 171          set to PCA9532_TYPE_GPIO.
 173config 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.
 184config 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.
 193          To compile this driver as a module, choose M here: the
 194          module will be called leds-lp3944.
 196config LEDS_LP5521
 197        tristate "LED Support for N.S. LP5521 LED driver chip"
 198        depends on LEDS_CLASS && I2C
 199        help
 200          If you say yes here you get support for the National Semiconductor
 201          LP5521 LED driver. It is 3 channel chip with programmable engines.
 202          Driver provides direct control via LED class and interface for
 203          programming the engines.
 205config LEDS_LP5523
 206        tristate "LED Support for TI/National LP5523/55231 LED driver chip"
 207        depends on LEDS_CLASS && I2C
 208        help
 209          If you say yes here you get support for TI/National Semiconductor
 210          LP5523/55231 LED driver.
 211          It is 9 channel chip with programmable engines.
 212          Driver provides direct control via LED class and interface for
 213          programming the engines.
 215config LEDS_LP8788
 216        tristate "LED support for the TI LP8788 PMIC"
 217        depends on LEDS_CLASS
 218        depends on MFD_LP8788
 219        help
 220          This option enables support for the Keyboard LEDs on the LP8788 PMIC.
 222config LEDS_CLEVO_MAIL
 223        tristate "Mail LED on Clevo notebook"
 224        depends on LEDS_CLASS
 225        depends on X86 && SERIO_I8042 && DMI
 226        help
 227          This driver makes the mail LED accessible from userspace
 228          programs through the leds subsystem. This LED have three
 229          known mode: off, blink at 0.5Hz and blink at 1Hz.
 231          The driver supports two kinds of interface: using ledtrig-timer
 232          or through /sys/class/leds/clevo::mail/brightness. As this LED
 233          cannot change it's brightness it blinks instead. The brightness
 234          value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
 235          blink at 1Hz.
 237          This module can drive the mail LED for the following notebooks:
 239                Clevo D400P
 240                Clevo D410J
 241                Clevo D410V
 242                Clevo D400V/D470V (not tested, but might work)
 243                Clevo M540N
 244                Clevo M5x0N (not tested, but might work)
 245                Positivo Mobile (Clevo M5x0V)
 247          If your model is not listed here you can try the "nodetect"
 248          module parameter.
 250          To compile this driver as a module, choose M here: the
 251          module will be called leds-clevo-mail.
 253config LEDS_PCA955X
 254        tristate "LED Support for PCA955x I2C chips"
 255        depends on LEDS_CLASS
 256        depends on I2C
 257        help
 258          This option enables support for LEDs connected to PCA955x
 259          LED driver chips accessed via the I2C bus.  Supported
 260          devices include PCA9550, PCA9551, PCA9552, and PCA9553.
 262config LEDS_PCA9633
 263        tristate "LED support for PCA9633 I2C chip"
 264        depends on LEDS_CLASS
 265        depends on I2C
 266        help
 267          This option enables support for LEDs connected to the PCA9633
 268          LED driver chip accessed via the I2C bus.
 270config LEDS_WM831X_STATUS
 271        tristate "LED support for status LEDs on WM831x PMICs"
 272        depends on LEDS_CLASS
 273        depends on MFD_WM831X
 274        help
 275          This option enables support for the status LEDs of the WM831x
 276          series of PMICs.
 278config LEDS_WM8350
 279        tristate "LED Support for WM8350 AudioPlus PMIC"
 280        depends on LEDS_CLASS
 281        depends on MFD_WM8350
 282        help
 283          This option enables support for LEDs driven by the Wolfson
 284          Microelectronics WM8350 AudioPlus PMIC.
 286config LEDS_DA903X
 287        tristate "LED Support for DA9030/DA9034 PMIC"
 288        depends on LEDS_CLASS
 289        depends on PMIC_DA903X
 290        help
 291          This option enables support for on-chip LED drivers found
 292          on Dialog Semiconductor DA9030/DA9034 PMICs.
 294config LEDS_DA9052
 295        tristate "Dialog DA9052/DA9053 LEDS"
 296        depends on LEDS_CLASS
 297        depends on PMIC_DA9052
 298        help
 299          This option enables support for on-chip LED drivers found
 300          on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
 302config LEDS_DAC124S085
 303        tristate "LED Support for DAC124S085 SPI DAC"
 304        depends on LEDS_CLASS
 305        depends on SPI
 306        help
 307          This option enables support for DAC124S085 SPI DAC from NatSemi,
 308          which can be used to control up to four LEDs.
 310config LEDS_PWM
 311        tristate "PWM driven LED Support"
 312        depends on LEDS_CLASS
 313        depends on HAVE_PWM
 314        help
 315          This option enables support for pwm driven LEDs
 318        tristate "REGULATOR driven LED support"
 319        depends on LEDS_CLASS
 320        depends on REGULATOR
 321        help
 322          This option enables support for regulator driven LEDs.
 324config LEDS_BD2802
 325        tristate "LED driver for BD2802 RGB LED"
 326        depends on LEDS_CLASS
 327        depends on I2C
 328        help
 329          This option enables support for BD2802GU RGB LED driver chips
 330          accessed via the I2C bus.
 332config LEDS_INTEL_SS4200
 333        tristate "LED driver for Intel NAS SS4200 series"
 334        depends on LEDS_CLASS
 335        depends on PCI && DMI
 336        help
 337          This option enables support for the Intel SS4200 series of
 338          Network Attached Storage servers.  You may control the hard
 339          drive or power LEDs on the front panel.  Using this driver
 340          can stop the front LED from blinking after startup.
 342config LEDS_LT3593
 343        tristate "LED driver for LT3593 controllers"
 344        depends on LEDS_CLASS
 345        depends on GENERIC_GPIO
 346        help
 347          This option enables support for LEDs driven by a Linear Technology
 348          LT3593 controller. This controller uses a special one-wire pulse
 349          coding protocol to set the brightness.
 351config LEDS_ADP5520
 352        tristate "LED Support for ADP5520/ADP5501 PMIC"
 353        depends on LEDS_CLASS
 354        depends on PMIC_ADP5520
 355        help
 356          This option enables support for on-chip LED drivers found
 357          on Analog Devices ADP5520/ADP5501 PMICs.
 359          To compile this driver as a module, choose M here: the module will
 360          be called leds-adp5520.
 363        tristate "External LED on Dell Business Netbooks"
 364        depends on LEDS_CLASS
 365        depends on X86 && ACPI_WMI
 366        help
 367          This adds support for the Latitude 2100 and similar
 368          notebooks that have an external LED.
 370config LEDS_MC13783
 371        tristate "LED Support for MC13783 PMIC"
 372        depends on LEDS_CLASS
 373        depends on MFD_MC13783
 374        help
 375          This option enable support for on-chip LED drivers found
 376          on Freescale Semiconductor MC13783 PMIC.
 378config LEDS_NS2
 379        tristate "LED support for Network Space v2 GPIO LEDs"
 380        depends on LEDS_CLASS
 381        depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
 382                   MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2
 383        default y
 384        help
 385          This option enable support for the dual-GPIO LED found on the
 386          Network Space v2 board (and parents). This include Internet Space v2,
 387          Network Space (Max) v2 and d2 Network v2 boards.
 389config LEDS_NETXBIG
 390        tristate "LED support for Big Network series LEDs"
 391        depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
 392        depends on LEDS_CLASS
 393        default y
 394        help
 395          This option enable support for LEDs found on the LaCie 2Big
 396          and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
 397          controlled through a GPIO extension bus.
 399config LEDS_ASIC3
 400        bool "LED support for the HTC ASIC3"
 401        depends on LEDS_CLASS=y
 402        depends on MFD_ASIC3
 403        default y
 404        help
 405          This option enables support for the LEDs on the HTC ASIC3. The HTC
 406          ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
 407          cannot be used. This driver supports hardware blinking with an on+off
 408          period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
 411        bool "LED support for Renesas TPU"
 412        depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO
 413        help
 414          This option enables build of the LED TPU platform driver,
 415          suitable to drive any TPU channel on newer Renesas SoCs.
 416          The driver controls the GPIO pin connected to the LED via
 417          the GPIO framework and expects the LED to be connected to
 418          a pin that can be driven in both GPIO mode and using TPU
 419          pin function. The latter to support brightness control.
 420          Brightness control is supported but hardware blinking is not.
 422config LEDS_TCA6507
 423        tristate "LED Support for TCA6507 I2C chip"
 424        depends on LEDS_CLASS && I2C
 425        help
 426          This option enables support for LEDs connected to TC6507
 427          LED driver chips accessed via the I2C bus.
 428          Driver support brightness control and hardware-assisted blinking.
 430config LEDS_MAX8997
 431        tristate "LED support for MAX8997 PMIC"
 432        depends on LEDS_CLASS && MFD_MAX8997
 433        help
 434          This option enables support for on-chip LED drivers on
 435          MAXIM MAX8997 PMIC.
 437config LEDS_LM355x
 438        tristate "LED support for LM355x Chips, LM3554 and LM3556"
 439        depends on LEDS_CLASS && I2C
 440        select REGMAP_I2C
 441        help
 442          This option enables support for LEDs connected to LM355x.
 443          LM355x includes Torch, Flash and Indicator functions.
 445config LEDS_OT200
 446        tristate "LED support for the Bachmann OT200"
 447        depends on LEDS_CLASS && HAS_IOMEM
 448        help
 449          This option enables support for the LEDs on the Bachmann OT200.
 450          Say Y to enable LEDs on the Bachmann OT200.
 452config LEDS_BLINKM
 453        tristate "LED support for the BlinkM I2C RGB LED"
 454        depends on LEDS_CLASS
 455        depends on I2C
 456        help
 457          This option enables support for the BlinkM RGB LED connected
 458          through I2C. Say Y to enable support for the BlinkM LED.
 460config LEDS_TRIGGERS
 461        bool "LED Trigger support"
 462        depends on LEDS_CLASS
 463        help
 464          This option enables trigger support for the leds class.
 465          These triggers allow kernel events to drive the LEDs and can
 466          be configured via sysfs. If unsure, say Y.
 468comment "LED Triggers"
 471        tristate "LED Timer Trigger"
 472        depends on LEDS_TRIGGERS
 473        help
 474          This allows LEDs to be controlled by a programmable timer
 475          via sysfs. Some LED hardware can be programmed to start
 476          blinking the LED without any further software interaction.
 477          For more details read Documentation/leds/leds-class.txt.
 479          If unsure, say Y.
 482        tristate "LED One-shot Trigger"
 483        depends on LEDS_TRIGGERS
 484        help
 485          This allows LEDs to blink in one-shot pulses with parameters
 486          controlled via sysfs.  It's useful to notify the user on
 487          sporadic events, when there are no clear begin and end trap points,
 488          or on dense events, where this blinks the LED at constant rate if
 489          rearmed continuously.
 491          It also shows how to use the led_blink_set_oneshot() function.
 493          If unsure, say Y.
 496        bool "LED IDE Disk Trigger"
 497        depends on IDE_GD_ATA
 498        depends on LEDS_TRIGGERS
 499        help
 500          This allows LEDs to be controlled by IDE disk activity.
 501          If unsure, say Y.
 504        tristate "LED Heartbeat Trigger"
 505        depends on LEDS_TRIGGERS
 506        help
 507          This allows LEDs to be controlled by a CPU load average.
 508          The flash frequency is a hyperbolic function of the 1-minute
 509          load average.
 510          If unsure, say Y.
 513        tristate "LED backlight Trigger"
 514        depends on LEDS_TRIGGERS
 515        help
 516          This allows LEDs to be controlled as a backlight device: they
 517          turn off and on when the display is blanked and unblanked.
 519          If unsure, say N.
 522        bool "LED CPU Trigger"
 523        depends on LEDS_TRIGGERS
 524        help
 525          This allows LEDs to be controlled by active CPUs. This shows
 526          the active CPUs across an array of LEDs so you can see which
 527          CPUs are active on the system at any given moment.
 529          If unsure, say N.
 532        tristate "LED GPIO Trigger"
 533        depends on LEDS_TRIGGERS
 534        depends on GPIOLIB
 535        help
 536          This allows LEDs to be controlled by gpio events. It's good
 537          when using gpios as switches and triggering the needed LEDs
 538          from there. One use case is n810's keypad LEDs that could
 539          be triggered by this trigger when user slides up to show
 540          keypad.
 542          If unsure, say N.
 545        tristate "LED Default ON Trigger"
 546        depends on LEDS_TRIGGERS
 547        help
 548          This allows LEDs to be initialised in the ON state.
 549          If unsure, say Y.
 551comment "iptables trigger is under Netfilter config (LED target)"
 552        depends on LEDS_TRIGGERS
 555        tristate "LED Transient Trigger"
 556        depends on LEDS_TRIGGERS
 557        help
 558          This allows one time activation of a transient state on
 559          GPIO/PWM based hardware.
 560          If unsure, say Y.
 562endif # NEW_LEDS
 563 kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.