Home
last modified time | relevance | path

Searched +full:white +full:- +full:led (Results 1 – 25 of 123) sorted by relevance

12345

/linux-6.12.1/arch/arm/boot/dts/broadcom/
Dbcm47094-linksys-panamera.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
6 /dts-v1/;
9 #include "bcm5301x-nand-cs0-bch8.dtsi"
30 gpio-keys {
31 compatible = "gpio-keys";
33 button-wps {
39 button-rfkill {
45 button-reset {
53 compatible = "gpio-leds";
55 led-wps {
[all …]
Dbcm4709-netgear-r7000.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
29 compatible = "gpio-leds";
31 led-power-white {
32 label = "bcm53xx:white:power";
34 linux,default-trigger = "default-on";
37 led-power-amber {
42 led-5ghz {
43 label = "bcm53xx:white:5ghz";
[all …]
Dbcm4708-smartrg-sr400ac.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
29 compatible = "gpio-leds";
31 led-power-white {
32 label = "bcm53xx:white:power";
34 linux,default-trigger = "default-on";
37 led-power-amber {
42 led-usb2 {
43 label = "bcm53xx:white:usb2";
[all …]
Dbcm4709-buffalo-wxr-1900dhp.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
4 * DTS for Buffalo WXR-1900DHP
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch8.dtsi"
15 compatible = "buffalo,wxr-1900dhp", "brcm,bcm4709", "brcm,bcm4708";
16 model = "Buffalo WXR-1900DHP";
29 compatible = "gpio-leds";
31 led-usb {
36 led-power-amber {
41 led-power-white {
[all …]
Dbcm4709-netgear-r8000.dts20 /dts-v1/;
23 #include "bcm5301x-nand-cs0-bch8.dtsi"
40 compatible = "gpio-leds";
42 led-power-white {
43 label = "bcm53xx:white:power";
45 linux,default-trigger = "default-on";
48 led-power-amber {
53 led-wan-white {
54 label = "bcm53xx:white:wan";
56 linux,default-trigger = "default-on";
[all …]
Dbcm47094-dlink-dir-890l.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
3 * Device tree for D-Link DIR-890L
4 * D-Link calls this board "WRGAC36"
5 * this router has the same looks and form factor as D-Link DIR-885L.
7 * Some differences from DIR-885L include a separate USB2 port, separate LEDs
13 * Based on the device tree for DIR-885L
18 /dts-v1/;
21 #include "bcm5301x-nand-cs0-bch1.dtsi"
24 compatible = "dlink,dir-890l", "brcm,bcm47094", "brcm,bcm4708";
25 model = "D-Link DIR-890L";
[all …]
Dbcm47094-netgear-r8500.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
6 /dts-v1/;
9 #include "bcm5301x-nand-cs0-bch8.dtsi"
26 compatible = "gpio-leds";
28 led-power0 {
29 label = "bcm53xx:white:power";
31 linux,default-trigger = "default-on";
34 led-power1 {
39 led-5ghz-1 {
40 label = "bcm53xx:white:5ghz-1";
[all …]
Dbcm47094-dlink-dir-885l.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
4 * DTS for D-Link DIR-885L
9 /dts-v1/;
12 #include "bcm5301x-nand-cs0-bch1.dtsi"
15 compatible = "dlink,dir-885l", "brcm,bcm47094", "brcm,bcm4708";
16 model = "D-Link DIR-885L";
33 #nvmem-cell-cells = <1>;
37 nand_controller: nand-controller@18028000 {
40 compatible = "fixed-partitions";
41 #address-cells = <1>;
[all …]
/linux-6.12.1/arch/arm/boot/dts/marvell/
Dkirkwood-goflexnet.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
5 #include "kirkwood-6281.dtsi"
9 compatible = "seagate,goflexnet", "marvell,kirkwood-88f6281", "marvell,kirkwood";
18 stdout-path = &uart0;
22 pinctrl: pin-controller@10000 {
23 pmx_usb_power_enable: pmx-usb-power-enable {
27 pmx_led_right_cap_0: pmx-led_right_cap_0 {
31 pmx_led_right_cap_1: pmx-led_right_cap_1 {
35 pmx_led_right_cap_2: pmx-led_right_cap_2 {
[all …]
Darmada-385-linksys-rango.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
9 #include <dt-bindings/gpio/gpio.h>
10 #include <dt-bindings/input/input.h>
11 #include "armada-385-linksys.dtsi"
26 label = "rango:white:wan";
31 label = "rango:white:usb2";
36 label = "rango:white:usb3_1";
41 label = "rango:white:usb3_2";
46 label = "rango:white:wps";
[all …]
Dkirkwood-dns325.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "kirkwood-dnskw.dtsi"
7 model = "D-Link DNS-325 NAS (Rev A1)";
8 …compatible = "dlink,dns-325-a1", "dlink,dns-325", "dlink,dns-kirkwood", "marvell,kirkwood-88f6281"…
17 stdout-path = &uart0;
20 gpio-leds {
21 compatible = "gpio-leds";
22 pinctrl-0 = <&pmx_led_power &pmx_led_red_usb_325
25 pinctrl-names = "default";
[all …]
Dkirkwood-linksys-viper.dts1 // SPDX-License-Identifier: GPL-2.0
3 * kirkwood-viper.dts - Device Tree file for Linksys viper (E4200v2 / EA4500)
12 /dts-v1/;
15 #include "kirkwood-6282.dtsi"
19 compatible = "linksys,viper", "marvell,kirkwood-88f6282", "marvell,kirkwood";
31 stdout-path = "serial0:115200n8";
35 compatible = "gpio-keys";
36 pinctrl-0 = < &pmx_btn_wps &pmx_btn_reset >;
37 pinctrl-names = "default";
39 button-wps {
[all …]
Darmada-385-linksys-caiman.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
9 #include "armada-385-linksys.dtsi"
24 label = "caiman:white:wan";
29 label = "caiman:white:wlan_2g";
34 label = "caiman:white:wlan_5g";
39 label = "caiman:white:usb2";
44 label = "caiman:white:usb3_1";
49 label = "caiman:white:usb3_2";
54 label = "caiman:white:wps";
[all …]
Darmada-385-linksys-cobra.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
9 #include "armada-385-linksys.dtsi"
24 label = "cobra:white:wan";
29 label = "cobra:white:wlan_2g";
34 label = "cobra:white:wlan_5g";
39 label = "cobra:white:usb2";
44 label = "cobra:white:usb3_1";
49 label = "cobra:white:usb3_2";
54 label = "cobra:white:wps";
[all …]
Darmada-385-linksys-shelby.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
8 /dts-v1/;
9 #include "armada-385-linksys.dtsi"
24 label = "shelby:white:wan";
29 label = "shelby:white:wlan_2g";
34 label = "shelby:white:wlan_5g";
39 label = "shelby:white:usb2";
44 label = "shelby:white:usb3_1";
49 label = "shelby:white:usb3_2";
54 label = "shelby:white:wps";
[all …]
Darmada-370-seagate-nas-xbay.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree common file for the Seagate NAS 2 and 4-bay (Armada 370 SoC).
11 * TODO: add support for the white SATA LEDs associated with HDD 0 and 1.
14 #include "armada-370.dtsi"
15 #include <dt-bindings/gpio/gpio.h>
16 #include <dt-bindings/input/input.h>
20 stdout-path = "serial0:115200n8";
32 internal-regs {
38 nr-ports = <2>;
44 pinctrl-0 = <&ge0_rgmii_pins>;
[all …]
Darmada-370-seagate-nas-4bay.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Device Tree file for Seagate NAS 4-Bay (Armada 370 SoC).
13 * Product name : Seagate NAS 4-Bay
14 * Code name (board/PCB) : Dart 4-Bay
19 /dts-v1/;
20 #include "armada-370-seagate-nas-xbay.dtsi"
21 #include <dt-bindings/leds/leds-ns2.h>
24 model = "Seagate NAS 4-Bay (Dart, SRPD40)";
25 compatible = "seagate,dart-4", "marvell,armada370", "marvell,armada-370-xp";
28 internal-regs {
[all …]
/linux-6.12.1/drivers/leds/
DTODO1 -*- org -*-
9 * Review atomicity requirements in LED subsystem
12 semantics is sometimes non-intuitive. (For example blink callback may
16 * LED names are still a mess
19 userland. Nudge authors into creating common LED names for common
22 ? Perhaps check for known LED names during boot, and warn if there are
27 The number of drivers is getting big, and driver for on/off LED on a
28 i/o port is really quite different from camera flash LED, which is
29 really different from driver for RGB color LED that can run its own
35 Green-Magenta-Ultraviolet LED, but so far all the LEDs we support are
[all …]
Dleds-acer-a500.c1 // SPDX-License-Identifier: GPL-2.0+
40 struct a500_led *led = container_of(led_cdev, struct a500_led, cdev); in a500_ec_led_brightness_set() local
45 control_seq[0] = led->enable_seq[0]; in a500_ec_led_brightness_set()
52 * RESET_LEDS turns off both LEDs, thus restore other LED if in a500_ec_led_brightness_set()
55 if (led->other->cdev.brightness) in a500_ec_led_brightness_set()
59 control_seq[1] = led->other->enable_seq[0]; in a500_ec_led_brightness_set()
62 return regmap_multi_reg_write(led->rmap, control_seq, num_regs); in a500_ec_led_brightness_set()
71 rmap = dev_get_regmap(pdev->dev.parent, "KB930"); in a500_ec_leds_probe()
73 return -EINVAL; in a500_ec_leds_probe()
78 white_led = devm_kzalloc(&pdev->dev, sizeof(*white_led), GFP_KERNEL); in a500_ec_leds_probe()
[all …]
/linux-6.12.1/arch/mips/boot/dts/brcm/
Dbcm6358-neufbox4-sercomm.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
7 compatible = "sfr,nb4-ser", "brcm,bcm6358";
17 stdout-path = &uart0;
24 led@0 {
26 active-low;
27 label = "nb4-ser:white:alarm";
29 led@2 {
31 active-low;
32 label = "nb4-ser:white:tv";
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/leds/
Dleds-lm3697.txt1 * Texas Instruments - LM3697 Highly Efficient White LED Driver
3 The LM3697 11-bit LED driver provides high-
5 LED strings while delivering up to 90% efficiency.
10 - compatible:
12 - reg : I2C slave address
13 - #address-cells : 1
14 - #size-cells : 0
17 - enable-gpios : GPIO pin to enable/disable the device
18 - vled-supply : LED supply
21 - reg : 0 - LED is Controlled by bank A
[all …]
Dleds-bcm6358.txt5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
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.
21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device.
23 LED sub-node required properties:
24 - reg : LED pin number (only LEDs 0 to 31 are valid).
[all …]
Dti.lm36922.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments - LM3692x Highly Efficient White LED Driver
10 - Dan Murphy <dmurphy@ti.com>
13 The LM3692x is an ultra-compact, highly efficient,
14 white-LED driver designed for LCD display backlighting.
17 LED strings it supports. The LM36922 supports two strings while the LM36923
26 - ti,lm36922
27 - ti,lm36923
[all …]
Dkinetic,ktd202x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Kinetic KTD2026/7 RGB/White LED Driver
10 - André Apitzsch <git@apitzsch.eu>
13 The KTD2026/7 is a RGB/White LED driver with I2C interface.
16 https://www.kinet-ic.com/uploads/KTD2026-7-04h.pdf
21 - kinetic,ktd2026
22 - kinetic,ktd2027
27 vin-supply:
[all …]
/linux-6.12.1/Documentation/leds/
Dleds-lp5562.rst5 * TI LP5562 LED Driver
12 LP5562 can drive up to 4 channels. R/G/B and White.
13 LEDs can be controlled directly via the led class control interface.
16 LP5562 has the internal program memory for running various LED patterns.
17 For the details, please refer to 'firmware' section in leds-lp55xx.txt
28 This attribute is used for programming LED data with the firmware interface.
32 LED Map
38 White ... Engine 1 or 2 or 3 (selective)
58 To run a blinking white pattern::
70 Please refer to 'leds-lp55xx.txt"
[all …]

12345