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 if NEW_LEDS
  11
  12 config LEDS_CLASS
  13         tristate "LED Class Support"
  14         help
  15           This option enables the led sysfs class in /sys/class/leds.  You'll
  16           need this to do anything useful with LEDs.  If unsure, say N.
  17
  18 comment "LED drivers"
  19
  20 config LEDS_ATMEL_PWM
  21         tristate "LED Support using Atmel PWM outputs"
  22         depends on LEDS_CLASS && ATMEL_PWM
  23         help
  24           This option enables support for LEDs driven using outputs
  25           of the dedicated PWM controller found on newer Atmel SOCs.
  26
  27 config LEDS_LOCOMO
  28         tristate "LED Support for Locomo device"
  29         depends on LEDS_CLASS && SHARP_LOCOMO
  30         help
  31           This option enables support for the LEDs on Sharp Locomo.
  32           Zaurus models SL-5500 and SL-5600.
  33
  34 config LEDS_MIKROTIK_RB532
  35         tristate "LED Support for Mikrotik Routerboard 532"
  36         depends on LEDS_CLASS && MIKROTIK_RB532
  37         help
  38           This option enables support for the so called "User LED" of
  39           Mikrotik's Routerboard 532.
  40
  41 config LEDS_S3C24XX
  42         tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  43         depends on LEDS_CLASS && ARCH_S3C2410
  44         help
  45           This option enables support for LEDs connected to GPIO lines
  46           on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  47
  48 config LEDS_AMS_DELTA
  49         tristate "LED Support for the Amstrad Delta (E3)"
  50         depends on LEDS_CLASS && MACH_AMS_DELTA
  51         help
  52           This option enables support for the LEDs on Amstrad Delta (E3).
  53
  54 config LEDS_NET48XX
  55         tristate "LED Support for Soekris net48xx series Error LED"
  56         depends on LEDS_CLASS && SCx200_GPIO
  57         help
  58           This option enables support for the Soekris net4801 and net4826 error
  59           LED.
  60
  61 config LEDS_FSG
  62         tristate "LED Support for the Freecom FSG-3"
  63         depends on LEDS_CLASS && MACH_FSG
  64         help
  65           This option enables support for the LEDs on the Freecom FSG-3.
  66
  67 config LEDS_WRAP
  68         tristate "LED Support for the WRAP series LEDs"
  69         depends on LEDS_CLASS && SCx200_GPIO
  70         help
  71           This option enables support for the PCEngines WRAP programmable LEDs.
  72
  73 config LEDS_ALIX2
  74         tristate "LED Support for ALIX.2 and ALIX.3 series"
  75         depends on LEDS_CLASS && X86 && EXPERIMENTAL
  76         help
  77           This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
  78           You have to set leds-alix2.force=1 for boards with Award BIOS.
  79
  80 config LEDS_H1940
  81         tristate "LED Support for iPAQ H1940 device"
  82         depends on LEDS_CLASS && ARCH_H1940
  83         help
  84           This option enables support for the LEDs on the h1940.
  85
  86 config LEDS_COBALT_QUBE
  87         tristate "LED Support for the Cobalt Qube series front LED"
  88         depends on LEDS_CLASS && MIPS_COBALT
  89         help
  90           This option enables support for the front LED on Cobalt Qube series
  91
  92 config LEDS_COBALT_RAQ
  93         bool "LED Support for the Cobalt Raq series"
  94         depends on LEDS_CLASS=y && MIPS_COBALT
  95         select LEDS_TRIGGERS
  96         help
  97           This option enables support for the Cobalt Raq series LEDs.
  98
  99 config LEDS_SUNFIRE
 100         tristate "LED support for SunFire servers."
 101         depends on LEDS_CLASS && SPARC64
 102         select LEDS_TRIGGERS
 103         help
 104           This option enables support for the Left, Middle, and Right
 105           LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
 106
 107 config LEDS_HP6XX
 108         tristate "LED Support for the HP Jornada 6xx"
 109         depends on LEDS_CLASS && SH_HP6XX
 110         help
 111           This option enables LED support for the handheld
 112           HP Jornada 620/660/680/690.
 113
 114 config LEDS_PCA9532
 115         tristate "LED driver for PCA9532 dimmer"
 116         depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
 117         help
 118           This option enables support for NXP pca9532
 119           LED controller. It is generally only useful
 120           as a platform driver
 121
 122 config LEDS_GPIO
 123         tristate "LED Support for GPIO connected LEDs"
 124         depends on LEDS_CLASS && GENERIC_GPIO
 125         help
 126           This option enables support for the LEDs connected to GPIO
 127           outputs. To be useful the particular board must have LEDs
 128           and they must be connected to the GPIO lines.  The LEDs must be
 129           defined as platform devices and/or OpenFirmware platform devices.
 130           The code to use these bindings can be selected below.
 131
 132 config LEDS_GPIO_PLATFORM
 133         bool "Platform device bindings for GPIO LEDs"
 134         depends on LEDS_GPIO
 135         default y
 136         help
 137           Let the leds-gpio driver drive LEDs which have been defined as
 138           platform devices.  If you don't know what this means, say yes.
 139
 140 config LEDS_GPIO_OF
 141         bool "OpenFirmware platform device bindings for GPIO LEDs"
 142         depends on LEDS_GPIO && OF_DEVICE
 143         default y
 144         help
 145           Let the leds-gpio driver drive LEDs which have been defined as
 146           of_platform devices.  For instance, LEDs which are listed in a "dts"
 147           file.
 148
 149 config LEDS_LP3944
 150         tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
 151         depends on LEDS_CLASS && I2C
 152         help
 153     This option enables support for LEDs connected to the National
 154     Semiconductor LP3944 Lighting Management Unit (LMU) also known as
 155     Fun Light Chip.
 156
 157           To compile this driver as a module, choose M here: the
 158           module will be called leds-lp3944.
 159
 160 config LEDS_CLEVO_MAIL
 161         tristate "Mail LED on Clevo notebook"
 162         depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
 163         help
 164           This driver makes the mail LED accessible from userspace
 165           programs through the leds subsystem. This LED have three
 166           known mode: off, blink at 0.5Hz and blink at 1Hz.
 167
 168           The driver supports two kinds of interface: using ledtrig-timer
 169           or through /sys/class/leds/clevo::mail/brightness. As this LED
 170           cannot change it's brightness it blinks instead. The brightness
 171           value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
 172           blink at 1Hz.
 173
 174           This module can drive the mail LED for the following notebooks:
 175
 176                 Clevo D400P
 177                 Clevo D410J
 178                 Clevo D410V
 179                 Clevo D400V/D470V (not tested, but might work)
 180                 Clevo M540N
 181                 Clevo M5x0N (not tested, but might work)
 182                 Positivo Mobile (Clevo M5x0V)
 183
 184           If your model is not listed here you can try the "nodetect"
 185           module parameter.
 186
 187           To compile this driver as a module, choose M here: the
 188           module will be called leds-clevo-mail.
 189
 190 config LEDS_PCA955X
 191         tristate "LED Support for PCA955x I2C chips"
 192         depends on LEDS_CLASS && I2C
 193         help
 194           This option enables support for LEDs connected to PCA955x
 195           LED driver chips accessed via the I2C bus.  Supported
 196           devices include PCA9550, PCA9551, PCA9552, and PCA9553.
 197
 198 config LEDS_WM8350
 199         tristate "LED Support for WM8350 AudioPlus PMIC"
 200         depends on LEDS_CLASS && MFD_WM8350
 201         help
 202           This option enables support for LEDs driven by the Wolfson
 203           Microelectronics WM8350 AudioPlus PMIC.
 204
 205 config LEDS_DA903X
 206         tristate "LED Support for DA9030/DA9034 PMIC"
 207         depends on LEDS_CLASS && PMIC_DA903X
 208         help
 209           This option enables support for on-chip LED drivers found
 210           on Dialog Semiconductor DA9030/DA9034 PMICs.
 211
 212 config LEDS_DAC124S085
 213         tristate "LED Support for DAC124S085 SPI DAC"
 214         depends on LEDS_CLASS && SPI
 215         help
 216           This option enables support for DAC124S085 SPI DAC from NatSemi,
 217           which can be used to control up to four LEDs.
 218
 219 config LEDS_PWM
 220         tristate "PWM driven LED Support"
 221         depends on LEDS_CLASS && HAVE_PWM
 222         help
 223           This option enables support for pwm driven LEDs
 224
 225 config LEDS_BD2802
 226         tristate "LED driver for BD2802 RGB LED"
 227         depends on LEDS_CLASS && I2C
 228         help
 229           This option enables support for BD2802GU RGB LED driver chips
 230           accessed via the I2C bus.
 231
 232 comment "LED Triggers"
 233
 234 config LEDS_TRIGGERS
 235         bool "LED Trigger support"
 236         help
 237           This option enables trigger support for the leds class.
 238           These triggers allow kernel events to drive the LEDs and can
 239           be configured via sysfs. If unsure, say Y.
 240
 241 config LEDS_TRIGGER_TIMER
 242         tristate "LED Timer Trigger"
 243         depends on LEDS_TRIGGERS
 244         help
 245           This allows LEDs to be controlled by a programmable timer
 246           via sysfs. Some LED hardware can be programmed to start
 247           blinking the LED without any further software interaction.
 248           For more details read Documentation/leds-class.txt.
 249
 250           If unsure, say Y.
 251
 252 config LEDS_TRIGGER_IDE_DISK
 253         bool "LED IDE Disk Trigger"
 254         depends on LEDS_TRIGGERS && IDE_GD_ATA
 255         help
 256           This allows LEDs to be controlled by IDE disk activity.
 257           If unsure, say Y.
 258
 259 config LEDS_TRIGGER_HEARTBEAT
 260         tristate "LED Heartbeat Trigger"
 261         depends on LEDS_TRIGGERS
 262         help
 263           This allows LEDs to be controlled by a CPU load average.
 264           The flash frequency is a hyperbolic function of the 1-minute
 265           load average.
 266           If unsure, say Y.
 267
 268 config LEDS_TRIGGER_BACKLIGHT
 269         tristate "LED backlight Trigger"
 270         depends on LEDS_TRIGGERS
 271         help
 272           This allows LEDs to be controlled as a backlight device: they
 273           turn off and on when the display is blanked and unblanked.
 274
 275           If unsure, say N.
 276
 277 config LEDS_TRIGGER_GPIO
 278         tristate "LED GPIO Trigger"
 279         depends on LEDS_TRIGGERS
 280         depends on GPIOLIB
 281         help
 282           This allows LEDs to be controlled by gpio events. It's good
 283           when using gpios as switches and triggering the needed LEDs
 284           from there. One use case is n810's keypad LEDs that could
 285           be triggered by this trigger when user slides up to show
 286           keypad.
 287
 288           If unsure, say N.
 289
 290 config LEDS_TRIGGER_DEFAULT_ON
 291         tristate "LED Default ON Trigger"
 292         depends on LEDS_TRIGGERS
 293         help
 294           This allows LEDs to be initialised in the ON state.
 295           If unsure, say Y.
 296
 297 comment "iptables trigger is under Netfilter config (LED target)"
 298         depends on LEDS_TRIGGERS
 299
 300 endif # NEW_LEDS