Home
last modified time | relevance | path

Searched +full:pwm +full:- +full:leds (Results 1 – 25 of 335) sorted by relevance

12345678910>>...14

/linux/drivers/leds/rgb/
H A DKconfig1 # 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 Dleds-pwm-multicolor.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * PWM-based multi-color LED control
5 * Copyright 2022 Sven Schwermer <sven.schwermer@disruptive-technologies.com>
10 #include <linux/led-class-multicolor.h>
11 #include <linux/leds.h>
17 #include <linux/pwm.h>
20 struct pwm_device *pwm; member
28 struct pwm_led leds[]; member
42 mutex_lock(&priv->lock); in led_pwm_mc_set()
44 for (i = 0; i < mc_cdev->num_colors; i++) { in led_pwm_mc_set()
[all …]
H A DMakefile1 # 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/Documentation/devicetree/bindings/leds/
H A Dleds-pwm-multicolor.yaml1 # 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 …]
/linux/drivers/leds/
H A Dleds-pca9532.c1 // 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 Dleds-pca955x.c1 // 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 …]
/linux/Documentation/ABI/testing/
H A Dsysfs-class-led-driver-lm35331 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 Dlp3943.c1 // 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/arch/arm64/boot/dts/mediatek/
H A Dmt7981b-openwrt-one.dts1 // SPDX-License-Identifier: GPL-2.0-only OR MIT
3 /dts-v1/;
6 #include <dt-bindings/gpio/gpio.h>
7 #include <dt-bindings/leds/common.h>
8 #include "dt-bindings/pinctrl/mt65xx.h"
19 stdout-path = "serial0:115200n8";
27 pwm-leds {
28 compatible = "pwm-leds";
30 led-0 {
32 default-brightness = <0>;
[all …]
H A Dmt7986a-bananapi-bpi-r3-mini.dts1 // 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 …]
/linux/Documentation/devicetree/bindings/pwm/
H A Dpwm-lp3943.txt1 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 …]
H A Dnxp,pca9685-pwm.txt1 NXP PCA9685 16-channel 12-bit PWM LED controller
5 - compatible: "nxp,pca9685-pwm"
6 - #pwm-cells: Should be 2. See pwm.yaml in this directory for a description of
8 The index 16 is the ALLCALL channel, that sets all PWM channels at the same
12 - invert (bool): boolean to enable inverted logic
13 - open-drain (bool): boolean to configure outputs with open-drain structure;
14 if omitted use totem-pole structure
18 For LEDs that are directly connected to the PCA, the following setting is
22 compatible = "nxp,pca9685-pwm";
23 #pwm-cells = <2>;
[all …]
/linux/arch/arm/boot/dts/samsung/
H A Dexynos54xx-odroidxu-leds.dtsi1 // 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 Dexynos5422-odroidxu4.dts1 // 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 Dexynos4412-odroidu3.dts1 // 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 Dexynos4412-itop-elite.dts1 // 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 Dbcm53016-meraki-mr32.dts1 // 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 Dbcm958625-meraki-mx6x-common.dtsi1 // 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 0>;
[all …]
/linux/Documentation/driver-api/gpio/
H A Ddrivers-on-gpio.rst6 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 Dleds-qcom-lpg.rst1 .. 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/platform/chrome/wilco_ec/
H A Dkeyboard_leds.c1 // 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/arch/arm/boot/dts/rockchip/
H A Drv1109-relfor-saib.dts1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
7 /dts-v1/;
9 #include <dt-bindings/leds/common.h>
10 #include <dt-bindings/input/input.h>
16 gpio-keys {
17 compatible = "gpio-keys";
23 linux,input-type = <1>;
27 ir_receiver: ir-receiver {
28 compatible = "gpio-ir-receiver";
30 pinctrl-names = "default";
[all …]
/linux/Documentation/devicetree/bindings/mfd/
H A Dti-lmu.txt6 ------ ---------------------------------
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/arch/arm64/boot/dts/rockchip/
H A Drk3528-radxa-e20c.dts1 // SPDX-License-Identifier: GPL-2.0+
8 /dts-v1/;
10 #include <dt-bindings/input/input.h>
11 #include <dt-bindings/leds/common.h>
12 #include <dt-bindings/pwm/pwm.h>
28 stdout-path = "serial0:1500000n8";
31 adc-keys {
32 compatible = "adc-keys";
33 io-channels = <&saradc 0>;
34 io-channel-names = "buttons";
[all …]
/linux/Documentation/driver-api/
H A Dpwm.rst2 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 …]

12345678910>>...14