| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/leds/ |
| D | leds-pwm.txt | 1 LED connected to PWM
4 - compatible : should be "pwm-leds".
6 Each LED is represented as a sub-node of the pwm-leds device. Each
9 LED sub-node properties:
10 - pwms : PWM property to point to the PWM device (phandle)/port (id) and to
12 - pwm-names : (optional) Name to be used by the PWM subsystem for the PWM device
13 For the pwms and pwm-names property please refer to:
14 Documentation/devicetree/bindings/pwm/pwm.txt
15 - max-brightness : Maximum brightness possible for the LED
16 - active-low : (optional) For PWMs where the LED is wired to supply
[all …]
|
| D | leds-pca9532.txt | 1 *NXP - pca9532 PWM LED Driver
3 The PCA9532 family is SMBus I/O expander optimized for dimming LEDs.
4 The PWM support 256 steps.
7 - compatible:
12 - reg - I2C slave address
14 Each led is represented as a sub-node of the nxp,pca9530.
16 Optional sub-node properties:
17 - label: see Documentation/devicetree/bindings/leds/common.txt
18 - type: Output configuration, see dt-bindings/leds/leds-pca9532.h (default NONE)
19 - linux,default-trigger: see Documentation/devicetree/bindings/leds/common.txt
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-pwm.txt | 1 LED connected to PWM
4 - compatible : should be "pwm-leds".
6 Each LED is represented as a sub-node of the pwm-leds device. Each
9 LED sub-node properties:
10 - pwms : PWM property to point to the PWM device (phandle)/port (id) and to
12 - pwm-names : (optional) Name to be used by the PWM subsystem for the PWM device
13 For the pwms and pwm-names property please refer to:
14 Documentation/devicetree/bindings/pwm/pwm.txt
15 - max-brightness : Maximum brightness possible for the LED
16 - active-low : (optional) For PWMs where the LED is wired to supply
[all …]
|
| D | leds-pca9532.txt | 1 *NXP - pca9532 PWM LED Driver
3 The PCA9532 family is SMBus I/O expander optimized for dimming LEDs.
4 The PWM support 256 steps.
7 - compatible:
12 - reg - I2C slave address
14 Each led is represented as a sub-node of the nxp,pca9530.
16 Optional sub-node properties:
17 - label: see Documentation/devicetree/bindings/leds/common.txt
18 - type: Output configuration, see dt-bindings/leds/leds-pca9532.h (default NONE)
19 - linux,default-trigger: see Documentation/devicetree/bindings/leds/common.txt
[all …]
|
| /kernel/linux/linux-4.19/drivers/leds/ |
| D | leds-pwm.c | 2 * linux/drivers/leds-pwm.c
4 * simple PWM based LED control
8 * based on leds-gpio.c by Raphael Assenat <raph@8d.com>
19 #include <linux/leds.h>
21 #include <linux/pwm.h>
27 struct pwm_device *pwm; member
35 struct led_pwm_data leds[0]; member
40 int new_duty = led_dat->duty; in __led_pwm_set()
42 pwm_config(led_dat->pwm, new_duty, led_dat->period); in __led_pwm_set()
45 pwm_disable(led_dat->pwm); in __led_pwm_set()
[all …]
|
| D | leds-pca9532.c | 2 * pca9532.c - 16-bit Led dimmer
18 #include <linux/leds.h>
22 #include <linux/leds-pca9532.h>
43 struct pca9532_led leds[16]; member
51 u8 pwm[2]; member
105 .name = "leds-pca953x",
113 /* We have two pwm/blinkers, but 16 possible leds to drive. Additionally,
114 * the clever Thecus people are using one pwm to drive the beeper. So,
115 * as a compromise we average one pwm to the values requested by all
116 * leds that are not ON/OFF.
[all …]
|
| D | Kconfig | 12 LEDs from both userspace and optionally, by kernel events (triggers).
19 This option enables the led sysfs class in /sys/class/leds. You'll
20 need this to do anything useful with LEDs. If unsure, say N.
26 This option enables the flash led sysfs class in /sys/class/leds.
27 It wrapps LED Class and adds flash LEDs specific sysfs attributes
37 for led sysfs class devices under /sys/class/leds.
39 See Documentation/ABI/testing/sysfs-class-led for details.
48 This option enables support for on-chip LED drivers found on Marvell
59 This option enables support for the LEDs on the AAT1290.
66 This driver makes the PC Engines APU/APU2/APU3 front panel LEDs
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class-led-driver-lm3533 | 1 What: /sys/class/leds/<led>/als_channel
7 ALS-current-control mode (1, 2), where
9 1 - out_current1
10 2 - out_current2
12 What: /sys/class/leds/<led>/als_en
17 Enable ALS-current-control mode (0, 1).
19 What: /sys/class/leds/<led>/falltime
20 What: /sys/class/leds/<led>/risetime
27 0 - 2048 us
28 1 - 262 ms
[all …]
|
| /kernel/linux/linux-5.10/drivers/leds/ |
| 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>
29 struct pwm_device *pwm; member
36 struct led_pwm_data leds[]; member
44 unsigned int max = led_dat->cdev.max_brightness; in led_pwm_set()
45 unsigned long long duty = led_dat->pwmstate.period; in led_pwm_set()
[all …]
|
| 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>
41 struct pca9532_led leds[16]; member
49 u8 pwm[2]; member
103 .name = "leds-pca953x",
111 /* We have two pwm/blinkers, but 16 possible leds to drive. Additionally,
112 * the clever Thecus people are using one pwm to drive the beeper. So,
113 * as a compromise we average one pwm to the values requested by all
[all …]
|
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 LEDs from both userspace and optionally, by kernel events (triggers).
20 This option enables the LED sysfs class in /sys/class/leds. You'll
21 need this to do anything useful with LEDs. If unsure, say N.
27 This option enables the flash LED sysfs class in /sys/class/leds.
28 It wraps LED Class and adds flash LEDs specific sysfs attributes
37 This option enables the multicolor LED sysfs class in /sys/class/leds.
40 for multicolor LEDs that are grouped together. This class is not
41 intended for single color LEDs. It can be built as a module.
48 for LED sysfs class devices under /sys/class/leds.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| 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 …]
|
| /kernel/linux/linux-4.19/drivers/mfd/ |
| D | lp3943.c | 14 * It can be used for a GPIO expander and PWM generators.
19 * LP3943 MFD ---- GPIO expander leds-gpio eg) HW enable pin
21 * --- PWM generator leds-pwm eg) PWM input
23 * Internal two PWM channels are used for LED dimming effect.
26 * LEDs can be controlled with legacy leds-gpio(static brightness) or
27 * leds-pwm drivers(dynamic brightness control).
28 * Alternatively, it can be used for generic GPIO and PWM controller.
30 * A PWM is input pin of a backlight device.
67 .name = "lp3943-pwm",
68 .of_compatible = "ti,lp3943-pwm",
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | max77693.txt | 1 Maxim MAX77693 multi-function device
4 - PMIC,
5 - CHARGER,
6 - LED,
7 - MUIC,
8 - HAPTIC
14 - compatible : Must be "maxim,max77693".
15 - reg : Specifies the i2c slave address of PMIC block.
16 - interrupts : This i2c device has an IRQ line connected to the main SoC.
19 - regulators : The regulators of max77693 have to be instantiated under subnode
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/ |
| D | max77693.txt | 1 Maxim MAX77693 multi-function device
4 - PMIC,
5 - CHARGER,
6 - LED,
7 - MUIC,
8 - HAPTIC
14 - compatible : Must be "maxim,max77693".
15 - reg : Specifies the i2c slave address of PMIC block.
16 - interrupts : This i2c device has an IRQ line connected to the main SoC.
19 - regulators : The regulators of max77693 have to be instantiated under subnode
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pwm/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pwm/ |
| D | pwm-lp3943.txt | 1 TI/National Semiconductor LP3943 PWM controller
4 - compatible: "ti,lp3943-pwm"
5 - #pwm-cells: Should be 2. See pwm.txt 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 …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| 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";
50 #address-cells = <1>;
[all …]
|
| D | exynos54xx-odroidxu-leds.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
11 #include <dt-bindings/gpio/gpio.h>
15 compatible = "pwm-leds";
19 pwms = <&pwm 1 2000000 0>;
20 pwm-names = "pwm1";
25 max-brightness = <127>;
26 linux,default-trigger = "mmc0";
31 pwms = <&pwm 2 2000000 0>;
32 pwm-names = "pwm2";
33 max-brightness = <255>;
[all …]
|
| D | berlin2cd-google-chromecast.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
11 #include <dt-bindings/gpio/gpio.h>
19 stdout-path = "serial0:115200n8";
26 * We're using "linux,usable-memory" instead of "reg" here
34 linux,usable-memory = <0x00000000 0x20000000>; /* 512 MB */
37 leds {
38 compatible = "pwm-leds";
39 pinctrl-0 = <&ledpwm_pmux>;
40 pinctrl-names = "default";
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | exynos54xx-odroidxu-leds.dtsi | 1 // SPDX-License-Identifier: GPL-2.0
11 #include <dt-bindings/gpio/gpio.h>
15 compatible = "pwm-leds";
19 pwms = <&pwm 1 2000000 0>;
20 pwm-names = "pwm1";
26 linux,default-trigger = "mmc0";
31 pwms = <&pwm 2 2000000 0>;
32 pwm-names = "pwm2";
34 linux,default-trigger = "heartbeat";
39 compatible = "gpio-leds";
[all …]
|
| D | berlin2cd-google-chromecast.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
11 #include <dt-bindings/gpio/gpio.h>
19 stdout-path = "serial0:115200n8";
26 * We're using "linux,usable-memory" instead of "reg" here
34 linux,usable-memory = <0x00000000 0x20000000>; /* 512 MB */
37 leds {
38 compatible = "pwm-leds";
39 pinctrl-0 = <&ledpwm_pmux>;
40 pinctrl-names = "default";
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | leds_pwm.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * PWM LED driver data - see drivers/leds/leds-pwm.c
19 struct led_pwm *leds; member
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | pwm.txt | 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 …]
|