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
|
|
|
|
2007-05-10 17:44:11 +08:00
|
|
|
if NEW_LEDS
|
|
|
|
|
|
2006-03-31 18:31:04 +08:00
|
|
|
config LEDS_CLASS
|
|
|
|
|
tristate "LED Class Support"
|
|
|
|
|
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
|
|
|
|
2008-02-08 20:21:22 +08:00
|
|
|
config LEDS_ATMEL_PWM
|
|
|
|
|
tristate "LED Support using Atmel PWM outputs"
|
|
|
|
|
depends on LEDS_CLASS && ATMEL_PWM
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs driven using outputs
|
|
|
|
|
of the dedicated PWM controller found on newer Atmel SOCs.
|
|
|
|
|
|
2006-03-31 18:31:10 +08:00
|
|
|
config LEDS_LOCOMO
|
|
|
|
|
tristate "LED Support for Locomo device"
|
2006-12-13 03:04:19 +08:00
|
|
|
depends on LEDS_CLASS && 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"
|
|
|
|
|
depends on LEDS_CLASS && MIKROTIK_RB532
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && ARCH_S3C2410
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to GPIO lines
|
|
|
|
|
on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
|
|
|
|
|
|
2006-06-23 17:05:33 +08:00
|
|
|
config LEDS_AMS_DELTA
|
|
|
|
|
tristate "LED Support for the Amstrad Delta (E3)"
|
2006-12-13 03:04:19 +08:00
|
|
|
depends on LEDS_CLASS && MACH_AMS_DELTA
|
2006-06-23 17:05:33 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on Amstrad Delta (E3).
|
|
|
|
|
|
2006-07-10 19:45:34 +08:00
|
|
|
config LEDS_NET48XX
|
|
|
|
|
tristate "LED Support for Soekris net48xx series Error LED"
|
|
|
|
|
depends on LEDS_CLASS && SCx200_GPIO
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && MACH_FSG
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && SCx200_GPIO
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the PCEngines WRAP programmable LEDs.
|
|
|
|
|
|
2008-11-17 19:31:08 +08:00
|
|
|
config LEDS_ALIX2
|
|
|
|
|
tristate "LED Support for ALIX.2 and ALIX.3 series"
|
|
|
|
|
depends on LEDS_CLASS && X86 && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
|
|
|
|
|
|
2007-02-13 07:09:32 +08:00
|
|
|
config LEDS_H1940
|
|
|
|
|
tristate "LED Support for iPAQ H1940 device"
|
2007-09-27 02:02:52 +08:00
|
|
|
depends on LEDS_CLASS && ARCH_H1940
|
2007-02-13 07:09:32 +08:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the h1940.
|
|
|
|
|
|
2007-09-21 07:02:47 +08:00
|
|
|
config LEDS_COBALT_QUBE
|
|
|
|
|
tristate "LED Support for the Cobalt Qube series front LED"
|
2007-02-13 07:16:27 +08:00
|
|
|
depends on LEDS_CLASS && MIPS_COBALT
|
|
|
|
|
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."
|
|
|
|
|
depends on LEDS_CLASS && SPARC64
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && SH_HP6XX
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
|
|
|
|
|
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
|
|
|
|
|
|
2007-02-28 03:49:53 +08:00
|
|
|
config LEDS_GPIO
|
|
|
|
|
tristate "LED Support for GPIO connected LEDs"
|
|
|
|
|
depends on LEDS_CLASS && GENERIC_GPIO
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config LEDS_GPIO_PLATFORM
|
|
|
|
|
bool "Platform device bindings for GPIO LEDs"
|
|
|
|
|
depends on LEDS_GPIO
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Let the leds-gpio driver drive LEDs which have been defined as
|
|
|
|
|
platform devices. If you don't know what this means, say yes.
|
|
|
|
|
|
|
|
|
|
config LEDS_GPIO_OF
|
|
|
|
|
bool "OpenFirmware platform device bindings for GPIO LEDs"
|
|
|
|
|
depends on LEDS_GPIO && OF_DEVICE
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Let the leds-gpio driver drive LEDs which have been defined as
|
|
|
|
|
of_platform devices. For instance, LEDs which are listed in a "dts"
|
|
|
|
|
file.
|
2007-02-28 03:49:53 +08:00
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && 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"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
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.
|
|
|
|
|
|
2008-12-05 00:52:33 +08:00
|
|
|
config LEDS_WM8350
|
|
|
|
|
tristate "LED Support for WM8350 AudioPlus PMIC"
|
|
|
|
|
depends on LEDS_CLASS && MFD_WM8350
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && PMIC_DA903X
|
|
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found
|
|
|
|
|
on Dialog Semiconductor DA9030/DA9034 PMICs.
|
|
|
|
|
|
2009-01-11 02:58:28 +08:00
|
|
|
config LEDS_DAC124S085
|
|
|
|
|
tristate "LED Support for DAC124S085 SPI DAC"
|
|
|
|
|
depends on LEDS_CLASS && SPI
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_CLASS && HAVE_PWM
|
|
|
|
|
help
|
|
|
|
|
This option enables support for pwm driven LEDs
|
|
|
|
|
|
2009-03-05 03:59:29 +08:00
|
|
|
config LEDS_BD2802
|
|
|
|
|
tristate "LED driver for BD2802 RGB LED"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for BD2802GU RGB LED driver chips
|
|
|
|
|
accessed via the I2C bus.
|
|
|
|
|
|
2006-04-11 13:54:01 +08:00
|
|
|
comment "LED Triggers"
|
|
|
|
|
|
|
|
|
|
config LEDS_TRIGGERS
|
|
|
|
|
bool "LED Trigger support"
|
|
|
|
|
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.
|
|
|
|
|
|
2006-03-31 18:31:07 +08:00
|
|
|
config LEDS_TRIGGER_TIMER
|
|
|
|
|
tristate "LED Timer Trigger"
|
2006-12-13 03:04:19 +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.
|
|
|
|
|
For more details read Documentation/leds-class.txt.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2006-03-31 18:31:07 +08:00
|
|
|
|
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"
|
2008-10-18 00:09:14 +08:00
|
|
|
depends on LEDS_TRIGGERS && IDE_GD_ATA
|
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"
|
2006-12-13 03:04:19 +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"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
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.
|
|
|
|
|
|
2009-02-17 19:18:11 +08:00
|
|
|
config LEDS_TRIGGER_GPIO
|
|
|
|
|
tristate "LED GPIO Trigger"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
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"
|
|
|
|
|
depends on LEDS_TRIGGERS
|
|
|
|
|
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
|
|
|
|
|
|
2007-05-10 17:44:11 +08:00
|
|
|
endif # NEW_LEDS
|
