Searched +full:led +full:- +full:controller (Results 1 – 25 of 1006) sorted by relevance
12345678910>>...41
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 1 What: /sys/class/leds/<led>/flash_brightness
6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
11 /sys/class/leds/<led>/max_flash_brightness.
13 What: /sys/class/leds/<led>/max_flash_brightness
18 Maximum brightness level for this LED in the flash strobe mode,
21 What: /sys/class/leds/<led>/flash_timeout
28 of the strobe. The file is created only for the flash LED
31 What: /sys/class/leds/<led>/max_flash_timeout
36 Maximum flash timeout for this LED, in microseconds.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 1 What: /sys/class/leds/<led>/flash_brightness
6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
11 /sys/class/leds/<led>/max_flash_brightness.
13 What: /sys/class/leds/<led>/max_flash_brightness
18 Maximum brightness level for this LED in the flash strobe mode,
21 What: /sys/class/leds/<led>/flash_timeout
28 of the strobe. The file is created only for the flash LED
31 What: /sys/class/leds/<led>/max_flash_timeout
36 Maximum flash timeout for this LED, in microseconds.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _flash-controls:
10 controller devices. Flash controller devices are typically used in
13 The interface can support both LED and xenon flash devices. As of
17 .. _flash-controls-use-cases:
23 Unsynchronised LED flash (software strobe)
24 ------------------------------------------
26 Unsynchronised LED flash is controlled directly by the host as the
34 Synchronised LED flash (hardware strobe)
35 ----------------------------------------
[all …]
|
| /kernel/linux/linux-4.19/arch/mips/boot/dts/mti/ |
| D | sead3.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
8 #include <dt-bindings/interrupt-controller/mips-gic.h>
11 #address-cells = <1>;
12 #size-cells = <1>;
13 compatible = "mti,sead-3";
14 model = "MIPS SEAD-3";
17 stdout-path = "serial1:115200";
36 cpu_intc: interrupt-controller {
37 compatible = "mti,cpu-interrupt-controller";
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/boot/dts/mti/ |
| D | sead3.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
8 #include <dt-bindings/interrupt-controller/mips-gic.h>
11 #address-cells = <1>;
12 #size-cells = <1>;
13 compatible = "mti,sead-3";
14 model = "MIPS SEAD-3";
17 stdout-path = "serial1:115200";
36 cpu_intc: interrupt-controller {
37 compatible = "mti,cpu-interrupt-controller";
[all …]
|
| /kernel/linux/linux-5.10/drivers/leds/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 bool "LED Support"
12 Say Y to enable Linux LED support. This allows control of supported
18 tristate "LED Class Support"
20 This option enables the LED sysfs class in /sys/class/leds. You'll
24 tristate "LED Flash Class Support"
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
30 for the flash related features of a LED device. It can be built
34 tristate "LED Multicolor Class Support"
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller
3 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268.
6 controller), which can either be controlled by software (exporting the 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
13 BCM6328 LED controller has a HWDIS register, which controls whether a LED
16 is usually 1:1 for hardware to LED signals, but through the activity/link
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-sc27xx-bltc.txt | 1 LEDs connected to Spreadtrum SC27XX PMIC breathing light controller
3 The SC27xx breathing light controller supports to 3 outputs:
4 red LED, green LED and blue LED. Each LED can work at normal
8 - compatible: Should be "sprd,sc2731-bltc".
9 - #address-cells: Must be 1.
10 - #size-cells: Must be 0.
11 - reg: Specify the controller address.
14 - reg: Port this LED is connected to.
17 - label: See Documentation/devicetree/bindings/leds/common.txt.
21 led-controller@200 {
[all …]
|
| D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller
3 This controller is present on BCM6358 and BCM6368.
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.
[all …]
|
| D | leds-mt6323.txt | 1 Device Tree Bindings for LED support on MT6323 PMIC
3 MT6323 LED controller is subfunction provided by MT6323 PMIC, so the LED
5 PMIC controller that is being defined as one kind of Muti-Function Device (MFD)
15 - compatible : Must be "mediatek,mt6323-led"
16 - address-cells : Must be 1
17 - size-cells : Must be 0
19 Each led is represented as a child node of the mediatek,mt6323-led that
20 describes the initial behavior for each LED physically and currently only four
21 LED child nodes can be supported.
23 Required properties for the LED child node:
[all …]
|
| D | leds-lt3593.txt | 1 Bindings for Linear Technologies LT3593 LED controller
4 - compatible: Should be "lltc,lt3593".
5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL'
8 The hardware supports only one LED. The properties of this LED are
9 configured in a sub-node in the device node.
11 Optional sub-node properties:
12 - label: A label for the LED. If none is given, the LED will be
14 - linux,default-trigger: The default trigger for the LED.
16 - default-state: The initial state of the LED.
24 led-controller {
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller
3 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268.
6 controller), which can either be controlled by software (exporting the 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
13 BCM6328 LED controller has a HWDIS register, which controls whether a LED
16 is usually 1:1 for hardware to LED signals, but through the activity/link
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-sc27xx-bltc.txt | 1 LEDs connected to Spreadtrum SC27XX PMIC breathing light controller
3 The SC27xx breathing light controller supports to 3 outputs:
4 red LED, green LED and blue LED. Each LED can work at normal
8 - compatible: Should be "sprd,sc2731-bltc".
9 - #address-cells: Must be 1.
10 - #size-cells: Must be 0.
11 - reg: Specify the controller address.
14 - reg: Port this LED is connected to.
17 - function: See Documentation/devicetree/bindings/leds/common.txt.
18 - color: See Documentation/devicetree/bindings/leds/common.txt.
[all …]
|
| D | ti,tca6507.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TCA6507 LED and GPIO controller
10 - NeilBrown <neilb@suse.de>
13 The TCA6507 is a programmable LED controller connected via I2C that can drive
22 description: I2C slave address of the controller.
25 "#address-cells":
28 "#size-cells":
31 gpio-controller: true
[all …]
|
| D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller
3 This controller is present on BCM6358 and BCM6368.
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.
[all …]
|
| D | leds-mt6323.txt | 1 Device Tree Bindings for LED support on MT6323 PMIC
3 MT6323 LED controller is subfunction provided by MT6323 PMIC, so the LED
5 PMIC controller that is being defined as one kind of Muti-Function Device (MFD)
15 - compatible : Must be "mediatek,mt6323-led"
16 - address-cells : Must be 1
17 - size-cells : Must be 0
19 Each led is represented as a child node of the mediatek,mt6323-led that
20 describes the initial behavior for each LED physically and currently only four
21 LED child nodes can be supported.
23 Required properties for the LED child node:
[all …]
|
| D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
14 LED and flash LED devices provide the same basic functionality as current
15 regulators, but extended with LED and flash LED specific features like
18 Many LED devices expose more than one current output that can be connected
19 to one or more discrete LED component. Since the arrangement of connections
20 can influence the way of the LED device initialization, the LED components
[all …]
|
| D | leds-lt3593.txt | 1 Bindings for Linear Technologies LT3593 LED controller
4 - compatible: Should be "lltc,lt3593".
5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL'
8 The hardware supports only one LED. The properties of this LED are
9 configured in a sub-node in the device node.
11 Optional sub-node properties:
12 - function: See Documentation/devicetree/bindings/leds/common.txt
13 - color: See Documentation/devicetree/bindings/leds/common.txt
14 - label: A label for the LED. If none is given, the LED will be
16 - linux,default-trigger: The default trigger for the LED.
[all …]
|
| D | leds-an30259a.txt | 1 * Panasonic AN30259A 3-channel LED driver
3 The AN30259A is a LED controller capable of driving three LEDs independently. It supports
7 - compatible: Must be "panasonic,an30259a".
8 - reg: I2C slave address.
9 - #address-cells: Must be 1.
10 - #size-cells: Must be 0.
12 Each LED is represented as a sub-node of the panasonic,an30259a node.
14 Required sub-node properties:
15 - reg: Pin that the LED is connected to. Must be 1, 2, or 3.
17 Optional sub-node properties:
[all …]
|
| D | cznic,turris-omnia-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marek Behún <marek.behun@nic.cz>
15 microcontroller that communicates via the I2C bus. Each LED is described
20 const: cznic,turris-omnia-leds
26 "#address-cells":
29 "#size-cells":
33 "^multi-led@[0-9a-b]$":
[all …]
|
| /kernel/linux/linux-4.19/drivers/leds/ |
| D | Kconfig | 9 bool "LED Support"
11 Say Y to enable Linux LED support. This allows control of supported
17 tristate "LED Class Support"
19 This option enables the led sysfs class in /sys/class/leds. You'll
23 tristate "LED Flash Class Support"
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
29 for the flash related features of a LED device. It can be built
33 bool "LED Class brightness_hw_changed attribute support"
37 for led sysfs class devices under /sys/class/leds.
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | versatile-ab.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
6 compatible = "arm,versatile-ab";
7 #address-cells = <1>;
8 #size-cells = <1>;
9 interrupt-parent = <&vic>;
19 stdout-path = &uart0;
28 #clock-cells = <0>;
29 compatible = "fixed-clock";
30 clock-frequency = <24000000>;
[all …]
|
| D | arm-realview-pb1176.dts | 23 /dts-v1/;
24 #include <dt-bindings/interrupt-controller/irq.h>
25 #include <dt-bindings/gpio/gpio.h>
28 #address-cells = <1>;
29 #size-cells = <1>;
31 compatible = "arm,realview-pb1176";
50 vmmc: regulator-vmmc {
51 compatible = "regulator-fixed";
52 regulator-name = "vmmc";
53 regulator-min-microvolt = <3300000>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mt7622.txt | 1 == MediaTek MT7622 pinctrl controller ==
4 - compatible: Should be one of the following
5 "mediatek,mt7622-pinctrl" for MT7622 SoC
6 "mediatek,mt7629-pinctrl" for MT7629 SoC
7 - reg: offset and length of the pinctrl space
9 - gpio-controller: Marks the device node as a GPIO controller.
10 - #gpio-cells: Should be two. The first cell is the pin number and the
14 - interrupt-controller : Marks the device node as an interrupt controller
16 If the property interrupt-controller is defined, following property is required
17 - reg-names: A string describing the "reg" entries. Must contain "eint".
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | versatile-ab.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
7 compatible = "arm,versatile-ab";
8 #address-cells = <1>;
9 #size-cells = <1>;
10 interrupt-parent = <&vic>;
20 stdout-path = &uart0;
28 #clock-cells = <0>;
29 compatible = "fixed-clock";
30 clock-frequency = <24000000>;
[all …]
|
12345678910>>...41