2011-06-16 06:08:31 +08:00
|
|
|
config LEDS_GPIO_REGISTER
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option provides the function gpio_led_register_device.
|
|
|
|
|
As this function is used by arch code it must not be compiled as a
|
|
|
|
|
module.
|
|
|
|
|
|
2007-05-10 17:44:11 +08:00
|
|
|
menuconfig NEW_LEDS
|
2006-03-31 18:31:04 +08:00
|
|
|
bool "LED Support"
|
|
|
|
|
help
|
2006-05-16 00:44:14 +08:00
|
|
|
Say Y to enable Linux LED support. This allows control of supported
|
|
|
|
|
LEDs from both userspace and optionally, by kernel events (triggers).
|
|
|
|
|
|
|
|
|
|
This is not related to standard keyboard LEDs which are controlled
|
|
|
|
|
via the input system.
|
2006-03-31 18:31:04 +08:00
|
|
|
|
2011-06-16 06:08:40 +08:00
|
|
|
if NEW_LEDS
|
|
|
|
|
|
2006-03-31 18:31:04 +08:00
|
|
|
config LEDS_CLASS
|
2012-03-24 06:02:14 +08:00
|
|
|
tristate "LED Class Support"
|
2006-03-31 18:31:04 +08:00
|
|
|
help
|
|
|
|
|
This option enables the led sysfs class in /sys/class/leds. You'll
|
|
|
|
|
need this to do anything useful with LEDs. If unsure, say N.
|
|
|
|
|
|
2006-04-11 13:54:01 +08:00
|
|
|
comment "LED drivers"
|
2006-03-31 18:31:05 +08:00
|
|
|
|
2010-01-07 06:10:09 +08:00
|
|
|
config LEDS_88PM860X
|
|
|
|
|
tristate "LED Support for Marvell 88PM860x PMIC"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-05-27 20:08:33 +08:00
|
|
|
depends on MFD_88PM860X
|
2010-01-07 06:10:09 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found on Marvell
|
|
|
|
|
Semiconductor 88PM8606 PMIC.
|
|
|
|
|
|
2008-02-08 20:21:22 +08:00
|
|
|
config LEDS_ATMEL_PWM
|
|
|
|
|
tristate "LED Support using Atmel PWM outputs"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on ATMEL_PWM
|
2008-02-08 20:21:22 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for LEDs driven using outputs
|
|
|
|
|
of the dedicated PWM controller found on newer Atmel SOCs.
|
|
|
|
|
|
2011-03-23 07:30:16 +08:00
|
|
|
config LEDS_LM3530
|
|
|
|
|
tristate "LCD Backlight driver for LM3530"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the LCD backlight using
|
|
|
|
|
LM3530 ambient light sensor chip. This ALS chip can be
|
|
|
|
|
controlled manually or using PWM input or using ambient
|
|
|
|
|
light automatically.
|
|
|
|
|
|
2012-05-30 06:07:31 +08:00
|
|
|
config LEDS_LM3533
|
|
|
|
|
tristate "LED support for LM3533"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on MFD_LM3533
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on National Semiconductor /
|
|
|
|
|
TI LM3533 Lighting Power chips.
|
|
|
|
|
|
|
|
|
|
The LEDs can be controlled directly, through PWM input, or by the
|
|
|
|
|
ambient-light-sensor interface. The chip supports
|
|
|
|
|
hardware-accelerated blinking with maximum on and off periods of 9.8
|
|
|
|
|
and 77 seconds respectively.
|
|
|
|
|
|
2012-09-12 20:05:50 +08:00
|
|
|
config LEDS_LM3642
|
|
|
|
|
tristate "LED support for LM3642 Chip"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to LM3642.
|
|
|
|
|
The LM3642 is a 4MHz fixed-frequency synchronous boost
|
|
|
|
|
converter plus 1.5A constant current driver for a high-current
|
|
|
|
|
white LED.
|
|
|
|
|
|
|
|
|
|
|
2006-03-31 18:31:10 +08:00
|
|
|
config LEDS_LOCOMO
|
|
|
|
|
tristate "LED Support for Locomo device"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on SHARP_LOCOMO
|
2006-03-31 18:31:10 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on Sharp Locomo.
|
|
|
|
|
Zaurus models SL-5500 and SL-5600.
|
|
|
|
|
|
2009-01-23 02:35:48 +08:00
|
|
|
config LEDS_MIKROTIK_RB532
|
|
|
|
|
tristate "LED Support for Mikrotik Routerboard 532"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on MIKROTIK_RB532
|
2009-01-23 02:35:48 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the so called "User LED" of
|
|
|
|
|
Mikrotik's Routerboard 532.
|
|
|
|
|
|
2006-04-11 13:54:00 +08:00
|
|
|
config LEDS_S3C24XX
|
|
|
|
|
tristate "LED Support for Samsung S3C24XX GPIO LEDs"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2012-02-03 13:29:23 +08:00
|
|
|
depends on ARCH_S3C24XX
|
2006-04-11 13:54:00 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to GPIO lines
|
|
|
|
|
on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
|
|
|
|
|
|
2006-07-10 19:45:34 +08:00
|
|
|
config LEDS_NET48XX
|
|
|
|
|
tristate "LED Support for Soekris net48xx series Error LED"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on SCx200_GPIO
|
2006-07-10 19:45:34 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the Soekris net4801 and net4826 error
|
|
|
|
|
LED.
|
|
|
|
|
|
2008-04-25 06:43:09 +08:00
|
|
|
config LEDS_FSG
|
|
|
|
|
tristate "LED Support for the Freecom FSG-3"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on MACH_FSG
|
2008-04-25 06:43:09 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the Freecom FSG-3.
|
|
|
|
|
|
2006-12-07 12:37:28 +08:00
|
|
|
config LEDS_WRAP
|
|
|
|
|
tristate "LED Support for the WRAP series LEDs"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on SCx200_GPIO
|
2006-12-07 12:37:28 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the PCEngines WRAP programmable LEDs.
|
|
|
|
|
|
2007-09-21 07:02:47 +08:00
|
|
|
config LEDS_COBALT_QUBE
|
|
|
|
|
tristate "LED Support for the Cobalt Qube series front LED"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on MIPS_COBALT
|
2007-02-13 07:16:27 +08:00
|
|
|
help
|
2007-09-21 07:02:47 +08:00
|
|
|
This option enables support for the front LED on Cobalt Qube series
|
2007-02-13 07:16:27 +08:00
|
|
|
|
2007-09-27 16:51:05 +08:00
|
|
|
config LEDS_COBALT_RAQ
|
|
|
|
|
bool "LED Support for the Cobalt Raq series"
|
2008-12-03 16:09:28 +08:00
|
|
|
depends on LEDS_CLASS=y && MIPS_COBALT
|
2007-09-27 16:51:05 +08:00
|
|
|
select LEDS_TRIGGERS
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the Cobalt Raq series LEDs.
|
|
|
|
|
|
2008-09-01 11:26:48 +08:00
|
|
|
config LEDS_SUNFIRE
|
|
|
|
|
tristate "LED support for SunFire servers."
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on SPARC64
|
2008-09-01 11:26:48 +08:00
|
|
|
select LEDS_TRIGGERS
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the Left, Middle, and Right
|
|
|
|
|
LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
|
|
|
|
|
|
2008-02-07 18:10:28 +08:00
|
|
|
config LEDS_HP6XX
|
|
|
|
|
tristate "LED Support for the HP Jornada 6xx"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on SH_HP6XX
|
2008-02-07 18:10:28 +08:00
|
|
|
help
|
2009-01-26 18:12:25 +08:00
|
|
|
This option enables LED support for the handheld
|
2008-02-07 18:10:28 +08:00
|
|
|
HP Jornada 620/660/680/690.
|
|
|
|
|
|
2008-05-31 21:43:41 +08:00
|
|
|
config LEDS_PCA9532
|
|
|
|
|
tristate "LED driver for PCA9532 dimmer"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2013-01-17 10:53:41 +08:00
|
|
|
depends on I2C && INPUT
|
2008-05-31 21:43:41 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for NXP pca9532
|
2009-01-26 18:12:25 +08:00
|
|
|
LED controller. It is generally only useful
|
2008-05-31 21:43:41 +08:00
|
|
|
as a platform driver
|
|
|
|
|
|
2011-05-25 08:13:23 +08:00
|
|
|
config LEDS_PCA9532_GPIO
|
|
|
|
|
bool "Enable GPIO support for PCA9532"
|
|
|
|
|
depends on LEDS_PCA9532
|
|
|
|
|
depends on GPIOLIB
|
|
|
|
|
help
|
|
|
|
|
Allow unused pins on PCA9532 to be used as gpio.
|
|
|
|
|
|
|
|
|
|
To use a pin as gpio pca9532_type in pca9532_platform data needs to
|
|
|
|
|
set to PCA9532_TYPE_GPIO.
|
|
|
|
|
|
2007-02-28 03:49:53 +08:00
|
|
|
config LEDS_GPIO
|
|
|
|
|
tristate "LED Support for GPIO connected LEDs"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on GENERIC_GPIO
|
2007-02-28 03:49:53 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs connected to GPIO
|
|
|
|
|
outputs. To be useful the particular board must have LEDs
|
2009-01-11 01:26:01 +08:00
|
|
|
and they must be connected to the GPIO lines. The LEDs must be
|
|
|
|
|
defined as platform devices and/or OpenFirmware platform devices.
|
|
|
|
|
The code to use these bindings can be selected below.
|
|
|
|
|
|
2009-06-19 19:55:42 +08:00
|
|
|
config LEDS_LP3944
|
|
|
|
|
tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on I2C
|
2009-06-19 19:55:42 +08:00
|
|
|
help
|
2009-07-03 22:18:45 +08:00
|
|
|
This option enables support for LEDs connected to the National
|
|
|
|
|
Semiconductor LP3944 Lighting Management Unit (LMU) also known as
|
|
|
|
|
Fun Light Chip.
|
2009-06-19 19:55:42 +08:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called leds-lp3944.
|
|
|
|
|
|
2013-02-05 17:01:23 +08:00
|
|
|
config LEDS_LP55XX_COMMON
|
|
|
|
|
tristate "Common Driver for TI/National LP5521 and LP5523/55231"
|
|
|
|
|
depends on LEDS_LP5521 || LEDS_LP5523
|
2013-02-05 18:17:20 +08:00
|
|
|
select FW_LOADER
|
2013-02-05 17:01:23 +08:00
|
|
|
help
|
|
|
|
|
This option supports common operations for LP5521 and LP5523/55231
|
|
|
|
|
devices.
|
|
|
|
|
|
2010-11-12 06:05:23 +08:00
|
|
|
config LEDS_LP5521
|
|
|
|
|
tristate "LED Support for N.S. LP5521 LED driver chip"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
2013-02-05 17:01:23 +08:00
|
|
|
select LEDS_LP55XX_COMMON
|
2010-11-12 06:05:23 +08:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the National Semiconductor
|
|
|
|
|
LP5521 LED driver. It is 3 channel chip with programmable engines.
|
|
|
|
|
Driver provides direct control via LED class and interface for
|
|
|
|
|
programming the engines.
|
|
|
|
|
|
|
|
|
|
config LEDS_LP5523
|
2012-09-04 15:06:11 +08:00
|
|
|
tristate "LED Support for TI/National LP5523/55231 LED driver chip"
|
2010-11-12 06:05:23 +08:00
|
|
|
depends on LEDS_CLASS && I2C
|
2013-02-05 17:01:23 +08:00
|
|
|
select LEDS_LP55XX_COMMON
|
2010-11-12 06:05:23 +08:00
|
|
|
help
|
2012-09-04 15:06:11 +08:00
|
|
|
If you say yes here you get support for TI/National Semiconductor
|
|
|
|
|
LP5523/55231 LED driver.
|
|
|
|
|
It is 9 channel chip with programmable engines.
|
2010-11-12 06:05:23 +08:00
|
|
|
Driver provides direct control via LED class and interface for
|
|
|
|
|
programming the engines.
|
|
|
|
|
|
2012-07-20 16:43:59 +08:00
|
|
|
config LEDS_LP8788
|
|
|
|
|
tristate "LED support for the TI LP8788 PMIC"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on MFD_LP8788
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the Keyboard LEDs on the LP8788 PMIC.
|
|
|
|
|
|
2007-10-31 18:46:41 +08:00
|
|
|
config LEDS_CLEVO_MAIL
|
2009-04-03 13:42:47 +08:00
|
|
|
tristate "Mail LED on Clevo notebook"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on X86 && SERIO_I8042 && DMI
|
2007-10-31 18:46:41 +08:00
|
|
|
help
|
|
|
|
|
This driver makes the mail LED accessible from userspace
|
|
|
|
|
programs through the leds subsystem. This LED have three
|
|
|
|
|
known mode: off, blink at 0.5Hz and blink at 1Hz.
|
|
|
|
|
|
2007-10-31 22:09:05 +08:00
|
|
|
The driver supports two kinds of interface: using ledtrig-timer
|
|
|
|
|
or through /sys/class/leds/clevo::mail/brightness. As this LED
|
|
|
|
|
cannot change it's brightness it blinks instead. The brightness
|
|
|
|
|
value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
|
|
|
|
|
blink at 1Hz.
|
2007-10-31 18:46:41 +08:00
|
|
|
|
|
|
|
|
This module can drive the mail LED for the following notebooks:
|
|
|
|
|
|
2008-03-10 04:47:59 +08:00
|
|
|
Clevo D400P
|
2007-10-31 18:46:41 +08:00
|
|
|
Clevo D410J
|
|
|
|
|
Clevo D410V
|
|
|
|
|
Clevo D400V/D470V (not tested, but might work)
|
|
|
|
|
Clevo M540N
|
|
|
|
|
Clevo M5x0N (not tested, but might work)
|
|
|
|
|
Positivo Mobile (Clevo M5x0V)
|
|
|
|
|
|
2008-03-10 04:47:59 +08:00
|
|
|
If your model is not listed here you can try the "nodetect"
|
2009-01-26 18:12:25 +08:00
|
|
|
module parameter.
|
2008-03-10 04:47:59 +08:00
|
|
|
|
2007-10-31 18:46:41 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called leds-clevo-mail.
|
|
|
|
|
|
2008-07-17 05:49:55 +08:00
|
|
|
config LEDS_PCA955X
|
|
|
|
|
tristate "LED Support for PCA955x I2C chips"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on I2C
|
2008-07-17 05:49:55 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to PCA955x
|
|
|
|
|
LED driver chips accessed via the I2C bus. Supported
|
|
|
|
|
devices include PCA9550, PCA9551, PCA9552, and PCA9553.
|
|
|
|
|
|
2012-03-24 06:02:10 +08:00
|
|
|
config LEDS_PCA9633
|
|
|
|
|
tristate "LED support for PCA9633 I2C chip"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to the PCA9633
|
|
|
|
|
LED driver chip accessed via the I2C bus.
|
|
|
|
|
|
2009-09-05 21:09:21 +08:00
|
|
|
config LEDS_WM831X_STATUS
|
|
|
|
|
tristate "LED support for status LEDs on WM831x PMICs"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on MFD_WM831X
|
2009-09-05 21:09:21 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the status LEDs of the WM831x
|
|
|
|
|
series of PMICs.
|
|
|
|
|
|
2008-12-05 00:52:33 +08:00
|
|
|
config LEDS_WM8350
|
|
|
|
|
tristate "LED Support for WM8350 AudioPlus PMIC"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on MFD_WM8350
|
2008-12-05 00:52:33 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for LEDs driven by the Wolfson
|
|
|
|
|
Microelectronics WM8350 AudioPlus PMIC.
|
|
|
|
|
|
2008-10-13 16:06:10 +08:00
|
|
|
config LEDS_DA903X
|
|
|
|
|
tristate "LED Support for DA9030/DA9034 PMIC"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on PMIC_DA903X
|
2008-10-13 16:06:10 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found
|
|
|
|
|
on Dialog Semiconductor DA9030/DA9034 PMICs.
|
|
|
|
|
|
2012-05-30 06:07:26 +08:00
|
|
|
config LEDS_DA9052
|
|
|
|
|
tristate "Dialog DA9052/DA9053 LEDS"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on PMIC_DA9052
|
|
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found
|
|
|
|
|
on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
|
|
|
|
|
|
2009-01-11 02:58:28 +08:00
|
|
|
config LEDS_DAC124S085
|
|
|
|
|
tristate "LED Support for DAC124S085 SPI DAC"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on SPI
|
2009-01-11 02:58:28 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for DAC124S085 SPI DAC from NatSemi,
|
|
|
|
|
which can be used to control up to four LEDs.
|
|
|
|
|
|
2009-02-12 05:24:40 +08:00
|
|
|
config LEDS_PWM
|
|
|
|
|
tristate "PWM driven LED Support"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2013-01-23 16:35:04 +08:00
|
|
|
depends on PWM
|
2009-02-12 05:24:40 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for pwm driven LEDs
|
|
|
|
|
|
2009-12-07 22:08:13 +08:00
|
|
|
config LEDS_REGULATOR
|
|
|
|
|
tristate "REGULATOR driven LED support"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on REGULATOR
|
2009-12-07 22:08:13 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for regulator driven LEDs.
|
|
|
|
|
|
2009-03-05 03:59:29 +08:00
|
|
|
config LEDS_BD2802
|
|
|
|
|
tristate "LED driver for BD2802 RGB LED"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on I2C
|
2009-03-05 03:59:29 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for BD2802GU RGB LED driver chips
|
|
|
|
|
accessed via the I2C bus.
|
|
|
|
|
|
2009-10-02 06:43:32 +08:00
|
|
|
config LEDS_INTEL_SS4200
|
|
|
|
|
tristate "LED driver for Intel NAS SS4200 series"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on PCI && DMI
|
2009-10-02 06:43:32 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the Intel SS4200 series of
|
|
|
|
|
Network Attached Storage servers. You may control the hard
|
|
|
|
|
drive or power LEDs on the front panel. Using this driver
|
|
|
|
|
can stop the front LED from blinking after startup.
|
|
|
|
|
|
2009-10-15 08:59:35 +08:00
|
|
|
config LEDS_LT3593
|
|
|
|
|
tristate "LED driver for LT3593 controllers"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on GENERIC_GPIO
|
2009-10-15 08:59:35 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for LEDs driven by a Linear Technology
|
|
|
|
|
LT3593 controller. This controller uses a special one-wire pulse
|
|
|
|
|
coding protocol to set the brightness.
|
|
|
|
|
|
2009-10-08 16:00:19 +08:00
|
|
|
config LEDS_ADP5520
|
|
|
|
|
tristate "LED Support for ADP5520/ADP5501 PMIC"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on PMIC_ADP5520
|
2009-10-08 16:00:19 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found
|
|
|
|
|
on Analog Devices ADP5520/ADP5501 PMICs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module will
|
|
|
|
|
be called leds-adp5520.
|
|
|
|
|
|
2010-02-18 05:23:31 +08:00
|
|
|
config LEDS_DELL_NETBOOKS
|
|
|
|
|
tristate "External LED on Dell Business Netbooks"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-02-18 05:23:31 +08:00
|
|
|
depends on X86 && ACPI_WMI
|
|
|
|
|
help
|
|
|
|
|
This adds support for the Latitude 2100 and similar
|
|
|
|
|
notebooks that have an external LED.
|
|
|
|
|
|
2010-05-19 15:24:31 +08:00
|
|
|
config LEDS_MC13783
|
|
|
|
|
tristate "LED Support for MC13783 PMIC"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-05-19 15:24:31 +08:00
|
|
|
depends on MFD_MC13783
|
|
|
|
|
help
|
|
|
|
|
This option enable support for on-chip LED drivers found
|
|
|
|
|
on Freescale Semiconductor MC13783 PMIC.
|
|
|
|
|
|
2010-07-06 22:08:46 +08:00
|
|
|
config LEDS_NS2
|
|
|
|
|
tristate "LED support for Network Space v2 GPIO LEDs"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2011-11-23 19:25:42 +08:00
|
|
|
depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
|
2012-10-17 18:09:04 +08:00
|
|
|
MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2 || \
|
|
|
|
|
MACH_NETSPACE_V2_DT || MACH_INETSPACE_V2_DT || \
|
2012-10-17 18:09:06 +08:00
|
|
|
MACH_NETSPACE_MAX_V2_DT || MACH_NETSPACE_MINI_V2_DT
|
2010-07-06 22:08:46 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option enable support for the dual-GPIO LED found on the
|
|
|
|
|
Network Space v2 board (and parents). This include Internet Space v2,
|
|
|
|
|
Network Space (Max) v2 and d2 Network v2 boards.
|
|
|
|
|
|
2010-10-07 22:38:49 +08:00
|
|
|
config LEDS_NETXBIG
|
|
|
|
|
tristate "LED support for Big Network series LEDs"
|
|
|
|
|
depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
|
2011-07-26 08:13:16 +08:00
|
|
|
depends on LEDS_CLASS
|
2010-10-07 22:38:49 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option enable support for LEDs found on the LaCie 2Big
|
|
|
|
|
and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
|
|
|
|
|
controlled through a GPIO extension bus.
|
|
|
|
|
|
2011-05-14 02:52:56 +08:00
|
|
|
config LEDS_ASIC3
|
|
|
|
|
bool "LED support for the HTC ASIC3"
|
2012-06-09 07:41:42 +08:00
|
|
|
depends on LEDS_CLASS=y
|
2011-05-14 02:52:56 +08:00
|
|
|
depends on MFD_ASIC3
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the HTC ASIC3. The HTC
|
|
|
|
|
ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
|
|
|
|
|
cannot be used. This driver supports hardware blinking with an on+off
|
|
|
|
|
period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
|
|
|
|
|
|
2011-11-01 08:11:55 +08:00
|
|
|
config LEDS_RENESAS_TPU
|
|
|
|
|
bool "LED support for Renesas TPU"
|
2012-06-09 07:41:42 +08:00
|
|
|
depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO
|
2011-11-01 08:11:55 +08:00
|
|
|
help
|
|
|
|
|
This option enables build of the LED TPU platform driver,
|
|
|
|
|
suitable to drive any TPU channel on newer Renesas SoCs.
|
|
|
|
|
The driver controls the GPIO pin connected to the LED via
|
|
|
|
|
the GPIO framework and expects the LED to be connected to
|
|
|
|
|
a pin that can be driven in both GPIO mode and using TPU
|
|
|
|
|
pin function. The latter to support brightness control.
|
|
|
|
|
Brightness control is supported but hardware blinking is not.
|
|
|
|
|
|
2012-01-11 07:09:40 +08:00
|
|
|
config LEDS_TCA6507
|
|
|
|
|
tristate "LED Support for TCA6507 I2C chip"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to TC6507
|
|
|
|
|
LED driver chips accessed via the I2C bus.
|
|
|
|
|
Driver support brightness control and hardware-assisted blinking.
|
|
|
|
|
|
2011-12-14 17:23:56 +08:00
|
|
|
config LEDS_MAX8997
|
|
|
|
|
tristate "LED support for MAX8997 PMIC"
|
|
|
|
|
depends on LEDS_CLASS && MFD_MAX8997
|
|
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers on
|
|
|
|
|
MAXIM MAX8997 PMIC.
|
|
|
|
|
|
2012-09-05 15:05:58 +08:00
|
|
|
config LEDS_LM355x
|
|
|
|
|
tristate "LED support for LM355x Chips, LM3554 and LM3556"
|
2012-06-22 08:12:06 +08:00
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
2012-09-05 15:05:58 +08:00
|
|
|
This option enables support for LEDs connected to LM355x.
|
|
|
|
|
LM355x includes Torch, Flash and Indicator functions.
|
2012-06-22 08:12:06 +08:00
|
|
|
|
2012-01-21 06:33:59 +08:00
|
|
|
config LEDS_OT200
|
|
|
|
|
tristate "LED support for the Bachmann OT200"
|
|
|
|
|
depends on LEDS_CLASS && HAS_IOMEM
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the Bachmann OT200.
|
|
|
|
|
Say Y to enable LEDs on the Bachmann OT200.
|
|
|
|
|
|
2012-07-20 16:49:06 +08:00
|
|
|
config LEDS_BLINKM
|
|
|
|
|
tristate "LED support for the BlinkM I2C RGB LED"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the BlinkM RGB LED connected
|
|
|
|
|
through I2C. Say Y to enable support for the BlinkM LED.
|
|
|
|
|
|
2006-04-11 13:54:01 +08:00
|
|
|
config LEDS_TRIGGERS
|
|
|
|
|
bool "LED Trigger support"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_CLASS
|
2006-04-11 13:54:01 +08:00
|
|
|
help
|
|
|
|
|
This option enables trigger support for the leds class.
|
|
|
|
|
These triggers allow kernel events to drive the LEDs and can
|
|
|
|
|
be configured via sysfs. If unsure, say Y.
|
|
|
|
|
|
2010-01-21 07:08:30 +08:00
|
|
|
comment "LED Triggers"
|
|
|
|
|
|
2006-03-31 18:31:07 +08:00
|
|
|
config LEDS_TRIGGER_TIMER
|
|
|
|
|
tristate "LED Timer Trigger"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_TRIGGERS
|
2006-03-31 18:31:07 +08:00
|
|
|
help
|
|
|
|
|
This allows LEDs to be controlled by a programmable timer
|
2007-10-31 22:07:12 +08:00
|
|
|
via sysfs. Some LED hardware can be programmed to start
|
|
|
|
|
blinking the LED without any further software interaction.
|
2011-08-15 08:02:26 +08:00
|
|
|
For more details read Documentation/leds/leds-class.txt.
|
2007-10-31 22:07:12 +08:00
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2006-03-31 18:31:07 +08:00
|
|
|
|
2012-06-07 06:11:05 +08:00
|
|
|
config LEDS_TRIGGER_ONESHOT
|
|
|
|
|
tristate "LED One-shot Trigger"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
help
|
|
|
|
|
This allows LEDs to blink in one-shot pulses with parameters
|
|
|
|
|
controlled via sysfs. It's useful to notify the user on
|
|
|
|
|
sporadic events, when there are no clear begin and end trap points,
|
|
|
|
|
or on dense events, where this blinks the LED at constant rate if
|
|
|
|
|
rearmed continuously.
|
|
|
|
|
|
|
|
|
|
It also shows how to use the led_blink_set_oneshot() function.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2006-03-31 18:31:16 +08:00
|
|
|
config LEDS_TRIGGER_IDE_DISK
|
2006-04-11 13:54:01 +08:00
|
|
|
bool "LED IDE Disk Trigger"
|
2010-01-21 07:08:30 +08:00
|
|
|
depends on IDE_GD_ATA
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_TRIGGERS
|
2006-03-31 18:31:16 +08:00
|
|
|
help
|
|
|
|
|
This allows LEDs to be controlled by IDE disk activity.
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2006-06-25 20:49:15 +08:00
|
|
|
config LEDS_TRIGGER_HEARTBEAT
|
|
|
|
|
tristate "LED Heartbeat Trigger"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_TRIGGERS
|
2006-06-25 20:49:15 +08:00
|
|
|
help
|
|
|
|
|
This allows LEDs to be controlled by a CPU load average.
|
|
|
|
|
The flash frequency is a hyperbolic function of the 1-minute
|
|
|
|
|
load average.
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2008-10-13 16:25:24 +08:00
|
|
|
config LEDS_TRIGGER_BACKLIGHT
|
|
|
|
|
tristate "LED backlight Trigger"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_TRIGGERS
|
2008-10-13 16:25:24 +08:00
|
|
|
help
|
|
|
|
|
This allows LEDs to be controlled as a backlight device: they
|
|
|
|
|
turn off and on when the display is blanked and unblanked.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-06-25 18:33:50 +08:00
|
|
|
config LEDS_TRIGGER_CPU
|
|
|
|
|
bool "LED CPU Trigger"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
help
|
|
|
|
|
This allows LEDs to be controlled by active CPUs. This shows
|
|
|
|
|
the active CPUs across an array of LEDs so you can see which
|
|
|
|
|
CPUs are active on the system at any given moment.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-02-17 19:18:11 +08:00
|
|
|
config LEDS_TRIGGER_GPIO
|
|
|
|
|
tristate "LED GPIO Trigger"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_TRIGGERS
|
2009-02-17 19:18:11 +08:00
|
|
|
depends on GPIOLIB
|
|
|
|
|
help
|
|
|
|
|
This allows LEDs to be controlled by gpio events. It's good
|
|
|
|
|
when using gpios as switches and triggering the needed LEDs
|
|
|
|
|
from there. One use case is n810's keypad LEDs that could
|
|
|
|
|
be triggered by this trigger when user slides up to show
|
|
|
|
|
keypad.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2008-04-25 07:06:52 +08:00
|
|
|
config LEDS_TRIGGER_DEFAULT_ON
|
|
|
|
|
tristate "LED Default ON Trigger"
|
2010-12-03 06:31:14 +08:00
|
|
|
depends on LEDS_TRIGGERS
|
2008-04-25 07:06:52 +08:00
|
|
|
help
|
|
|
|
|
This allows LEDs to be initialised in the ON state.
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2009-02-20 17:55:14 +08:00
|
|
|
comment "iptables trigger is under Netfilter config (LED target)"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
|
leds: add new transient trigger for one shot timer activation
The leds timer trigger does not currently have an interface to activate a
one shot timer. The current support allows for setting two timers, one
for specifying how long a state to be on, and the second for how long the
state to be off. The delay_on value specifies the time period an LED
should stay in on state, followed by a delay_off value that specifies how
long the LED should stay in off state. The on and off cycle repeats until
the trigger gets deactivated. There is no provision for one time
activation to implement features that require an on or off state to be
held just once and then stay in the original state forever.
Without one shot timer interface, user space can still use timer trigger
to set a timer to hold a state, however when user space application
crashes or goes away without deactivating the timer, the hardware will be
left in that state permanently.
As a specific example of this use-case, let's look at vibrate feature on
phones. Vibrate function on phones is implemented using PWM pins on SoC
or PMIC. There is a need to activate one shot timer to control the
vibrate feature, to prevent user space crashes leaving the phone in
vibrate mode permanently causing the battery to drain.
This trigger exports three properties, activate, state, and duration When
transient trigger is activated these properties are set to default values.
- duration allows setting timer value in msecs. The initial value is 0.
- activate allows activating and deactivating the timer specified by
duration as needed. The initial and default value is 0. This will allow
duration to be set after trigger activation.
- state allows user to specify a transient state to be held for the specified
duration.
Signed-off-by: Shuah Khan <shuahkhan@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>
Cc: Richard Purdie <rpurdie@rpsys.net>
Cc: NeilBrown <neilb@suse.de>
Cc: Bryan Wu <bryan.wu@canonical.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-05-30 06:07:30 +08:00
|
|
|
config LEDS_TRIGGER_TRANSIENT
|
|
|
|
|
tristate "LED Transient Trigger"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
help
|
|
|
|
|
This allows one time activation of a transient state on
|
2012-06-15 18:13:25 +08:00
|
|
|
GPIO/PWM based hardware.
|
leds: add new transient trigger for one shot timer activation
The leds timer trigger does not currently have an interface to activate a
one shot timer. The current support allows for setting two timers, one
for specifying how long a state to be on, and the second for how long the
state to be off. The delay_on value specifies the time period an LED
should stay in on state, followed by a delay_off value that specifies how
long the LED should stay in off state. The on and off cycle repeats until
the trigger gets deactivated. There is no provision for one time
activation to implement features that require an on or off state to be
held just once and then stay in the original state forever.
Without one shot timer interface, user space can still use timer trigger
to set a timer to hold a state, however when user space application
crashes or goes away without deactivating the timer, the hardware will be
left in that state permanently.
As a specific example of this use-case, let's look at vibrate feature on
phones. Vibrate function on phones is implemented using PWM pins on SoC
or PMIC. There is a need to activate one shot timer to control the
vibrate feature, to prevent user space crashes leaving the phone in
vibrate mode permanently causing the battery to drain.
This trigger exports three properties, activate, state, and duration When
transient trigger is activated these properties are set to default values.
- duration allows setting timer value in msecs. The initial value is 0.
- activate allows activating and deactivating the timer specified by
duration as needed. The initial and default value is 0. This will allow
duration to be set after trigger activation.
- state allows user to specify a transient state to be held for the specified
duration.
Signed-off-by: Shuah Khan <shuahkhan@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>
Cc: Richard Purdie <rpurdie@rpsys.net>
Cc: NeilBrown <neilb@suse.de>
Cc: Bryan Wu <bryan.wu@canonical.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-05-30 06:07:30 +08:00
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2007-05-10 17:44:11 +08:00
|
|
|
endif # NEW_LEDS
|