Home
last modified time | relevance | path

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

12345678910>>...45

/freebsd/sys/contrib/device-tree/Bindings/leds/
H A Dcommon.yaml1 # 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 …]
H A Dleds-mt6360.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-mt6360.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LED driver for MT6360 PMIC from MediaTek Integrated.
10 - Gene Chen <gene_chen@richtek.com>
15 Add MT6360 LED driver include 2-channel Flash LED with torch/strobe mode,
16 and 4-channel RGB LED support Register/Flash/Breath Mode
20 const: mediatek,mt6360-led
22 "#address-cells":
[all …]
H A Dleds-lp55xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lp55xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI/National Semiconductor LP55xx and LP8501 LED Drivers
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
15 LED Drivers.
27 - national,lp5521
28 - national,lp5523
[all …]
H A Dqcom,spmi-flash-led.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/qcom,spmi-flas
[all...]
H A Dregister-bit-led.txt5 single LED. The register bit LEDs appear as children to the
10 Each LED is represented as a sub-node of the syscon device. Each
11 node's name represents the name of the corresponding LED.
13 LED sub-node properties:
16 - compatible : must be "register-bit-led"
17 - offset : register offset to the register controlling this LED
18 - mask : bit mask for the bit controlling this LED in the register
22 - label : (optional)
24 - linux,default-trigger : (optional)
26 - default-state: (optional) The initial state of the LED
[all …]
H A Dleds-lp55xx.txt1 Binding for TI/National Semiconductor LP55xx Led Drivers
4 - compatible: one of
11 - reg: I2C slave address
12 - clock-mode: Input clock mode, (0: automode, 1: internal, 2: external)
15 - led-cur: Current setting at each led channel (mA x10, 0 if led is not connected)
16 - max-cur: Maximun current at each led channel.
19 - enable-gpio: GPIO attached to the chip's enable pin
20 - label: Used for naming LEDs
21 - pwr-sel: LP8501 specific property. Power selection for output channels.
28 - chan-name (optional): name of channel
[all …]
H A Dleds-pm8058.txt1 Qualcomm PM8058 LED driver
3 The Qualcomm PM8058 is a multi-functional device which contains
4 an LED driver block for up to six LEDs: three normal LEDs, two
5 "flash" LEDs and one "keypad backlight" LED. The names are
6 quoted because sometimes these LED drivers are used for wildly
8 are more of a suggestion than a hard-wired usecase.
10 Hardware-wise the different LEDs support slightly different
12 do they support external triggers. They are just powerful LED
17 mfd/qcom-pm8xxx.txt.
19 Each LED is represented as a sub-node of the syscon device. Each
[all …]
H A Dleds-bcm6328.txt7 as spi-gpio. See Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml),
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".
25 - #address-cells : must be 1.
26 - #size-cells : must be 0.
27 - reg : BCM6328 LED controller address and size.
[all …]
H A Dleds-mt6323.txt1 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 one of
16 - "mediatek,mt6323-led"
17 - "mediatek,mt6331-led"
18 - "mediatek,mt6332-led"
19 - address-cells : Must be 1
20 - size-cells : Must be 0
22 Each led is represented as a child node of the mediatek,mt6323-led that
[all …]
H A Dleds-bcm6328.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
17 as spi-gpio. See
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
24 BCM6328 LED controller has a HWDIS register, which controls whether a LED
27 is usually 1:1 for hardware to LED signals, but through the activity/link
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
[all …]
H A Dawinic,aw200xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: AWINIC AW200XX LED
10 - Martin Kurbanov <mmkurbanov@sberdevices.ru>
13 It is a matrix LED driver programmed via an I2C interface. Devices have
16 - AW20036 (3x12) 36 LEDs
17 - AW20054 (6x9) 54 LEDs
18 - AW20072 (6x12) 72 LEDs
19 - AW20108 (9x12) 108 LEDs
[all …]
H A Dleds-lp50xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lp50xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LED driver for LP50XX RGB LED from Texas Instruments.
10 - Andrew Davis <afd@ti.com>
13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into
14 a LED group or control them individually.
16 The difference in these RGB LED drivers is the number of supported RGB
27 - ti,lp5009
[all …]
H A Dleds-cpcap.txt2 ------------------------
5 chip see Documentation/devicetree/bindings/mfd/motorola-cpcap.txt.
8 - compatible: should be one of
9 * "motorola,cpcap-led-mdl" (Main Display Lighting)
10 * "motorola,cpcap-led-kl" (Keyboard Lighting)
11 * "motorola,cpcap-led-adl" (Aux Display Lighting)
12 * "motorola,cpcap-led-red" (Red Triode)
13 * "motorola,cpcap-led-green" (Green Triode)
14 * "motorola,cpcap-led-blue" (Blue Triode)
15 * "motorola,cpcap-led-cf" (Camera Flash)
[all …]
H A Dleds-lm3532.txt1 * Texas Instruments - lm3532 White LED driver with ambient light sensing
4 The LM3532 provides the 3 high-voltage, low-side current sinks. The device is
5 programmable over an I2C-compatible interface and has independent
7 method allows for different LED currents in each current sink thus allowing
11 each with 32 internal voltage setting resistors, 8-bit logarithmic and linear
16 - compatible : "ti,lm3532"
17 - reg : I2C slave address
18 - #address-cells : 1
19 - #size-cells : 0
22 - enable-gpios : gpio pin to enable (active high)/disable the device.
[all …]
/freebsd/sys/contrib/device-tree/src/arm/ti/omap/
H A Domap3-echo.dts1 // SPDX-License-Identifier: GPL-2.0-only
5 /dts-v1/;
9 #include <dt-bindings/input/input.h>
10 #include <dt-bindings/leds/common.h>
14 compatible = "amazon,omap3-echo", "ti,omap3630", "ti,omap3";
18 cpu0-supply = <&vdd1_reg>;
28 compatible = "regulator-fixed";
29 regulator-name = "vcc5v";
30 regulator-min-microvolt = <5000000>;
31 regulator-max-microvolt = <5000000>;
[all …]
/freebsd/sys/contrib/device-tree/src/arm/aspeed/
H A Daspeed-bmc-ibm-blueridge.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include <dt-bindings/gpio/aspeed-gpio.h>
6 #include <dt-bindings/i2c/i2c.h>
7 #include <dt-bindings/leds/leds-pca955x.h>
8 #include "aspeed-g6.dtsi"
9 #include "ibm-power11-quad.dtsi"
13 compatible = "ibm,blueridge-bmc", "aspeed,ast2600";
35 stdout-path = &uart5;
43 reserved-memory {
[all …]
H A Daspeed-bmc-ibm-rainier.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include "aspeed-g6.dtsi"
6 #include <dt-bindings/gpio/aspeed-gpio.h>
7 #include <dt-bindings/i2c/i2c.h>
8 #include <dt-bindings/leds/leds-pca955x.h>
12 compatible = "ibm,rainier-bmc", "aspeed,ast2600";
34 stdout-path = &uart5;
43 reserved-memory {
44 #address-cells = <1>;
[all …]
H A Daspeed-bmc-ibm-fuji.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include <dt-bindings/gpio/aspeed-gpio.h>
6 #include <dt-bindings/i2c/i2c.h>
7 #include <dt-bindings/leds/leds-pca955x.h>
8 #include "aspeed-g6.dtsi"
9 #include "ibm-power11-quad.dtsi"
13 compatible = "ibm,fuji-bmc", "aspeed,ast2600";
170 stdout-path = &uart5;
178 reserved-memory {
[all …]
/freebsd/sys/contrib/device-tree/src/mips/mti/
H A Dsead3.dts1 // 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 …]
/freebsd/sys/contrib/device-tree/src/arm/marvell/
H A Dkirkwood-nsa310a.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "kirkwood-nsa3x0-common.dtsi"
8 * not have the red USB Led.
12 compatible = "zyxel,nsa310a", "zyxel,nsa310", "marvell,kirkwood-88f6281", "marvell,kirkwood";
21 stdout-path = &uart0;
25 pinctrl: pin-controller@10000 {
26 pinctrl-names = "default";
28 pmx_led_esata_green: pmx-led-esata-green {
33 pmx_led_esata_red: pmx-led-esata-red {
[all …]
H A Dkirkwood-nsa310.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "kirkwood-nsa3x0-common.dtsi"
7 compatible = "zyxel,nsa310", "marvell,kirkwood-88f6281", "marvell,kirkwood";
16 stdout-path = &uart0;
20 pinctrl: pin-controller@10000 {
21 pinctrl-0 = <&pmx_unknown>;
22 pinctrl-names = "default";
24 pmx_led_esata_green: pmx-led-esata-green {
29 pmx_led_esata_red: pmx-led-esata-red {
[all …]
H A Dkirkwood-iomega_ix2_200.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
5 #include "kirkwood-6281.dtsi"
8 model = "Iomega StorCenter ix2-200";
9 compatible = "iom,ix2-200", "marvell,kirkwood-88f6281", "marvell,kirkwood";
18 stdout-path = &uart0;
22 pinctrl: pin-controller@10000 {
23 pinctrl-0 = < &pmx_led_sata_brt_ctrl_1
33 pinctrl-names = "default";
35 pmx_button_reset: pmx-button-reset {
[all …]
/freebsd/sys/contrib/dev/iwlwifi/mvm/
H A Dled.c1 // SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
3 * Copyright (C) 2012-2014, 2018-2019 Intel Corporation
7 #include "iwl-io.h"
8 #include "iwl-csr.h"
30 IWL_WARN(mvm, "LED command failed: %d\n", err); in iwl_mvm_send_led_fw_cmd()
35 if (fw_has_capa(&mvm->fw->ucode_capa, in iwl_mvm_led_set()
41 iwl_write32(mvm->trans, CSR_LED_REG, in iwl_mvm_led_set()
48 struct iwl_mvm *mvm = container_of(led_cdev, struct iwl_mvm, led); in iwl_led_brightness_set()
60 IWL_ERR(mvm, "Blink led mode not supported, used default\n"); in iwl_mvm_leds_init()
67 IWL_INFO(mvm, "Led disabled\n"); in iwl_mvm_leds_init()
[all …]
/freebsd/sys/contrib/device-tree/src/mips/brcm/
H A Dbcm63268-comtrend-vr-3032u.dts1 // 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;
27 led@0 {
29 brcm,hardware-controlled;
[all …]
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/
H A Dmarvell,armada-375-pinctrl.txt3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding
7 - compatible: "marvell,88f6720-pinctrl"
8 - reg: register specifier of MPP registers
18 mpp2 2 gpio, dev(ad4), ptp(evreq), led(c0), audio(sdi)
19 mpp3 3 gpio, dev(ad5), ptp(trig), led(p3), audio(mclk)
22 mpp6 6 gpio, dev(ad0), led(p1), audio(lrclk)
23 mpp7 7 gpio, dev(ad1), ptp(clk), led(p2), audio(extclk)
26 mpp10 10 gpio, dram(vttctrl), led(c1), nand(re)
27 mpp11 11 gpio, dev(a0), led(c2), audio(sdo)
40 mpp24 24 gpio, led(p0), ge1(rxd0), sd(cmd), uart0(rts)
[all …]

12345678910>>...45