Home
last modified time | relevance | path

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

12345678910>>...18

/openbmc/linux/Documentation/devicetree/bindings/leds/
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 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 …]
H A Dleds-bcm63138.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm63138.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rafał Miłecki <rafal@milecki.pl>
24 - items:
25 - enum:
26 - brcm,bcm4908-leds
27 - brcm,bcm6848-leds
28 - brcm,bcm6858-leds
[all …]
/openbmc/u-boot/doc/device-tree-bindings/leds/
H A Dleds-bcm6358.txt5 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.
21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device.
23 LED sub-node required properties:
[all …]
H A Dleds-bcm6328.txt7 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
14 - compatible : should be "brcm,bcm6328-leds".
15 - #address-cells : must be 1.
16 - #size-cells : must be 0.
17 - reg : BCM6328 LED controller address and size.
20 - brcm,serial-leds : Boolean, enables Serial LEDs.
22 - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
24 - brcm,serial-clk-low : Boolean, makes clock signal active low.
26 - brcm,serial-dat-low : Boolean, makes data signal active low.
[all …]
H A Dleds-gpio.txt4 - compatible : should be "gpio-leds".
6 Each LED is represented as a sub-node of the gpio-leds device. Each
7 node's name represents the name of the corresponding LED.
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)
15 - linux,default-trigger : (optional)
17 - default-state: (optional) The initial state of the LED. Valid
18 values are "on", "off", and "keep". If the LED is already on or off
[all …]
/openbmc/u-boot/arch/mips/dts/
H A Dnetgear,dgnd3700v2.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
19 stdout-path = "serial0:115200n8";
22 gpio-leds {
23 compatible = "gpio-leds";
50 compatible = "brcm,enetsw-port";
53 brcm,phy-id = <0xff>;
55 full-duplex;
56 bypass-link;
70 brcm,serial-leds;
[all …]
H A Dnetgear,cg3100d.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
19 stdout-path = "serial0:115200n8";
22 gpio-leds {
23 compatible = "gpio-leds";
45 led@0 {
47 active-low;
51 led@1 {
53 active-low;
57 led@2 {
[all …]
H A Dcomtrend,ar-5315u.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
11 model = "Comtrend AR-5315u";
12 compatible = "comtrend,ar5315-un", "brcm,bcm6318";
19 stdout-path = "serial0:115200n8";
31 compatible = "brcm,enetsw-port";
34 brcm,phy-id = <1>;
38 compatible = "brcm,enetsw-port";
41 brcm,phy-id = <2>;
45 compatible = "brcm,enetsw-port";
[all …]
H A Dcomtrend,vr-3032u.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
11 model = "Comtrend VR-3032u";
12 compatible = "comtrend,vr-3032u", "brcm,bcm63268";
19 stdout-path = "serial0:115200n8";
31 compatible = "brcm,enetsw-port";
34 brcm,phy-id = <1>;
38 compatible = "brcm,enetsw-port";
41 brcm,phy-id = <2>;
45 compatible = "brcm,enetsw-port";
[all …]
H A Dsfr,nb4-ser.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
12 compatible = "sfr,nb4-ser", "brcm,bcm6358";
19 stdout-path = "serial0:115200n8";
22 gpio-leds {
23 compatible = "gpio-leds";
26 label = "NB4-SER:white:traffic";
31 label = "NB4-SER:blue:service";
36 label = "NB4-SER:white:wifi";
41 label = "NB4-SER:red:service";
[all …]
/openbmc/linux/arch/mips/boot/dts/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 …]
H A 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 …]
/openbmc/linux/Documentation/devicetree/bindings/leds/irled/
H A Dir-spi-led.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/irled/ir-spi-led.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IR LED connected through SPI bus
10 - Sean Young <sean@mess.org>
13 IR LED switch is connected to the MOSI line of the SPI device and the data
17 - $ref: /schemas/spi/spi-peripheral-props.yaml#
21 const: ir-spi-led
26 duty-cycle:
[all …]
/openbmc/linux/arch/riscv/boot/dts/sifive/
H A Dhifive-unleashed-a00.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
2 /* Copyright (c) 2018-2019 SiFive, Inc */
4 #include "fu540-c000.dtsi"
5 #include <dt-bindings/gpio/gpio.h>
6 #include <dt-bindings/leds/common.h>
7 #include <dt-bindings/pwm/pwm.h>
14 compatible = "sifive,hifive-unleashed-a00", "sifive,fu540-c000",
18 stdout-path = "serial0";
22 timebase-frequency = <RTCCLK_FREQ>;
31 #clock-cells = <0>;
[all …]
H A Dhifive-unmatched-a00.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
4 #include "fu740-c000.dtsi"
5 #include <dt-bindings/gpio/gpio.h>
6 #include <dt-bindings/interrupt-controller/irq.h>
7 #include <dt-bindings/leds/common.h>
8 #include <dt-bindings/pwm/pwm.h>
15 compatible = "sifive,hifive-unmatched-a00", "sifive,fu740-c000",
19 stdout-path = "serial0";
23 timebase-frequency = <RTCCLK_FREQ>;
32 #clock-cells = <0>;
[all …]
/openbmc/linux/arch/arm/boot/dts/st/
H A Dstm32mp157c-lxa-tac-gen2.dts1 // SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-3-Clause)
3 * Copyright (C) 2020 STMicroelectronics - All Rights Reserved
8 /dts-v1/;
11 #include "stm32mp15xc-lxa-tac.dtsi"
15 compatible = "lxa,stm32mp157c-tac-gen2", "oct,stm32mp15xx-osd32", "st,stm32mp157";
18 compatible = "pwm-backlight";
19 power-supply = <&v3v3>;
21 brightness-levels = <0 31 63 95 127 159 191 223 255>;
22 default-brightness-level = <7>;
26 reg_iobus_12v: regulator-iobus-12v {
[all …]
H A Dstm32mp157c-lxa-mc1.dts1 /* SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-3-Clause) */
3 * Copyright (C) 2020 STMicroelectronics - All Rights Reserved
7 /dts-v1/;
10 #include "stm32mp15xx-osd32.dtsi"
11 #include "stm32mp15xxac-pinctrl.dtsi"
13 #include <dt-bindings/gpio/gpio.h>
14 #include <dt-bindings/pwm/pwm.h>
17 model = "Linux Automation MC-1 board";
18 compatible = "lxa,stm32mp157c-mc1", "oct,stm32mp15xx-osd32", "st,stm32mp157";
28 compatible = "pwm-backlight";
[all …]
/openbmc/linux/Documentation/driver-api/gpio/
H A Dboard.rst7 Note that it only applies to the new descriptor-based interface. For a
8 description of the deprecated integer-based GPIO interface please refer to
20 -----------
26 <function>-gpios, where <function> is the function the driver will request
32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
39 Properties named <function>-gpio are also considered valid and old bindings use
44 "led" function, and GPIO 1 as the "power" GPIO::
48 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
49 green = gpiod_get_index(dev, "led", 1, GPIOD_OUT_HIGH);
[all …]
/openbmc/linux/arch/arm64/boot/dts/broadcom/bcmbca/
H A Dbcm4908-asus-gt-ac5300.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
3 #include <dt-bindings/gpio/gpio.h>
4 #include <dt-bindings/input/input.h>
5 #include <dt-bindings/leds/common.h>
10 compatible = "asus,gt-ac5300", "brcm,bcm4908", "brcm,bcmbca";
11 model = "Asus GT-AC5300";
18 gpio-keys-polled {
19 compatible = "gpio-keys-polled";
20 poll-interval = <100>;
22 key-wifi {
[all …]
/openbmc/docs/designs/
H A Ddevice-tree-gpio-naming.md12 subsystem. The replacement is a "descriptor-based" character device interface.
25 specific field used to name the GPIOs in the DTS is `gpio-line-names`. This
29 scheme in the face of a universe of potential use-cases.
37 - Ensure common function GPIOs within OpenBMC use the same naming convention
52 Pattern: `*-button`
55 BMC-less machines use a button to trigger system behavior and in a BMC-managed
59 #### power-button
64 depends on the index of Host and the active state is high or low.
68 - `host*-ready`: Host ready, active high
69 - `host*-ready-n`: Host ready, active low
[all …]
/openbmc/linux/drivers/leds/
H A Dleds-bcm6358.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Driver for BCM6358 memory-mapped LEDs, based on leds-syscon.c
31 * struct bcm6358_led - state container for bcm6358 based LEDs
32 * @cdev: LED class device for this LED
35 * @pin: LED pin number
36 * @active_low: LED is active low
78 struct bcm6358_led *led = in bcm6358_led_set() local
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()
[all …]
/openbmc/openbmc-test-automation/ipmi/
H A Dtest_ipmi_general.robot45 ${uuid}= Remove String ${uuid} -
63 # [channel_protocol_type]: IPMB-1.0
64 # [session_support]: multi-session
67 # [volatile(active)_settings]:
69 # [per-message_auth]: enabled
72 # [Non-Volatile Settings]:
74 # [per-message_auth]: enabled
79 ${active_channel_config}= Get Active Channel Config
102 # Verify volatile(active)_settings
103 …Valid Value disabled_ipmi_conf_map['${channel_info_ipmi['volatile(active)_settings']['alerting']}…
[all …]
/openbmc/linux/arch/arm/boot/dts/marvell/
H A Ddove-cm-a510.dtsi2 * 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 …]
/openbmc/linux/Documentation/devicetree/bindings/input/
H A Dmicrochip,cap11xx.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The Microchip CAP1xxx Family of RightTouchTM multiple-channel capacitive
11 touch controllers and LED drivers. The device communication via I2C only.
14 - Rob Herring <robh@kernel.org>
19 - microchip,cap1106
20 - microchip,cap1126
21 - microchip,cap1188
22 - microchip,cap1203
[all …]

12345678910>>...18