| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller
4 In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller),
5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
6 See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 - compatible : should be "brcm,bcm6358-leds".
11 - #address-cells : must be 1.
12 - #size-cells : must be 0.
13 - reg : BCM6358 LED controller address and size.
16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8.
18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low.
[all …]
|
| D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller
4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
5 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
17 registers you have some limited control over rerouting the LEDs (as
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
21 reason, hardware controlled LEDs aren't registered as LED class devices.
24 - compatible : should be "brcm,bcm6328-leds".
[all …]
|
| D | leds-gpio.txt | 1 LEDs connected to GPIO lines
4 - compatible : should be "gpio-leds".
6 Each LED is represented as a sub-node of the gpio-leds device. Each
9 LED sub-node properties:
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
11 Documentation/devicetree/bindings/gpio/gpio.txt. Active low LEDs should be
13 - label : (optional)
14 see Documentation/devicetree/bindings/leds/common.txt
15 - linux,default-trigger : (optional)
16 see Documentation/devicetree/bindings/leds/common.txt
[all …]
|
| D | leds-pwm.txt | 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:
15 - max-brightness : Maximum brightness possible for the LED
16 - active-low : (optional) For PWMs where the LED is wired to supply
18 - label : (optional)
19 see Documentation/devicetree/bindings/leds/common.txt
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller
4 In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller),
5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
6 See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 - compatible : should be "brcm,bcm6358-leds".
11 - #address-cells : must be 1.
12 - #size-cells : must be 0.
13 - reg : BCM6358 LED controller address and size.
16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8.
18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low.
[all …]
|
| D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller
4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
5 However, on some devices there are Serial LEDs (LEDs connected to a 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
17 registers you have some limited control over rerouting the LEDs (as
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
21 reason, hardware controlled LEDs aren't registered as LED class devices.
24 - compatible : should be "brcm,bcm6328-leds".
[all …]
|
| D | leds-pwm.txt | 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:
15 - max-brightness : Maximum brightness possible for the LED
16 - active-low : (optional) For PWMs where the LED is wired to supply
18 - label : (optional)
19 see Documentation/devicetree/bindings/leds/common.txt
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | lpc3250-ea3250.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
8 /dts-v1/;
20 gpio-keys {
21 compatible = "gpio-keys";
85 leds {
86 compatible = "gpio-leds";
88 /* LEDs on OEM Board */
91 gpios = <&gpio 5 14 1>; /* GPO_P3 14, GPIO 93, active low */
92 linux,default-trigger = "timer";
93 default-state = "off";
[all …]
|
| D | dove-cm-a510.dtsi | 2 * Device Tree include for Compulab CM-A510 System-on-Module
6 * This file is dual-licensed: you can use it either under the terms
46 * The CM-A510 comes with several optional components:
66 * U2: 2 dual-role USB2.0 ports
70 * W: Broadcom BCM4319 802.11b/g/n (USI WM-N-BM-01 on SDIO1)
72 * GPIOs used on CM-A510:
73 * 1 GbE PHY reset (active low)
75 * 8 PowerOff (active low)
76 * 13 Touchscreen pen irq (active low)
77 * 65 System LED (active high)
[all …]
|
| D | armada-385-clearfog-gtr.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
5 * Rabeeh Khoury <rabeeh@solid-run.com>, based on Russell King clearfog work
9 SERDES mapping -
10 0. SATA1 on CON18, or optionally mini PCIe CON3 - PCIe0
12 2. SATA0 on CON17, or optionally mini PCIe CON4 - PCIe1
14 4. mini PCIe CON2 - PCIe2
17 USB 2.0 mapping -
18 0. USB 2.0 - 0 USB pins header CON12
19 1. USB 2.0 - 1 mini PCIe CON2
20 2. USB 2.0 - 2 to USB 3.0 connector (used with SERDES #3)
[all …]
|
| D | sun8i-s3-pinecube.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR X11)
6 /dts-v1/;
7 #include "sun8i-v3.dtsi"
8 #include <dt-bindings/gpio/gpio.h>
9 #include <dt-bindings/input/input.h>
13 compatible = "pine64,pinecube", "sochip,s3", "allwinner,sun8i-v3";
20 stdout-path = "serial0:115200n8";
23 leds {
24 compatible = "gpio-leds";
38 compatible = "regulator-fixed";
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | lpc3250-ea3250.dts | 10 * http://www.opensource.org/licenses/gpl-license.html
14 /dts-v1/;
20 #address-cells = <1>;
21 #size-cells = <1>;
29 compatible = "gpio-keys";
30 #address-cells = <1>;
31 #size-cells = <0>;
85 leds {
86 compatible = "gpio-leds";
88 /* LEDs on OEM Board */
[all …]
|
| D | dove-cm-a510.dtsi | 2 * Device Tree include for Compulab CM-A510 System-on-Module
6 * This file is dual-licensed: you can use it either under the terms
46 * The CM-A510 comes with several optional components:
66 * U2: 2 dual-role USB2.0 ports
70 * W: Broadcom BCM4319 802.11b/g/n (USI WM-N-BM-01 on SDIO1)
72 * GPIOs used on CM-A510:
73 * 1 GbE PHY reset (active low)
75 * 8 PowerOff (active low)
76 * 13 Touchscreen pen irq (active low)
77 * 65 System LED (active high)
[all …]
|
| /kernel/linux/linux-5.10/drivers/leds/ |
| D | leds-sc27xx-bltc.c | 1 // SPDX-License-Identifier: GPL-2.0
4 #include <linux/leds.h>
52 bool active; member
56 struct sc27xx_led leds[SC27XX_LEDS_MAX]; member
82 static u32 sc27xx_led_get_offset(struct sc27xx_led *leds) in sc27xx_led_get_offset() argument
84 return leds->priv->base + SC27XX_LEDS_OFFSET * leds->line; in sc27xx_led_get_offset()
87 static int sc27xx_led_enable(struct sc27xx_led *leds, enum led_brightness value) in sc27xx_led_enable() argument
89 u32 base = sc27xx_led_get_offset(leds); in sc27xx_led_enable()
90 u32 ctrl_base = leds->priv->base + SC27XX_LEDS_CTRL; in sc27xx_led_enable()
91 u8 ctrl_shift = SC27XX_CTRL_SHIFT * leds->line; in sc27xx_led_enable()
[all …]
|
| D | leds-bcm6358.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Driver for BCM6358 memory-mapped LEDs, based on leds-syscon.c
9 #include <linux/leds.h>
31 * struct bcm6358_led - state container for bcm6358 based LEDs
36 * @active_low: LED is active low
82 spin_lock_irqsave(led->lock, flags); in bcm6358_led_set()
83 bcm6358_led_busy(led->mem); in bcm6358_led_set()
84 val = bcm6358_led_read(led->mem + BCM6358_REG_MODE); in bcm6358_led_set()
85 if ((led->active_low && value == LED_OFF) || in bcm6358_led_set()
86 (!led->active_low && value != LED_OFF)) in bcm6358_led_set()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | allwinner,sun8i-a83t-emac.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/net/allwinner,sun8i-a83t-emac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
16 - const: allwinner,sun8i-a83t-emac
17 - const: allwinner,sun8i-h3-emac
18 - const: allwinner,sun8i-r40-emac
19 - const: allwinner,sun8i-v3s-emac
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | dwmac-sun8i.txt | 7 - compatible: must be one of the following string:
8 "allwinner,sun8i-a83t-emac"
9 "allwinner,sun8i-h3-emac"
10 "allwinner,sun8i-r40-gmac"
11 "allwinner,sun8i-v3s-emac"
12 "allwinner,sun50i-a64-emac"
13 - reg: address and length of the register for the device.
14 - interrupts: interrupt for the device
15 - interrupt-names: must be "macirq"
16 - clocks: A phandle to the reference clock for this device
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio_lpc32xx.txt | 4 - compatible: must be "nxp,lpc3220-gpio"
5 - reg: Physical base address and length of the controller's registers.
6 - gpio-controller: Marks the device node as a GPIO controller.
7 - #gpio-cells: Should be 3:
17 - bit 0 specifies polarity (0 for normal, 1 for inverted)
18 - reg: Index of the GPIO group
23 compatible = "nxp,lpc3220-gpio";
25 gpio-controller;
26 #gpio-cells = <3>; /* bank, pin, flags */
29 leds {
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpio/ |
| D | gpio_lpc32xx.txt | 4 - compatible: must be "nxp,lpc3220-gpio"
5 - reg: Physical base address and length of the controller's registers.
6 - gpio-controller: Marks the device node as a GPIO controller.
7 - #gpio-cells: Should be 3:
17 - bit 0 specifies polarity (0 for normal, 1 for inverted)
18 - reg: Index of the GPIO group
23 compatible = "nxp,lpc3220-gpio";
25 gpio-controller;
26 #gpio-cells = <3>; /* bank, pin, flags */
29 leds {
[all …]
|
| /kernel/linux/linux-4.19/drivers/leds/ |
| D | leds-bcm6358.c | 2 * Driver for BCM6358 memory-mapped LEDs, based on leds-syscon.c
13 #include <linux/leds.h>
35 * struct bcm6358_led - state container for bcm6358 based LEDs
40 * @active_low: LED is active low
86 spin_lock_irqsave(led->lock, flags); in bcm6358_led_set()
87 bcm6358_led_busy(led->mem); in bcm6358_led_set()
88 val = bcm6358_led_read(led->mem + BCM6358_REG_MODE); in bcm6358_led_set()
89 if ((led->active_low && value == LED_OFF) || in bcm6358_led_set()
90 (!led->active_low && value != LED_OFF)) in bcm6358_led_set()
91 val |= BIT(led->pin); in bcm6358_led_set()
[all …]
|
| D | leds-tlc591xx.c | 11 #include <linux/leds.h>
37 #define LEDOUT_OFF 0x0 /* Output LOW */
38 #define LEDOUT_ON 0x1 /* Output HI-Z */
46 bool active; member
53 struct tlc591xx_led leds[TLC591XX_MAX_LEDS]; member
92 unsigned int i = (led->led_no % 4) * 2; in tlc591xx_set_ledout()
94 unsigned int addr = priv->reg_ledout_offset + (led->led_no >> 2); in tlc591xx_set_ledout()
98 return regmap_update_bits(priv->regmap, addr, mask, val); in tlc591xx_set_ledout()
105 u8 pwm = TLC591XX_REG_PWM(led->led_no); in tlc591xx_set_pwm()
107 return regmap_write(priv->regmap, pwm, brightness); in tlc591xx_set_pwm()
[all …]
|
| D | leds-bcm6328.c | 2 * Driver for BCM6328 memory-mapped LEDs, based on leds-syscon.c
13 #include <linux/leds.h>
58 * struct bcm6328_led - state container for bcm6328 based LEDs
63 * @blink_leds: blinking LEDs
65 * @active_low: LED is active low
96 * LEDMode 64 bits / 24 LEDs
97 * bits [31:0] -> LEDs 8-23
98 * bits [47:32] -> LEDs 0-7
99 * bits [63:48] -> unused
104 return pin + 16; /* LEDs 0-7 (bits 47:32) */ in bcm6328_pin2shift()
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/boot/dts/brcm/ |
| D | bcm63268-comtrend-vr-3032u.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
7 compatible = "comtrend,vr-3032u", "brcm,bcm63268";
8 model = "Comtrend VR-3032u";
17 stdout-path = &uart0;
23 brcm,serial-leds;
24 brcm,serial-dat-low;
25 brcm,serial-shift-inv;
29 brcm,hardware-controlled;
30 brcm,link-signal-sources = <0>;
[all …]
|
| /kernel/linux/linux-4.19/arch/mips/boot/dts/brcm/ |
| D | bcm63268-comtrend-vr-3032u.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
7 compatible = "comtrend,vr-3032u", "brcm,bcm63268";
8 model = "Comtrend VR-3032u";
17 stdout-path = &uart0;
23 brcm,serial-leds;
24 brcm,serial-dat-low;
25 brcm,serial-shift-inv;
29 brcm,hardware-controlled;
30 brcm,link-signal-sources = <0>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | max77650.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MAX77650 ultra low-power PMIC from Maxim Integrated.
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
13 MAX77650 is an ultra-low power PMIC providing battery charging and power
14 supply for low-power IoT and wearable applications.
16 The GPIO-controller module is represented as part of the top-level PMIC
19 For device-tree bindings of other sub-modules (regulator, power supply,
20 LEDs and onkey) refer to the binding documents under the respective
[all …]
|