2019-05-19 19:07:45 +07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2011-06-16 05:08:31 +07: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 16:44:11 +07:00
|
|
|
menuconfig NEW_LEDS
|
2006-03-31 17:31:04 +07:00
|
|
|
bool "LED Support"
|
|
|
|
|
help
|
2006-05-15 23:44:14 +07:00
|
|
|
Say Y to enable Linux LED support. This allows control of supported
|
|
|
|
|
LEDs from both userspace and optionally, by kernel events (triggers).
|
|
|
|
|
|
2011-06-16 05:08:40 +07:00
|
|
|
if NEW_LEDS
|
|
|
|
|
|
2006-03-31 17:31:04 +07:00
|
|
|
config LEDS_CLASS
|
2012-03-24 05:02:14 +07:00
|
|
|
tristate "LED Class Support"
|
2006-03-31 17:31:04 +07: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.
|
|
|
|
|
|
2015-01-09 22:22:51 +07:00
|
|
|
config LEDS_CLASS_FLASH
|
|
|
|
|
tristate "LED Flash Class Support"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
help
|
2019-04-04 01:19:22 +07:00
|
|
|
This option enables the flash LED sysfs class in /sys/class/leds.
|
|
|
|
|
It wraps LED Class and adds flash LEDs specific sysfs attributes
|
2015-01-09 22:22:51 +07:00
|
|
|
and kernel internal API to it. You'll need this to provide support
|
|
|
|
|
for the flash related features of a LED device. It can be built
|
|
|
|
|
as a module.
|
|
|
|
|
|
2017-01-29 20:42:52 +07:00
|
|
|
config LEDS_BRIGHTNESS_HW_CHANGED
|
|
|
|
|
bool "LED Class brightness_hw_changed attribute support"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the brightness_hw_changed attribute
|
|
|
|
|
for led sysfs class devices under /sys/class/leds.
|
|
|
|
|
|
|
|
|
|
See Documentation/ABI/testing/sysfs-class-led for details.
|
|
|
|
|
|
2006-04-11 12:54:01 +07:00
|
|
|
comment "LED drivers"
|
2006-03-31 17:31:05 +07:00
|
|
|
|
2010-01-07 05:10:09 +07:00
|
|
|
config LEDS_88PM860X
|
|
|
|
|
tristate "LED Support for Marvell 88PM860x PMIC"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-05-27 19:08:33 +07:00
|
|
|
depends on MFD_88PM860X
|
2010-01-07 05:10:09 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found on Marvell
|
|
|
|
|
Semiconductor 88PM8606 PMIC.
|
|
|
|
|
|
2015-04-30 17:34:57 +07:00
|
|
|
config LEDS_AAT1290
|
|
|
|
|
tristate "LED support for the AAT1290"
|
|
|
|
|
depends on LEDS_CLASS_FLASH
|
2015-06-27 02:00:20 +07:00
|
|
|
depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS
|
2015-07-06 20:42:34 +07:00
|
|
|
depends on GPIOLIB || COMPILE_TEST
|
2015-04-30 17:34:57 +07:00
|
|
|
depends on OF
|
2015-06-19 14:33:22 +07:00
|
|
|
depends on PINCTRL
|
2015-04-30 17:34:57 +07:00
|
|
|
help
|
2019-03-07 01:15:46 +07:00
|
|
|
This option enables support for the LEDs on the AAT1290.
|
2018-06-25 19:50:02 +07:00
|
|
|
|
2018-09-09 17:38:25 +07:00
|
|
|
config LEDS_AN30259A
|
|
|
|
|
tristate "LED support for Panasonic AN30259A"
|
|
|
|
|
depends on LEDS_CLASS && I2C && OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the AN30259A 3-channel
|
|
|
|
|
LED driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called leds-an30259a.
|
|
|
|
|
|
2017-11-03 08:38:07 +07:00
|
|
|
config LEDS_APU
|
2018-06-25 19:50:02 +07:00
|
|
|
tristate "Front panel LED support for PC Engines APU/APU2/APU3 boards"
|
2017-11-03 08:38:07 +07:00
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on X86 && DMI
|
|
|
|
|
help
|
2019-07-15 21:57:28 +07:00
|
|
|
This driver makes the PC Engines APU1 front panel LEDs
|
2017-11-03 08:38:07 +07:00
|
|
|
accessible from userspace programs through the LED subsystem.
|
|
|
|
|
|
2019-07-15 21:57:28 +07:00
|
|
|
If you're looking for APU2/3, use the pcengines-apu2 driver.
|
|
|
|
|
(symbol CONFIG_PCENGINES_APU2)
|
|
|
|
|
|
2017-11-03 08:38:07 +07:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called leds-apu.
|
2015-04-30 17:34:57 +07:00
|
|
|
|
2015-04-27 04:56:54 +07:00
|
|
|
config LEDS_AS3645A
|
2018-02-02 03:26:34 +07:00
|
|
|
tristate "AS3645A and LM3555 LED flash controllers support"
|
2015-04-27 04:56:54 +07:00
|
|
|
depends on I2C && LEDS_CLASS_FLASH
|
2017-09-05 14:13:20 +07:00
|
|
|
depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS
|
2015-04-27 04:56:54 +07:00
|
|
|
help
|
|
|
|
|
Enable LED flash class support for AS3645A LED flash
|
|
|
|
|
controller. V4L2 flash API is provided as well if
|
|
|
|
|
CONFIG_V4L2_FLASH_API is enabled.
|
|
|
|
|
|
2015-04-28 23:50:50 +07:00
|
|
|
config LEDS_BCM6328
|
|
|
|
|
tristate "LED Support for Broadcom BCM6328"
|
|
|
|
|
depends on LEDS_CLASS
|
2016-01-02 20:05:49 +07:00
|
|
|
depends on HAS_IOMEM
|
2015-04-28 23:50:50 +07:00
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to the BCM6328
|
|
|
|
|
LED HW controller accessed via MMIO registers.
|
|
|
|
|
|
2015-05-22 00:11:10 +07:00
|
|
|
config LEDS_BCM6358
|
|
|
|
|
tristate "LED Support for Broadcom BCM6358"
|
|
|
|
|
depends on LEDS_CLASS
|
2016-01-02 20:05:49 +07:00
|
|
|
depends on HAS_IOMEM
|
2015-05-22 00:11:10 +07:00
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to the BCM6358
|
|
|
|
|
LED HW controller accessed via MMIO registers.
|
|
|
|
|
|
2017-03-24 15:47:32 +07:00
|
|
|
config LEDS_CPCAP
|
|
|
|
|
tristate "LED Support for Motorola CPCAP"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on MFD_CPCAP
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs offered by Motorola's
|
|
|
|
|
CPCAP PMIC.
|
|
|
|
|
|
2018-04-02 19:53:50 +07:00
|
|
|
config LEDS_CR0014114
|
|
|
|
|
tristate "LED Support for Crane CR0014114"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on SPI
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for CR0014114 LED Board which
|
|
|
|
|
is widely used in vending machines produced by
|
|
|
|
|
Crane Merchandising Systems.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called leds-cr0014114.
|
|
|
|
|
|
2011-03-23 06:30:16 +07: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.
|
|
|
|
|
|
2019-03-21 21:28:38 +07:00
|
|
|
config LEDS_LM3532
|
|
|
|
|
tristate "LCD Backlight driver for LM3532"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the LCD backlight using
|
|
|
|
|
LM3532 ambient light sensor chip. This ALS chip can be
|
|
|
|
|
controlled manually or using PWM input or using ambient
|
|
|
|
|
light automatically.
|
|
|
|
|
|
2012-05-30 05:07:31 +07: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 19:05:50 +07: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.
|
|
|
|
|
|
2017-12-13 01:15:50 +07:00
|
|
|
config LEDS_LM3692X
|
|
|
|
|
tristate "LED support for LM3692x Chips"
|
|
|
|
|
depends on LEDS_CLASS && I2C && OF
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the TI LM3692x family
|
|
|
|
|
of white LED string drivers used for backlighting.
|
2012-09-12 19:05:50 +07:00
|
|
|
|
2018-05-23 18:51:29 +07:00
|
|
|
config LEDS_LM3601X
|
|
|
|
|
tristate "LED support for LM3601x Chips"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
depends on LEDS_CLASS_FLASH
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the TI LM3601x family
|
|
|
|
|
of flash, torch and indicator classes.
|
|
|
|
|
|
2006-03-31 17:31:10 +07:00
|
|
|
config LEDS_LOCOMO
|
|
|
|
|
tristate "LED Support for Locomo device"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on SHARP_LOCOMO
|
2006-03-31 17:31:10 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on Sharp Locomo.
|
|
|
|
|
Zaurus models SL-5500 and SL-5600.
|
|
|
|
|
|
2009-01-23 01:35:48 +07:00
|
|
|
config LEDS_MIKROTIK_RB532
|
|
|
|
|
tristate "LED Support for Mikrotik Routerboard 532"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on MIKROTIK_RB532
|
2009-01-23 01:35:48 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the so called "User LED" of
|
|
|
|
|
Mikrotik's Routerboard 532.
|
|
|
|
|
|
2017-03-20 13:47:26 +07:00
|
|
|
config LEDS_MT6323
|
|
|
|
|
tristate "LED Support for Mediatek MT6323 PMIC"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on MFD_MT6397
|
|
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found on
|
|
|
|
|
Mediatek MT6323 PMIC.
|
|
|
|
|
|
2006-04-11 12:54:00 +07:00
|
|
|
config LEDS_S3C24XX
|
|
|
|
|
tristate "LED Support for Samsung S3C24XX GPIO LEDs"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2012-02-03 12:29:23 +07:00
|
|
|
depends on ARCH_S3C24XX
|
2006-04-11 12:54:00 +07: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 18:45:34 +07:00
|
|
|
config LEDS_NET48XX
|
|
|
|
|
tristate "LED Support for Soekris net48xx series Error LED"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on SCx200_GPIO
|
2006-07-10 18:45:34 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the Soekris net4801 and net4826 error
|
|
|
|
|
LED.
|
|
|
|
|
|
2008-04-25 05:43:09 +07:00
|
|
|
config LEDS_FSG
|
|
|
|
|
tristate "LED Support for the Freecom FSG-3"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on MACH_FSG
|
2008-04-25 05:43:09 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the Freecom FSG-3.
|
|
|
|
|
|
2006-12-07 11:37:28 +07:00
|
|
|
config LEDS_WRAP
|
|
|
|
|
tristate "LED Support for the WRAP series LEDs"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on SCx200_GPIO
|
2006-12-07 11:37:28 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the PCEngines WRAP programmable LEDs.
|
|
|
|
|
|
2007-09-21 06:02:47 +07:00
|
|
|
config LEDS_COBALT_QUBE
|
|
|
|
|
tristate "LED Support for the Cobalt Qube series front LED"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on MIPS_COBALT
|
2007-02-13 06:16:27 +07:00
|
|
|
help
|
2007-09-21 06:02:47 +07:00
|
|
|
This option enables support for the front LED on Cobalt Qube series
|
2007-02-13 06:16:27 +07:00
|
|
|
|
2007-09-27 15:51:05 +07:00
|
|
|
config LEDS_COBALT_RAQ
|
|
|
|
|
bool "LED Support for the Cobalt Raq series"
|
2008-12-03 15:09:28 +07:00
|
|
|
depends on LEDS_CLASS=y && MIPS_COBALT
|
2007-09-27 15:51:05 +07:00
|
|
|
select LEDS_TRIGGERS
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the Cobalt Raq series LEDs.
|
|
|
|
|
|
2008-09-01 10:26:48 +07:00
|
|
|
config LEDS_SUNFIRE
|
|
|
|
|
tristate "LED support for SunFire servers."
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on SPARC64
|
2008-09-01 10:26:48 +07: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.
|
|
|
|
|
|
2014-07-23 19:36:00 +07:00
|
|
|
config LEDS_IPAQ_MICRO
|
|
|
|
|
tristate "LED Support for the Compaq iPAQ h3xxx"
|
2015-09-07 22:06:05 +07:00
|
|
|
depends on LEDS_CLASS
|
2014-07-23 19:36:00 +07:00
|
|
|
depends on MFD_IPAQ_MICRO
|
|
|
|
|
help
|
|
|
|
|
Choose this option if you want to use the notification LED on
|
|
|
|
|
Compaq/HP iPAQ h3100 and h3600.
|
|
|
|
|
|
2008-02-07 17:10:28 +07:00
|
|
|
config LEDS_HP6XX
|
|
|
|
|
tristate "LED Support for the HP Jornada 6xx"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on SH_HP6XX
|
2008-02-07 17:10:28 +07:00
|
|
|
help
|
2009-01-26 17:12:25 +07:00
|
|
|
This option enables LED support for the handheld
|
2008-02-07 17:10:28 +07:00
|
|
|
HP Jornada 620/660/680/690.
|
|
|
|
|
|
2008-05-31 20:43:41 +07:00
|
|
|
config LEDS_PCA9532
|
|
|
|
|
tristate "LED driver for PCA9532 dimmer"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2013-01-17 09:53:41 +07:00
|
|
|
depends on I2C && INPUT
|
2008-05-31 20:43:41 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for NXP pca9532
|
2009-01-26 17:12:25 +07:00
|
|
|
LED controller. It is generally only useful
|
2008-05-31 20:43:41 +07:00
|
|
|
as a platform driver
|
|
|
|
|
|
2011-05-25 07:13:23 +07: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 02:49:53 +07:00
|
|
|
config LEDS_GPIO
|
|
|
|
|
tristate "LED Support for GPIO connected LEDs"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2015-05-07 15:08:10 +07:00
|
|
|
depends on GPIOLIB || COMPILE_TEST
|
2007-02-28 02:49:53 +07: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 00:26:01 +07: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 18:55:42 +07:00
|
|
|
config LEDS_LP3944
|
|
|
|
|
tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on I2C
|
2009-06-19 18:55:42 +07:00
|
|
|
help
|
2009-07-03 21:18:45 +07: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 18:55:42 +07:00
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called leds-lp3944.
|
|
|
|
|
|
2016-07-11 17:48:49 +07:00
|
|
|
config LEDS_LP3952
|
|
|
|
|
tristate "LED Support for TI LP3952 2 channel LED driver"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on I2C
|
|
|
|
|
depends on GPIOLIB
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to the Texas
|
|
|
|
|
Instruments LP3952 LED driver.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called leds-lp3952.
|
|
|
|
|
|
2013-02-05 16:01:23 +07:00
|
|
|
config LEDS_LP55XX_COMMON
|
2013-07-09 16:11:37 +07:00
|
|
|
tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501"
|
|
|
|
|
depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501
|
2013-02-05 17:17:20 +07:00
|
|
|
select FW_LOADER
|
2015-09-07 19:25:01 +07:00
|
|
|
select FW_LOADER_USER_HELPER
|
2013-02-05 16:01:23 +07:00
|
|
|
help
|
2013-07-09 16:11:37 +07:00
|
|
|
This option supports common operations for LP5521/5523/55231/5562/8501
|
2013-02-05 16:01:23 +07:00
|
|
|
devices.
|
|
|
|
|
|
2010-11-12 05:05:23 +07:00
|
|
|
config LEDS_LP5521
|
|
|
|
|
tristate "LED Support for N.S. LP5521 LED driver chip"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
2013-02-05 16:01:23 +07:00
|
|
|
select LEDS_LP55XX_COMMON
|
2010-11-12 05:05:23 +07: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 14:06:11 +07:00
|
|
|
tristate "LED Support for TI/National LP5523/55231 LED driver chip"
|
2010-11-12 05:05:23 +07:00
|
|
|
depends on LEDS_CLASS && I2C
|
2013-02-05 16:01:23 +07:00
|
|
|
select LEDS_LP55XX_COMMON
|
2010-11-12 05:05:23 +07:00
|
|
|
help
|
2012-09-04 14:06:11 +07: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 05:05:23 +07:00
|
|
|
Driver provides direct control via LED class and interface for
|
|
|
|
|
programming the engines.
|
|
|
|
|
|
2013-02-19 12:10:14 +07:00
|
|
|
config LEDS_LP5562
|
|
|
|
|
tristate "LED Support for TI LP5562 LED driver chip"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
select LEDS_LP55XX_COMMON
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for TI LP5562 LED driver.
|
|
|
|
|
It is 4 channels chip with programmable engines.
|
|
|
|
|
Driver provides direct control via LED class and interface for
|
|
|
|
|
programming the engines.
|
|
|
|
|
|
2013-07-09 16:11:37 +07:00
|
|
|
config LEDS_LP8501
|
|
|
|
|
tristate "LED Support for TI LP8501 LED driver chip"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
select LEDS_LP55XX_COMMON
|
|
|
|
|
help
|
|
|
|
|
If you say yes here you get support for TI LP8501 LED driver.
|
|
|
|
|
It is 9 channel chip with programmable engines.
|
|
|
|
|
Driver provides direct control via LED class and interface for
|
|
|
|
|
programming the engines.
|
|
|
|
|
It is similar as LP5523, but output power selection is available.
|
|
|
|
|
And register layout and engine program schemes are different.
|
|
|
|
|
|
2012-07-20 15:43:59 +07: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.
|
|
|
|
|
|
2014-11-19 19:48:35 +07:00
|
|
|
config LEDS_LP8860
|
|
|
|
|
tristate "LED support for the TI LP8860 4 channel LED driver"
|
2017-12-19 03:23:07 +07:00
|
|
|
depends on LEDS_CLASS && I2C && OF
|
2014-11-21 20:48:26 +07:00
|
|
|
select REGMAP_I2C
|
2014-11-19 19:48:35 +07:00
|
|
|
help
|
|
|
|
|
If you say yes here you get support for the TI LP8860 4 channel
|
|
|
|
|
LED driver.
|
|
|
|
|
This option enables support for the display cluster LEDs
|
|
|
|
|
on the LP8860 4 channel LED driver using the I2C communication
|
|
|
|
|
bus.
|
|
|
|
|
|
2007-10-31 17:46:41 +07:00
|
|
|
config LEDS_CLEVO_MAIL
|
2009-04-03 12:42:47 +07:00
|
|
|
tristate "Mail LED on Clevo notebook"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on X86 && SERIO_I8042 && DMI
|
2007-10-31 17:46:41 +07: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 21:09:05 +07: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 17:46:41 +07:00
|
|
|
|
|
|
|
|
This module can drive the mail LED for the following notebooks:
|
|
|
|
|
|
2019-03-07 01:15:46 +07:00
|
|
|
Clevo D400P
|
|
|
|
|
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)
|
2007-10-31 17:46:41 +07:00
|
|
|
|
2008-03-10 03:47:59 +07:00
|
|
|
If your model is not listed here you can try the "nodetect"
|
2009-01-26 17:12:25 +07:00
|
|
|
module parameter.
|
2008-03-10 03:47:59 +07:00
|
|
|
|
2007-10-31 17:46:41 +07:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called leds-clevo-mail.
|
|
|
|
|
|
2008-07-17 04:49:55 +07:00
|
|
|
config LEDS_PCA955X
|
|
|
|
|
tristate "LED Support for PCA955x I2C chips"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on I2C
|
2008-07-17 04:49:55 +07: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.
|
|
|
|
|
|
2017-08-08 20:42:39 +07:00
|
|
|
config LEDS_PCA955X_GPIO
|
|
|
|
|
bool "Enable GPIO support for PCA955X"
|
|
|
|
|
depends on LEDS_PCA955X
|
|
|
|
|
depends on GPIOLIB
|
|
|
|
|
help
|
|
|
|
|
Allow unused pins on PCA955X to be used as gpio.
|
|
|
|
|
|
|
|
|
|
To use a pin as gpio the pin type should be set to
|
|
|
|
|
PCA955X_TYPE_GPIO in the device tree.
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 04:23:50 +07:00
|
|
|
config LEDS_PCA963X
|
2013-08-15 04:23:47 +07:00
|
|
|
tristate "LED support for PCA963x I2C chip"
|
2012-03-24 05:02:10 +07:00
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on I2C
|
|
|
|
|
help
|
2013-08-15 04:23:47 +07:00
|
|
|
This option enables support for LEDs connected to the PCA963x
|
|
|
|
|
LED driver chip accessed via the I2C bus. Supported
|
|
|
|
|
devices include PCA9633 and PCA9634
|
2012-03-24 05:02:10 +07:00
|
|
|
|
2009-09-05 20:09:21 +07:00
|
|
|
config LEDS_WM831X_STATUS
|
|
|
|
|
tristate "LED support for status LEDs on WM831x PMICs"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on MFD_WM831X
|
2009-09-05 20:09:21 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the status LEDs of the WM831x
|
2019-03-07 01:15:46 +07:00
|
|
|
series of PMICs.
|
2009-09-05 20:09:21 +07:00
|
|
|
|
2008-12-04 23:52:33 +07:00
|
|
|
config LEDS_WM8350
|
|
|
|
|
tristate "LED Support for WM8350 AudioPlus PMIC"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on MFD_WM8350
|
2008-12-04 23:52:33 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for LEDs driven by the Wolfson
|
|
|
|
|
Microelectronics WM8350 AudioPlus PMIC.
|
|
|
|
|
|
2008-10-13 15:06:10 +07:00
|
|
|
config LEDS_DA903X
|
|
|
|
|
tristate "LED Support for DA9030/DA9034 PMIC"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on PMIC_DA903X
|
2008-10-13 15:06:10 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for on-chip LED drivers found
|
|
|
|
|
on Dialog Semiconductor DA9030/DA9034 PMICs.
|
|
|
|
|
|
2012-05-30 05:07:26 +07: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 01:58:28 +07:00
|
|
|
config LEDS_DAC124S085
|
|
|
|
|
tristate "LED Support for DAC124S085 SPI DAC"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on SPI
|
2009-01-11 01:58:28 +07: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 04:24:40 +07:00
|
|
|
config LEDS_PWM
|
|
|
|
|
tristate "PWM driven LED Support"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2013-01-23 15:35:04 +07:00
|
|
|
depends on PWM
|
2009-02-12 04:24:40 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for pwm driven LEDs
|
|
|
|
|
|
2009-12-07 21:08:13 +07:00
|
|
|
config LEDS_REGULATOR
|
|
|
|
|
tristate "REGULATOR driven LED support"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on REGULATOR
|
2009-12-07 21:08:13 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for regulator driven LEDs.
|
|
|
|
|
|
2009-03-05 02:59:29 +07:00
|
|
|
config LEDS_BD2802
|
|
|
|
|
tristate "LED driver for BD2802 RGB LED"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on I2C
|
2009-03-05 02:59:29 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for BD2802GU RGB LED driver chips
|
|
|
|
|
accessed via the I2C bus.
|
|
|
|
|
|
2009-10-02 05:43:32 +07:00
|
|
|
config LEDS_INTEL_SS4200
|
|
|
|
|
tristate "LED driver for Intel NAS SS4200 series"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on PCI && DMI
|
2016-04-17 18:27:52 +07:00
|
|
|
depends on X86
|
2009-10-02 05:43:32 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the Intel SS4200 series of
|
2016-04-17 18:27:52 +07:00
|
|
|
Network Attached Storage servers. You may control the hard
|
|
|
|
|
drive or power LEDs on the front panel. Using this driver
|
2009-10-02 05:43:32 +07:00
|
|
|
can stop the front LED from blinking after startup.
|
|
|
|
|
|
2009-10-15 07:59:35 +07:00
|
|
|
config LEDS_LT3593
|
|
|
|
|
tristate "LED driver for LT3593 controllers"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2015-05-05 23:32:25 +07:00
|
|
|
depends on GPIOLIB || COMPILE_TEST
|
2019-03-21 04:52:27 +07:00
|
|
|
depends on OF
|
2009-10-15 07:59:35 +07: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 15:00:19 +07:00
|
|
|
config LEDS_ADP5520
|
|
|
|
|
tristate "LED Support for ADP5520/ADP5501 PMIC"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2010-01-21 06:08:30 +07:00
|
|
|
depends on PMIC_ADP5520
|
2009-10-08 15:00:19 +07: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-05-19 14:24:31 +07:00
|
|
|
config LEDS_MC13783
|
2013-06-10 23:59:31 +07:00
|
|
|
tristate "LED Support for MC13XXX PMIC"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2013-06-10 23:59:31 +07:00
|
|
|
depends on MFD_MC13XXX
|
2010-05-19 14:24:31 +07:00
|
|
|
help
|
2018-02-16 01:11:37 +07:00
|
|
|
This option enables support for on-chip LED drivers found
|
2014-02-01 13:36:28 +07:00
|
|
|
on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC.
|
2010-05-19 14:24:31 +07:00
|
|
|
|
2010-07-06 21:08:46 +07:00
|
|
|
config LEDS_NS2
|
|
|
|
|
tristate "LED support for Network Space v2 GPIO LEDs"
|
2010-12-03 05:31:14 +07:00
|
|
|
depends on LEDS_CLASS
|
2015-07-03 00:56:43 +07:00
|
|
|
depends on MACH_KIRKWOOD || MACH_ARMADA_370
|
2010-07-06 21:08:46 +07:00
|
|
|
default y
|
|
|
|
|
help
|
2015-07-03 00:56:43 +07:00
|
|
|
This option enables support for the dual-GPIO LEDs found on the
|
|
|
|
|
following LaCie/Seagate boards:
|
|
|
|
|
|
|
|
|
|
Network Space v2 (and parents: Max, Mini)
|
|
|
|
|
Internet Space v2
|
|
|
|
|
d2 Network v2
|
|
|
|
|
n090401 (Seagate NAS 4-Bay)
|
2010-07-06 21:08:46 +07:00
|
|
|
|
2010-10-07 21:38:49 +07:00
|
|
|
config LEDS_NETXBIG
|
|
|
|
|
tristate "LED support for Big Network series LEDs"
|
2011-07-26 07:13:16 +07:00
|
|
|
depends on LEDS_CLASS
|
2014-08-30 23:46:09 +07:00
|
|
|
depends on MACH_KIRKWOOD
|
2019-07-28 23:40:15 +07:00
|
|
|
depends on OF_GPIO
|
2010-10-07 21:38:49 +07:00
|
|
|
default y
|
|
|
|
|
help
|
2018-02-16 01:11:37 +07:00
|
|
|
This option enables support for LEDs found on the LaCie 2Big
|
2010-10-07 21:38:49 +07:00
|
|
|
and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
|
|
|
|
|
controlled through a GPIO extension bus.
|
|
|
|
|
|
2011-05-14 01:52:56 +07:00
|
|
|
config LEDS_ASIC3
|
|
|
|
|
bool "LED support for the HTC ASIC3"
|
2012-06-09 06:41:42 +07:00
|
|
|
depends on LEDS_CLASS=y
|
2011-05-14 01:52:56 +07: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.
|
|
|
|
|
|
2012-01-11 06:09:40 +07: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.
|
|
|
|
|
|
2015-03-18 05:08:27 +07:00
|
|
|
config LEDS_TLC591XX
|
|
|
|
|
tristate "LED driver for TLC59108 and TLC59116 controllers"
|
|
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for Texas Instruments TLC59108
|
|
|
|
|
and TLC59116 LED controllers.
|
|
|
|
|
|
2019-04-23 16:04:49 +07:00
|
|
|
config LEDS_MAX77650
|
|
|
|
|
tristate "LED support for Maxim MAX77650 PMIC"
|
|
|
|
|
depends on LEDS_CLASS && MFD_MAX77650
|
|
|
|
|
help
|
|
|
|
|
LEDs driver for MAX77650 family of PMICs from Maxim Integrated.
|
|
|
|
|
|
2015-04-30 17:35:10 +07:00
|
|
|
config LEDS_MAX77693
|
|
|
|
|
tristate "LED support for MAX77693 Flash"
|
|
|
|
|
depends on LEDS_CLASS_FLASH
|
2015-06-29 21:45:23 +07:00
|
|
|
depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS
|
2015-04-30 17:35:10 +07:00
|
|
|
depends on MFD_MAX77693
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the flash part of the MAX77693
|
|
|
|
|
multifunction device. It has build in control for two leds in flash
|
|
|
|
|
and torch mode.
|
|
|
|
|
|
2011-12-14 16:23:56 +07: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 14:05:58 +07:00
|
|
|
config LEDS_LM355x
|
2018-02-02 03:26:34 +07:00
|
|
|
tristate "LED support for LM3554 and LM3556 chips"
|
2012-06-22 07:12:06 +07:00
|
|
|
depends on LEDS_CLASS && I2C
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
2018-02-02 03:26:34 +07:00
|
|
|
This option enables support for LEDs connected to LM3554
|
|
|
|
|
and LM3556. It includes Torch, Flash and Indicator functions.
|
2012-06-22 07:12:06 +07:00
|
|
|
|
2012-01-21 05:33:59 +07:00
|
|
|
config LEDS_OT200
|
|
|
|
|
tristate "LED support for the Bachmann OT200"
|
2014-03-11 23:30:53 +07:00
|
|
|
depends on LEDS_CLASS && HAS_IOMEM && (X86_32 || COMPILE_TEST)
|
2012-01-21 05:33:59 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the Bachmann OT200.
|
|
|
|
|
Say Y to enable LEDs on the Bachmann OT200.
|
|
|
|
|
|
2014-08-28 00:52:36 +07:00
|
|
|
config LEDS_MENF21BMC
|
|
|
|
|
tristate "LED support for the MEN 14F021P00 BMC"
|
|
|
|
|
depends on LEDS_CLASS && MFD_MENF21BMC
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include support for the MEN 14F021P00 BMC LEDs.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so the module
|
|
|
|
|
will be called leds-menf21bmc.
|
|
|
|
|
|
2015-05-12 15:37:57 +07:00
|
|
|
config LEDS_KTD2692
|
|
|
|
|
tristate "LED support for KTD2692 flash LED controller"
|
2015-07-06 20:42:34 +07:00
|
|
|
depends on LEDS_CLASS_FLASH && OF
|
|
|
|
|
depends on GPIOLIB || COMPILE_TEST
|
2015-05-12 15:37:57 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for KTD2692 LED flash connected
|
|
|
|
|
through ExpressWire interface.
|
|
|
|
|
|
|
|
|
|
Say Y to enable this driver.
|
|
|
|
|
|
2016-07-19 18:47:30 +07:00
|
|
|
config LEDS_IS31FL319X
|
|
|
|
|
tristate "LED Support for ISSI IS31FL319x I2C LED controller family"
|
|
|
|
|
depends on LEDS_CLASS && I2C && OF
|
|
|
|
|
select REGMAP_I2C
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LEDs connected to ISSI IS31FL319x
|
|
|
|
|
fancy LED driver chips accessed via the I2C bus.
|
|
|
|
|
Driver supports individual PWM brightness control for each channel.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so the module will be
|
|
|
|
|
called leds-is31fl319x.
|
|
|
|
|
|
leds: Add driver for the ISSI IS31FL32xx family of LED controllers
The IS31FL32xx family of LED controllers are I2C devices with multiple
constant-current channels, each with independent 256-level PWM control.
Datasheets: http://www.issi.com/US/product-analog-fxled-driver.shtml
This has been tested on the IS31FL3236 and IS31FL3216, on an ARM
(TI am335x) platform.
The programming paradigm of these devices is similar in the following
ways:
- All registers are 8 bit
- All LED control registers are write-only
- Each LED channel has a PWM register (0-255)
- PWM register writes are shadowed until an Update register is poked
- All have a concept of Software Shutdown, which disables output
However, there are some differences in devices:
- 3236/3235 have a separate Control register for each LED,
(3218/3216 pack the enable bits into fewer registers)
- 3236/3235 have a per-channel current divisor setting
- 3236/3235 have a Global Control register that can turn off all LEDs
- 3216 is unique in a number of ways
- OUT9-OUT16 can be configured as GPIOs instead of LED controls
- LEDs can be programmed with an 8-frame animation, with
programmable delay between frames
- LEDs can be modulated by an input audio signal
- Max output current can be adjusted from 1/4 to 2x globally
- Has a Configuration register instead of a Shutdown register
This driver currently only supports the base PWM control function
of these devices. The following features of these devices are not
implemented, although it should be possible to add them in the future:
- All devices are capable of going into a lower-power "software
shutdown" mode.
- The is31fl3236 and is31fl3235 can reduce the max output current
per-channel with a divisor of 1, 2, 3, or 4.
- The is31fl3216 can use some LED channels as GPIOs instead.
- The is31fl3216 can animate LEDs in hardware.
- The is31fl3216 can modulate LEDs according to an audio input.
- The is31fl3216 can reduce/increase max output current globally.
Signed-off-by: David Rivshin <drivshin@allworx.com>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
2016-03-08 07:57:15 +07:00
|
|
|
config LEDS_IS31FL32XX
|
|
|
|
|
tristate "LED support for ISSI IS31FL32XX I2C LED controller family"
|
|
|
|
|
depends on LEDS_CLASS && I2C && OF
|
|
|
|
|
help
|
2016-03-08 07:57:16 +07:00
|
|
|
Say Y here to include support for ISSI IS31FL32XX and Si-En SN32xx
|
|
|
|
|
LED controllers. They are I2C devices with multiple constant-current
|
|
|
|
|
channels, each with independent 256-level PWM control.
|
leds: Add driver for the ISSI IS31FL32xx family of LED controllers
The IS31FL32xx family of LED controllers are I2C devices with multiple
constant-current channels, each with independent 256-level PWM control.
Datasheets: http://www.issi.com/US/product-analog-fxled-driver.shtml
This has been tested on the IS31FL3236 and IS31FL3216, on an ARM
(TI am335x) platform.
The programming paradigm of these devices is similar in the following
ways:
- All registers are 8 bit
- All LED control registers are write-only
- Each LED channel has a PWM register (0-255)
- PWM register writes are shadowed until an Update register is poked
- All have a concept of Software Shutdown, which disables output
However, there are some differences in devices:
- 3236/3235 have a separate Control register for each LED,
(3218/3216 pack the enable bits into fewer registers)
- 3236/3235 have a per-channel current divisor setting
- 3236/3235 have a Global Control register that can turn off all LEDs
- 3216 is unique in a number of ways
- OUT9-OUT16 can be configured as GPIOs instead of LED controls
- LEDs can be programmed with an 8-frame animation, with
programmable delay between frames
- LEDs can be modulated by an input audio signal
- Max output current can be adjusted from 1/4 to 2x globally
- Has a Configuration register instead of a Shutdown register
This driver currently only supports the base PWM control function
of these devices. The following features of these devices are not
implemented, although it should be possible to add them in the future:
- All devices are capable of going into a lower-power "software
shutdown" mode.
- The is31fl3236 and is31fl3235 can reduce the max output current
per-channel with a divisor of 1, 2, 3, or 4.
- The is31fl3216 can use some LED channels as GPIOs instead.
- The is31fl3216 can animate LEDs in hardware.
- The is31fl3216 can modulate LEDs according to an audio input.
- The is31fl3216 can reduce/increase max output current globally.
Signed-off-by: David Rivshin <drivshin@allworx.com>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
2016-03-08 07:57:15 +07:00
|
|
|
|
2018-05-14 13:34:51 +07:00
|
|
|
config LEDS_SC27XX_BLTC
|
|
|
|
|
tristate "LED support for the SC27xx breathing light controller"
|
|
|
|
|
depends on LEDS_CLASS && MFD_SC27XX_PMIC
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include support for the SC27xx breathing light controller
|
|
|
|
|
LEDs.
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so the module will be
|
|
|
|
|
called leds-sc27xx-bltc.
|
|
|
|
|
|
2014-04-15 03:50:19 +07:00
|
|
|
comment "LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)"
|
|
|
|
|
|
2012-07-20 15:49:06 +07: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.
|
|
|
|
|
|
2015-08-19 23:49:54 +07:00
|
|
|
config LEDS_POWERNV
|
|
|
|
|
tristate "LED support for PowerNV Platform"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on PPC_POWERNV
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the system LEDs present on
|
|
|
|
|
PowerNV platforms. Say 'y' to enable this support in kernel.
|
|
|
|
|
To compile this driver as a module, choose 'm' here: the module
|
|
|
|
|
will be called leds-powernv.
|
|
|
|
|
|
2014-05-22 05:34:16 +07:00
|
|
|
config LEDS_SYSCON
|
|
|
|
|
bool "LED support for LEDs on system controllers"
|
|
|
|
|
depends on LEDS_CLASS=y
|
|
|
|
|
depends on MFD_SYSCON
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
2018-02-16 01:11:37 +07:00
|
|
|
This option enables support for the LEDs on syscon type
|
2014-05-22 05:34:16 +07:00
|
|
|
devices. This will only work with device tree enabled
|
|
|
|
|
devices.
|
|
|
|
|
|
2016-08-16 16:25:10 +07:00
|
|
|
config LEDS_PM8058
|
|
|
|
|
tristate "LED Support for the Qualcomm PM8058 PMIC"
|
2016-11-19 22:15:18 +07:00
|
|
|
depends on MFD_PM8XXX
|
2016-08-16 16:25:10 +07:00
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
help
|
|
|
|
|
Choose this option if you want to use the LED drivers in
|
|
|
|
|
the Qualcomm PM8058 PMIC.
|
|
|
|
|
|
leds: add driver for Mellanox systems LEDs
This makes it possible to create a set of LEDs for Mellanox systems:
"msx6710", "msx6720", "msb7700", "msn2700", "msx1410", "msn2410",
"msb7800", "msn2740", "msn2100".
Driver obtains LED devices according to system configuration, provided
through system DMI data, like mlxcpld:fan1:green, mlxcpld:fan1:red and
creates devices in form: "devicename:colour:function".
LED setting is controlled through on board CPLD Lattice device.
For setting particular LED off, solid, blink:
echo 0 > /sys/class/leds/mlxcpld\:status\:green/brightness
echo 1 > /sys/class/leds/mlxcpld\:status\:green/brightness
echo timer > /sys/class/leds/mlxcpld\:status\:green/trigger
On module probing all LEDs are set green, on removing - off.
Last setting overwrites previous, f.e. sequence for
changing LED from green - red - green:
echo 1 > /sys/class/leds/mlxcpld\:psu\:green/brightness
echo 1 > /sys/class/leds/mlxcpld\:psu\:red/brightness
echo 1 > /sys/class/leds/mlxcpld\:psu\:green/brightness
Note: LEDs cannot be turned on/off simultaneously.
The Kconfig currently controlling compilation of this code is:
drivers/leds/Kconfig:config LEDS_MLXCPLD
Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
Reviewed-by: Wei Yongjun <weiyongjun1@huawei.com>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
2016-09-08 14:25:53 +07:00
|
|
|
config LEDS_MLXCPLD
|
|
|
|
|
tristate "LED support for the Mellanox boards"
|
2018-02-01 15:10:34 +07:00
|
|
|
depends on X86 && DMI
|
leds: add driver for Mellanox systems LEDs
This makes it possible to create a set of LEDs for Mellanox systems:
"msx6710", "msx6720", "msb7700", "msn2700", "msx1410", "msn2410",
"msb7800", "msn2740", "msn2100".
Driver obtains LED devices according to system configuration, provided
through system DMI data, like mlxcpld:fan1:green, mlxcpld:fan1:red and
creates devices in form: "devicename:colour:function".
LED setting is controlled through on board CPLD Lattice device.
For setting particular LED off, solid, blink:
echo 0 > /sys/class/leds/mlxcpld\:status\:green/brightness
echo 1 > /sys/class/leds/mlxcpld\:status\:green/brightness
echo timer > /sys/class/leds/mlxcpld\:status\:green/trigger
On module probing all LEDs are set green, on removing - off.
Last setting overwrites previous, f.e. sequence for
changing LED from green - red - green:
echo 1 > /sys/class/leds/mlxcpld\:psu\:green/brightness
echo 1 > /sys/class/leds/mlxcpld\:psu\:red/brightness
echo 1 > /sys/class/leds/mlxcpld\:psu\:green/brightness
Note: LEDs cannot be turned on/off simultaneously.
The Kconfig currently controlling compilation of this code is:
drivers/leds/Kconfig:config LEDS_MLXCPLD
Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
Reviewed-by: Wei Yongjun <weiyongjun1@huawei.com>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
2016-09-08 14:25:53 +07:00
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
help
|
2018-02-16 01:11:37 +07:00
|
|
|
This option enables support for the LEDs on the Mellanox
|
|
|
|
|
boards. Say Y to enable these.
|
leds: add driver for Mellanox systems LEDs
This makes it possible to create a set of LEDs for Mellanox systems:
"msx6710", "msx6720", "msb7700", "msn2700", "msx1410", "msn2410",
"msb7800", "msn2740", "msn2100".
Driver obtains LED devices according to system configuration, provided
through system DMI data, like mlxcpld:fan1:green, mlxcpld:fan1:red and
creates devices in form: "devicename:colour:function".
LED setting is controlled through on board CPLD Lattice device.
For setting particular LED off, solid, blink:
echo 0 > /sys/class/leds/mlxcpld\:status\:green/brightness
echo 1 > /sys/class/leds/mlxcpld\:status\:green/brightness
echo timer > /sys/class/leds/mlxcpld\:status\:green/trigger
On module probing all LEDs are set green, on removing - off.
Last setting overwrites previous, f.e. sequence for
changing LED from green - red - green:
echo 1 > /sys/class/leds/mlxcpld\:psu\:green/brightness
echo 1 > /sys/class/leds/mlxcpld\:psu\:red/brightness
echo 1 > /sys/class/leds/mlxcpld\:psu\:green/brightness
Note: LEDs cannot be turned on/off simultaneously.
The Kconfig currently controlling compilation of this code is:
drivers/leds/Kconfig:config LEDS_MLXCPLD
Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
Reviewed-by: Jiri Pirko <jiri@mellanox.com>
Reviewed-by: Wei Yongjun <weiyongjun1@huawei.com>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
2016-09-08 14:25:53 +07:00
|
|
|
|
2018-02-16 06:37:50 +07:00
|
|
|
config LEDS_MLXREG
|
|
|
|
|
tristate "LED support for the Mellanox switches management control"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the LEDs on the Mellanox Ethernet and
|
|
|
|
|
InfiniBand switches. The driver can be activated by the platform device
|
|
|
|
|
device add call. Say Y to enable these. To compile this driver as a
|
|
|
|
|
module, choose 'M' here: the module will be called leds-mlxreg.
|
|
|
|
|
|
2016-09-17 02:16:48 +07:00
|
|
|
config LEDS_USER
|
|
|
|
|
tristate "Userspace LED support"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
help
|
|
|
|
|
This option enables support for userspace LEDs. Say 'y' to enable this
|
|
|
|
|
support in kernel. To compile this driver as a module, choose 'm' here:
|
|
|
|
|
the module will be called uleds.
|
|
|
|
|
|
2016-11-04 12:31:47 +07:00
|
|
|
config LEDS_NIC78BX
|
|
|
|
|
tristate "LED support for NI PXI NIC78bx devices"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on X86 && ACPI
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the User1 and User2 LEDs on NI
|
|
|
|
|
PXI NIC78bx devices.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the module
|
|
|
|
|
will be called leds-nic78bx.
|
|
|
|
|
|
2019-05-14 02:33:07 +07:00
|
|
|
config LEDS_SPI_BYTE
|
|
|
|
|
tristate "LED support for SPI LED controller with a single byte"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on SPI
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This option enables support for LED controller which use a single byte
|
|
|
|
|
for controlling the brightness. Currently the following controller is
|
|
|
|
|
supported: Ubiquiti airCube ISP microcontroller based LED controller.
|
|
|
|
|
|
2019-05-07 02:16:11 +07:00
|
|
|
config LEDS_TI_LMU_COMMON
|
|
|
|
|
tristate "LED driver for TI LMU"
|
|
|
|
|
depends on LEDS_CLASS
|
|
|
|
|
depends on REGMAP
|
|
|
|
|
help
|
|
|
|
|
Say Y to enable the LED driver for TI LMU devices.
|
|
|
|
|
This supports common features between the TI LM3532, LM3631, LM3632,
|
|
|
|
|
LM3633, LM3695 and LM3697.
|
|
|
|
|
|
2019-05-07 02:16:14 +07:00
|
|
|
config LEDS_LM3697
|
|
|
|
|
tristate "LED driver for LM3697"
|
|
|
|
|
depends on LEDS_TI_LMU_COMMON
|
|
|
|
|
depends on I2C && OF
|
|
|
|
|
help
|
|
|
|
|
Say Y to enable the LM3697 LED driver for TI LMU devices.
|
|
|
|
|
This supports the LED device LM3697.
|
|
|
|
|
|
2019-06-05 19:56:34 +07:00
|
|
|
config LEDS_LM36274
|
|
|
|
|
tristate "LED driver for LM36274"
|
|
|
|
|
depends on LEDS_TI_LMU_COMMON
|
|
|
|
|
depends on MFD_TI_LMU
|
|
|
|
|
help
|
|
|
|
|
Say Y to enable the LM36274 LED driver for TI LMU devices.
|
|
|
|
|
This supports the LED device LM36274.
|
|
|
|
|
|
2010-01-21 06:08:30 +07:00
|
|
|
comment "LED Triggers"
|
2013-02-20 15:36:01 +07:00
|
|
|
source "drivers/leds/trigger/Kconfig"
|
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 05:07:30 +07:00
|
|
|
|
2007-05-10 16:44:11 +07:00
|
|
|
endif # NEW_LEDS
|