/linux/drivers/leds/rgb/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 6 tristate "LEDs group multi-color support" 9 This option enables support for monochrome LEDs that are grouped 10 into multicolor LEDs which is useful in the case where LEDs of 11 different colors are physically grouped in a single multi-color LED 12 and driven by a controller that doesn't have multi-color support. 15 will be called leds-group-multicolor. 27 will be called leds-ktd202x. 38 will be called leds-ncp5623. 41 tristate "PWM driven multi-color LED Support" [all …]
|
H A D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0 3 obj-$(CONFIG_LEDS_GROUP_MULTICOLOR) += leds-group-multicolor.o 4 obj-$(CONFIG_LEDS_KTD202X) += leds-ktd202x.o 5 obj-$(CONFIG_LEDS_NCP5623) += leds-ncp5623.o 6 obj-$(CONFIG_LEDS_PWM_MULTICOLOR) += leds-pwm-multicolor.o 7 obj-$(CONFIG_LEDS_QCOM_LPG) += leds-qcom-lpg.o 8 obj-$(CONFIG_LEDS_MT6370_RGB) += leds-mt6370-rgb.o
|
/linux/drivers/leds/ |
H A D | leds-pwm.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * linux/drivers/leds-pwm.c 5 * simple PWM based LED control 9 * based on leds-gpio.c by Raphael Assenat <raph@8d.com> 16 #include <linux/leds.h> 18 #include <linux/pwm.h> 30 struct pwm_device *pwm; member 37 struct led_pwm_data leds[]; member 45 unsigned int max = led_dat->cdev.max_brightness; in led_pwm_set() 46 unsigned long long duty = led_dat->pwmstate.period; in led_pwm_set() [all …]
|
H A D | leds-pca9532.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * pca9532.c - 16-bit Led dimmer 14 #include <linux/leds.h> 18 #include <linux/leds-pca9532.h> 43 struct pca9532_led leds[16]; member 54 u8 pwm[2]; member 108 .name = "leds-pca953x", 116 /* We have two pwm/blinkers, but 16 possible leds to drive. Additionally, 117 * the clever Thecus people are using one pwm to drive the beeper. So, 118 * as a compromise we average one pwm to the values requested by all [all …]
|
H A D | leds-pca955x.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Copyright 2007-2008 Extreme Engineering Solutions, Inc. 5 * Author: Nate Case <ncase@xes-inc.com> 11 * Device Description 7-bit slave address 12 * ------ ----------- ------------------- 13 * PCA9550 2-bit driver 0x60 .. 0x61 14 * PCA9551 8-bit driver 0x60 .. 0x67 15 * PCA9552 16-bit driver 0x60 .. 0x67 16 * PCA9553/01 4-bit driver 0x62 17 * PCA9553/02 4-bit driver 0x63 [all …]
|
H A D | leds-is31fl32xx.c | 1 // SPDX-License-Identifier: GPL-2.0-only 8 * http://www.issi.com/US/product-analog-fxled-driver.shtml 9 * http://www.si-en.com/product.asp?parentid=890 15 #include <linux/leds.h> 38 u8 channel; /* 1-based, max priv->cdef->channels */ 46 struct is31fl32xx_led_data leds[]; member 50 * struct is31fl32xx_chipdef - chip-specific attributes 53 * @pwm_update_reg : address of PWM Update register 56 * @pwm_register_base : address of first PWM register 57 * @pwm_registers_reversed: : true if PWM registers count down instead of up [all …]
|
H A D | leds-lp3944.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * leds-lp3944.c - driver for National Semiconductor LP3944 Funlight Chip 12 * This helper chip can drive up to 8 leds, with two programmable DIM modes; 16 * The DIM modes are used to set _blink_ patterns for leds, the pattern is 18 * - period: from 0s to 1.6s 19 * - duty cycle: percentage of the period the led is on, from 0 to 100 22 * leds, the camera flash light and the displays backlights. 28 #include <linux/leds.h> 30 #include <linux/leds-lp3944.h> 33 #define LP3944_REG_INPUT1 0x00 /* LEDs 0-7 InputRegister (Read Only) */ [all …]
|
/linux/Documentation/devicetree/bindings/leds/ |
H A D | leds-pwm-multicolor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-pwm-multicolor.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Multi-color LEDs connected to PWM 10 - Sven Schwermer <sven.schwermer@disruptive-technologies.com> 13 This driver combines several monochrome PWM LEDs into one multi-color 18 const: pwm-leds-multicolor 20 multi-led: 22 $ref: leds-class-multicolor.yaml# [all …]
|
H A D | leds-pwm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-pwm.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LEDs connected to PWM 10 - Pavel Machek <pavel@ucw.cz> 13 Each LED is represented as a sub-node of the pwm-leds device. Each 18 const: pwm-leds 21 "^led(-[0-9a-f]+)?$": 30 pwm-names: true [all …]
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-class-led-driver-lm3533 | 1 What: /sys/class/leds/<led>/als_channel 7 ALS-current-control mode (1, 2), where: 14 What: /sys/class/leds/<led>/als_en 19 Enable ALS-current-control mode (0, 1). 21 What: /sys/class/leds/<led>/falltime 22 What: /sys/class/leds/<led>/risetime 40 What: /sys/class/leds/<led>/id 47 What: /sys/class/leds/<led>/linear 52 Set the brightness-mapping mode (0, 1), where: 59 What: /sys/class/leds/<led>/pwm [all …]
|
/linux/drivers/mfd/ |
H A D | lp3943.c | 1 // SPDX-License-Identifier: GPL-2.0-only 11 * It can be used for a GPIO expander and PWM generators. 16 * LP3943 MFD ---- GPIO expander leds-gpio eg) HW enable pin 18 * --- PWM generator leds-pwm eg) PWM input 20 * Internal two PWM channels are used for LED dimming effect. 23 * LEDs can be controlled with legacy leds-gpio(static brightness) or 24 * leds-pwm drivers(dynamic brightness control). 25 * Alternatively, it can be used for generic GPIO and PWM controller. 27 * A PWM is input pin of a backlight device. 64 .name = "lp3943-pwm", [all …]
|
/linux/Documentation/devicetree/bindings/pwm/ |
H A D | pwm-lp3943.txt | 1 TI/National Semiconductor LP3943 PWM controller 4 - compatible: "ti,lp3943-pwm" 5 - #pwm-cells: Should be 2. See pwm.yaml in this directory for a 9 - ti,pwm0 or ti,pwm1: Output pin number(s) for PWM channel 0 or 1. 17 PWM 0 is for RGB LED brightness control 18 PWM 1 is for brightness control of LP8557 backlight device 26 * PWM 0 : output 8, 9 and 10 27 * PWM 1 : output 15 29 pwm3943: pwm { 30 compatible = "ti,lp3943-pwm"; [all …]
|
/linux/arch/arm/boot/dts/samsung/ |
H A D | exynos54xx-odroidxu-leds.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 11 #include <dt-bindings/gpio/gpio.h> 12 #include <dt-bindings/leds/common.h> 15 led-controller-1 { 16 compatible = "pwm-leds"; 18 led-1 { 22 pwms = <&pwm 1 2000000 0>; 23 pwm-names = "pwm1"; 28 max-brightness = <127>; 29 linux,default-trigger = "mmc0"; [all …]
|
H A D | exynos5422-odroidxu4.dts | 1 // SPDX-License-Identifier: GPL-2.0 7 * Copyright (c) 2013-2015 Samsung Electronics Co., Ltd. 11 /dts-v1/; 12 #include <dt-bindings/leds/common.h> 13 #include <dt-bindings/sound/samsung-i2s.h> 14 #include "exynos5422-odroidxu3-common.dtsi" 18 compatible = "hardkernel,odroid-xu4", "samsung,exynos5800", \ 21 led-controller { 22 compatible = "pwm-leds"; 24 led-1 { [all …]
|
H A D | exynos4412-odroidu3.dts | 1 // SPDX-License-Identifier: GPL-2.0 3 * Hardkernel's Exynos4412 based ODROID-U3 board device tree source 7 * Device tree source file for Hardkernel's ODROID-U3 board which is based 11 /dts-v1/; 12 #include <dt-bindings/leds/common.h> 13 #include "exynos4412-odroid-common.dtsi" 14 #include "exynos4412-prime.dtsi" 17 model = "Hardkernel ODROID-U3 board based on Exynos4412"; 18 compatible = "hardkernel,odroid-u3", "samsung,exynos4412", "samsung,exynos4"; 29 vbus_otg_reg: regulator-1 { [all …]
|
H A D | exynos4412-itop-elite.dts | 1 // SPDX-License-Identifier: GPL-2.0 13 /dts-v1/; 14 #include <dt-bindings/leds/common.h> 15 #include <dt-bindings/pwm/pwm.h> 16 #include <dt-bindings/sound/samsung-i2s.h> 17 #include "exynos4412-itop-scp-core.dtsi" 21 compatible = "topeet,itop4412-elite", "samsung,exynos4412", "samsung,exynos4"; 29 stdout-path = "serial2:115200n8"; 32 leds { 33 compatible = "gpio-leds"; [all …]
|
/linux/arch/arm/boot/dts/broadcom/ |
H A D | bcm53016-meraki-mr32.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 6 * Copyright (C) 2018-2020 Christian Lamparter <chunkeey@gmail.com> 9 /dts-v1/; 12 #include "bcm5301x-nand-cs0-bch8.dtsi" 13 #include <dt-bindings/leds/common.h> 32 leds { 33 compatible = "gpio-leds"; 39 panic-indicator; 49 compatible = "gpio-keys"; 51 button-restart { [all …]
|
H A D | bcm958625-meraki-mx6x-common.dtsi | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 5 * Copyright (C) 2020-2021 Matthew Hagan <mnhagan88@gmail.com> 8 #include "bcm-nsp.dtsi" 9 #include <dt-bindings/gpio/gpio.h> 10 #include <dt-bindings/input/input.h> 11 #include <dt-bindings/leds/common.h> 14 pwm-leds { 15 compatible = "pwm-leds"; 17 led-1 { 20 pwms = <&pwm 1 50000>; [all …]
|
/linux/Documentation/driver-api/gpio/ |
H A D | drivers-on-gpio.rst | 6 the right in-kernel and userspace APIs/ABIs for the job, and that these 10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO 13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger, 15 (and that LED may in turn use the leds-gpio as per above). 17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line 20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your 24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with 29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from 31 off/on, for an actual PWM waveform, see pwm-gpio below.) 33 - pwm-gpio: drivers/pwm/pwm-gpio.c is used to toggle a GPIO with a high [all …]
|
/linux/Documentation/leds/ |
H A D | leds-qcom-lpg.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 ----------- 11 number of PWM channels, a programmable pattern lookup table and a RGB LED 15 individual LEDs, grouped together as RGB LEDs or otherwise be accessed as PWM 16 channels. The output of each PWM channel is routed to other hardware 19 The each PWM channel can operate with a period between 27us and 384 seconds and 30 /sys/class/leds/<led>/hw_pattern 31 -------------------------------- 35 The pattern is a series of brightness and hold-time pairs, with the hold-time 39 transitions expected by the leds-trigger-pattern format, each entry in the [all …]
|
/linux/drivers/pwm/ |
H A D | pwm-pca9685.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Driver for PCA9685 16-channel 12-bit PWM LED controller 8 * based on the pwm-twl-led.c driver 18 #include <linux/pwm.h> 28 * PWM channels requested afterwards must use a period that results in the same 96 /* No PWM enabled: Change allowed */ in pca9685_prescaler_can_change() 97 if (bitmap_empty(pca->pwms_enabled, PCA9685_MAXCHAN + 1)) in pca9685_prescaler_can_change() 99 /* More than one PWM enabled: Change not allowed */ in pca9685_prescaler_can_change() 100 if (bitmap_weight(pca->pwms_enabled, PCA9685_MAXCHAN + 1) > 1) in pca9685_prescaler_can_change() 103 * Only one PWM enabled: Change allowed if the PWM about to in pca9685_prescaler_can_change() [all …]
|
/linux/Documentation/devicetree/bindings/mfd/ |
H A D | ti-lmu.txt | 6 ------ --------------------------------- 14 - compatible: Should be one of: 20 - reg: I2C slave address. 28 - enable-gpios: A GPIO specifier for hardware enable pin. 29 - ramp-up-us: Current ramping from one brightness level to 31 Range from 2048 us - 117.44 s 32 - ramp-down-us: Current ramping from one brightness level to 34 Range from 2048 us - 117.44 s 35 - ti,brightness-resolution - This determines whether to use 8 bit brightness 47 - backlight: All LMU devices have backlight child nodes. [all …]
|
/linux/drivers/platform/chrome/wilco_ec/ |
H A D | keyboard_leds.c | 1 // SPDX-License-Identifier: GPL-2.0 13 #include <linux/leds.h> 14 #include <linux/platform_data/wilco-ec.h> 33 * struct wilco_keyboard_leds_msg - Message to/from EC for keyboard LED control. 40 * @percent: Brightness in 0-100. Only meaningful in PWM mode. 71 dev_err(ec->dev, in send_kbbl_msg() 72 "Failed sending keyboard LEDs command: %d\n", ret); in send_kbbl_msg() 96 dev_err(ec->dev, in set_kbbl() 97 "EC reported failure sending keyboard LEDs command: %d\n", in set_kbbl() 99 return -EIO; in set_kbbl() [all …]
|
/linux/Documentation/driver-api/ |
H A D | pwm.rst | 2 Pulse Width Modulation (PWM) interface 5 This provides an overview about the Linux PWM interface 7 PWMs are commonly used for controlling LEDs, fans or vibrators in 9 the Linux PWM API (although they could). However, PWMs are often 11 up to the board designer to connect them to LEDs or fans. To provide 12 this kind of flexibility the generic PWM API exists. 15 ---------------- 17 Users of the legacy PWM API use unique IDs to refer to PWM devices. 19 Instead of referring to a PWM device via its unique ID, board setup code 20 should instead register a static mapping that can be used to match PWM [all …]
|
/linux/arch/arm64/boot/dts/mediatek/ |
H A D | mt7986a-bananapi-bpi-r3-mini.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT) 4 * Authors: Frank Wunderlich <frank-w@public-files.de> 9 /dts-v1/; 11 #include <dt-bindings/gpio/gpio.h> 12 #include <dt-bindings/input/input.h> 13 #include <dt-bindings/leds/common.h> 14 #include <dt-bindings/pinctrl/mt65xx.h> 19 model = "Bananapi BPI-R3 Mini"; 20 chassis-type = "embedded"; 21 compatible = "bananapi,bpi-r3mini", "mediatek,mt7986a"; [all …]
|