/freebsd/sys/contrib/device-tree/Bindings/leds/ |
H A D | leds-bcm6328.txt | 7 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 D | leds-bcm6328.yaml | 1 # 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 D | leds-bcm6358.txt | 5 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 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 …]
|
H A D | leds-pwm-multicolor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-pwm-multicolor.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Multi-color LEDs connected to PWM 10 - Sven Schwermer <sven.schwermer@disruptive-technologies.com> 13 This driver combines several monochrome PWM LEDs into one multi-color 14 LED using the multicolor LED class. 18 const: pwm-leds-multicolor 20 multi-led: [all …]
|
H A D | leds-pwm.txt | 1 LED connected to PWM 4 - compatible : should be "pwm-leds". 6 Each LED is represented as a sub-node of the pwm-leds device. Each 7 node's name represents the name of the corresponding LED. 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 [all …]
|
/freebsd/sys/contrib/device-tree/src/mips/brcm/ |
H A 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; 27 led@0 { 29 brcm,hardware-controlled; [all …]
|
H A D | bcm6358-neufbox4-sercomm.dts | 1 // 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 …]
|
/freebsd/sys/contrib/device-tree/Bindings/leds/irled/ |
H A D | spi-ir-led.txt | 1 Device tree bindings for IR LED connected through SPI bus which is used as 4 The IR LED switch is connected to the MOSI line of the SPI device and the data 8 - compatible: should be "ir-spi-led". 11 - duty-cycle: 8 bit value that represents the percentage of one period 12 in which the signal is active. It can be 50, 60, 70, 75, 80 or 90. 13 - led-active-low: boolean value that specifies whether the output is 15 - power-supply: specifies the power source. It can either be a regulator 16 or a gpio which enables a regulator, i.e. a regulator-fixed as 18 Documentation/devicetree/bindings/regulator/fixed-regulator.yaml 23 compatible = "ir-spi-led"; [all …]
|
H A D | ir-spi-led.yaml | 1 # 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 …]
|
/freebsd/sys/contrib/device-tree/src/riscv/sifive/ |
H A D | hifive-unleashed-a00.dts | 1 // 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 D | hifive-unmatched-a00.dts | 1 // 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-unmatche [all...] |
/freebsd/sys/contrib/device-tree/src/arm/st/ |
H A D | stm32mp157c-lxa-tac-gen2.dts | 1 // 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 D | stm32mp157c-lxa-mc1.dts | 1 /* 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 …]
|
H A D | stih410-b2260.dts | 1 // SPDX-License-Identifier: GPL-2.0-only 6 /dts-v1/; 8 #include <dt-bindings/gpio/gpio.h> 12 compatible = "st,stih410-b2260", "st,stih410"; 15 stdout-path = &uart1; 29 compatible = "gpio-leds"; 30 led-user-green-1 { 33 linux,default-trigger = "heartbeat"; 34 default-state = "off"; 37 led-user-green-2 { [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/broadcom/bcmbca/ |
H A D | bcm4908-asus-gt-ac5300.dts | 1 // 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 …]
|
/freebsd/sys/contrib/device-tree/src/arm/marvell/ |
H A D | kirkwood-l-50.dts | 1 // SPDX-License-Identifier: GPL-2.0 3 * Check Point L-50 Board Description 7 /dts-v1/; 10 #include "kirkwood-6281.dtsi" 13 model = "Check Point L-50"; 14 compatible = "checkpoint,l-50", "marvell,kirkwood-88f6281", "marvell,kirkwood"; 23 stdout-path = &uart0; 27 pinctrl: pin-controller@10000 { 28 pinctrl-0 = <&pmx_led38 &pmx_sysrst &pmx_button29>; 29 pinctrl-names = "default"; [all …]
|
H A 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-A51 [all...] |
/freebsd/share/man/man4/man4.i386/ |
H A D | CPU_ELAN.4 | 1 .\" Copyright (c) 2003 Poul-Henning Kamp <phk@FreeBSD.org> 35 .Bl -item -compact 48 .Pa /dev/elan-mmcr 74 .Ql - 78 (lower-case ell) configures a 79 .Xr led 4 80 device (active low). 84 .Xr led 4 85 device (active high). 90 .Xr led 4 [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/input/ |
H A D | microchip,cap11xx.yaml | 1 # 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-channe [all...] |
/freebsd/sys/contrib/device-tree/src/arm64/mediatek/ |
H A D | mt7986a-bananapi-bpi-r3.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT) 5 * Frank Wunderlich <frank-w@public-files.de> 9 /dts-v1/; 10 #include <dt-bindings/gpio/gpio.h> 11 #include <dt-bindings/input/input.h> 12 #include <dt-bindings/leds/common.h> 13 #include <dt-bindings/pinctrl/mt65xx.h> 18 model = "Bananapi BPI-R3"; 19 chassis-type = "embedded"; 20 compatible = "bananapi,bpi-r3", "mediatek,mt7986a"; [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/gpio/ |
H A D | gpio.txt | 5 ----------------- 7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose 8 of this GPIO for the device. While a non-existent <name> is considered valid 10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old 24 and bit-banged data signals: 27 gpio-controller; 28 #gpio-cells = <2>; 32 data-gpios = <&gpio1 12 0>, 39 such as if the consumer desire the line to be active low (inverted) or open 44 recommended to use the two-cell approach. [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/rockchip/ |
H A D | rk3399-ficus.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 9 /dts-v1/; 10 #include "rk3399-rock960.dtsi" 21 stdout-path = "serial2:1500000n8"; 24 clkin_gmac: external-gmac-clock { 25 compatible = "fixed-clock"; 26 clock-frequenc [all...] |
/freebsd/sys/contrib/device-tree/Bindings/mfd/ |
H A 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, 21 sub-system directories. [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
H A D | brcm,nsp-gpio.txt | 4 - compatible: 5 Must be "brcm,nsp-gpio-a" 7 - reg: 11 - #gpio-cells: 14 bit[0]: polarity (0 for active high and 1 for active low) 16 - gpio-controller: 19 - ngpios: 23 - interrupts: 26 - interrupt-controller: 29 - gpio-ranges: [all …]
|