/freebsd/sys/contrib/device-tree/src/arm/nuvoton/ |
H A D | nuvoton-npcm750-runbmc-olympus.dts | 1 // SPDX-License-Identifier: GPL-2.0 5 /dts-v1/; 6 #include "nuvoton-npcm750.dtsi" 7 #include "nuvoton-npcm750-runbmc-olympus-pincfg.dtsi" 9 #include <dt-bindings/i2c/i2c.h> 10 #include <dt-bindings/gpio/gpio.h> 43 stdout-path = &serial3; 50 iio-hwmon { 51 compatible = "iio-hwmon"; 52 io-channels = <&adc 0>, <&adc 1>, <&adc 2>, <&adc 3>, [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/hisilicon/ |
H A D | hi3670-hikey970.dts | 1 // SPDX-License-Identifier: GPL-2.0 10 /dts-v1/; 11 #include <dt-bindings/gpio/gpio.h> 14 #include "hikey970-pinctrl.dtsi" 15 #include "hikey970-pmic.dtsi" 19 compatible = "hisilicon,hi3670-hikey970", "hisilicon,hi3670"; 34 stdout-path = "serial6:115200n8"; 43 wlan_en: wlan-en-1-8v { 44 compatible = "regulator-fixed"; 45 regulator-name = "wlan-en-regulator"; [all …]
|
H A D | hi3660-hikey960.dts | 1 // SPDX-License-Identifier: GPL-2.0 9 /dts-v1/; 12 #include "hikey960-pinctrl.dtsi" 13 #include <dt-bindings/gpio/gpio.h> 14 #include <dt-bindings/input/input.h> 15 #include <dt-bindings/interrupt-controller/irq.h> 16 #include <dt-bindings/usb/pd.h> 20 compatible = "hisilicon,hi3660-hikey960", "hisilicon,hi3660"; 35 stdout-path = "serial6:115200n8"; 44 reserved-memory { [all …]
|
H A D | hi6220-hikey.dts | 1 // SPDX-License-Identifier: GPL-2.0 9 /dts-v1/; 11 #include "hikey-pinctrl.dtsi" 12 #include <dt-bindings/gpio/gpio.h> 16 compatible = "hisilicon,hi6220-hikey", "hisilicon,hi6220"; 26 stdout-path = "serial3:115200n8"; 32 * 0x05e0,0000 - 0x05ef,ffff: MCU firmware runtime using 33 * 0x05f0,1000 - 0x05f0,1fff: Reboot reason 34 * 0x06df,f000 - 0x06df,ffff: Mailbox message data 35 * 0x0740,f000 - 0x0740,ffff: MCU firmware section [all …]
|
H A D | hi3798cv200-poplar.dts | 1 // SPDX-License-Identifier: GPL-2.0 5 * Copyright (c) 2016-2017 HiSilicon Technologies Co., Ltd. 8 /dts-v1/; 10 #include <dt-bindings/gpio/gpio.h> 12 #include "poplar-pinctrl.dtsi" 16 compatible = "hisilicon,hi3798cv200-poplar", "hisilicon,hi3798cv200"; 24 stdout-path = "serial0:115200n8"; 33 compatible = "gpio-leds"; 35 user-led0 { 38 linux,default-trigger = "heartbeat"; [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/media/ |
H A D | cec-gpio.txt | 1 * HDMI CEC GPIO driver 3 The HDMI CEC GPIO module supports CEC implementations where the CEC line 4 is hooked up to a pull-up GPIO line and - optionally - the HPD line is 5 hooked up to another GPIO line. 7 Please note: the maximum voltage for the CEC line is 3.63V, for the HPD and 9 when connecting them to a GPIO line. 12 - compatible: value must be "cec-gpio". 13 - cec-gpios: gpio that the CEC line is connected to. The line should be 16 If the CEC line is associated with an HDMI receiver/transmitter, then the 19 - hdmi-phandle - phandle to the HDMI controller, see also cec.txt. [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/gpio/ |
H A D | gpio-mmio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/gpio/gpio-mmio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Generic MMIO GPIO 10 - Linus Walleij <linus.walleij@linaro.org> 11 - Bartosz Golaszewski <brgl@bgdev.pl> 14 Some simple GPIO controllers may consist of a single data register or a pair 15 of set/clear-bit registers. Such controllers are common for glue logic in 16 FPGAs or ASICs. Commonly, these controllers are accessed over memory-mapped [all …]
|
H A D | gpio.txt | 1 Specifying GPIO information for devices 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 14 GPIO properties can contain one or more GPIO phandles, but only in exceptional 18 several GPIOs serve the same function (e.g. a parallel data line). 23 The following example could be used to describe GPIO pins used as device enable 24 and bit-banged data signals: 27 gpio-controller; [all …]
|
H A D | gpio-zynq.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/gpio/gpio-zynq.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Xilinx Zynq GPIO controller 10 - Michal Simek <michal.simek@amd.com> 15 - xlnx,zynq-gpio-1.0 16 - xlnx,zynqmp-gpio-1.0 17 - xlnx,versal-gpio-1.0 18 - xlnx,pmc-gpio-1.0 [all …]
|
H A D | nxp,pcf8575.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/gpio/nxp,pcf8575.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: PCF857x-compatible I/O expanders 10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> 13 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be 14 driven high by a pull-up current source or driven low to ground. This 15 combines the direction and output level into a single bit per line, which 17 line is configured (a) as output and driving the signal low/high, or (b) as [all …]
|
H A D | gpio-pcf857x.txt | 1 * PCF857x-compatible I/O expanders 3 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be 4 driven high by a pull-up current source or driven low to ground. This combines 5 the direction and output level into a single bit per line, which can't be read 6 back. We can't actually know at initialization time whether a line is configured 9 of reset (if any). The only reliable solution for setting up line direction is 14 - compatible: should be one of the following. 15 - "maxim,max7328": For the Maxim MAX7378 16 - "maxim,max7329": For the Maxim MAX7329 17 - "nxp,pca8574": For the NXP PCA8574 [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
H A D | qcom,pmic-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pinctrl/qcom,pmic-gpio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm PMIC GPIO block 10 - Bjorn Andersson <bjorn.andersson@linaro.org> 13 This binding describes the GPIO block(s) found in the 8xxx series of 19 - enum: 20 - qcom,pm2250-gpio 21 - qcom,pm660-gpio [all …]
|
/freebsd/sys/contrib/device-tree/src/arm/aspeed/ |
H A D | aspeed-bmc-opp-palmetto.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 2 /dts-v1/; 4 #include "aspeed-g4.dtsi" 5 #include <dt-bindings/gpio/aspeed-gpio.h> 9 compatible = "tyan,palmetto-bmc", "aspeed,ast2400"; 12 stdout-path = &uart5; 20 reserved-memory { 21 #address-cells = <1>; 22 #size-cells = <1>; 26 no-map; [all …]
|
H A D | aspeed-bmc-lenovo-hr855xg2.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 5 * Copyright (C) 2019-present Lenovo 8 /dts-v1/; 10 #include "aspeed-g5.dtsi" 11 #include <dt-bindings/gpio/aspeed-gpio [all...] |
H A D | aspeed-bmc-lenovo-hr630.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 5 * Copyright (C) 2019-present Lenovo 8 /dts-v1/; 10 #include "aspeed-g5.dtsi" 11 #include <dt-bindings/gpio/aspeed-gpio [all...] |
H A D | aspeed-bmc-facebook-bletchley.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 3 /dts-v1/; 5 #include "aspeed-g6.dtsi" 6 #include <dt-bindings/gpio/aspeed-gpio.h> 7 #include <dt-binding [all...] |
H A D | aspeed-bmc-facebook-harma.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later 4 /dts-v1/; 5 #include "aspeed-g6.dtsi" 6 #include <dt-bindings/gpio/aspeed-gpio.h> 7 #include <dt-bindings/i2c/i2c.h> 11 compatible = "facebook,harma-bmc", "aspeed,ast2600"; 32 stdout-path = &uart5; 40 iio-hwmon { 41 compatible = "iio-hwmon"; 42 io-channels = <&adc0 0>, <&adc0 1>, <&adc0 2>, <&adc0 3>, [all …]
|
H A D | aspeed-bmc-opp-lanyang.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 3 /dts-v1/; 5 #include "aspeed-g5.dtsi" 6 #include <dt-bindings/gpio/aspeed-gpio.h> 10 compatible = "inventec,lanyang-bmc", "aspeed,ast2500"; 13 stdout-path = &uart5; 21 reserved-memory { 22 #address-cells = <1>; 23 #size-cells = <1>; 27 no-map; [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/input/ |
H A D | gpio-mouse.txt | 1 Device-Tree bindings for GPIO attached mice 3 This simply uses standard GPIO handles to define a simple mouse connected 4 to 5-7 GPIO lines. 7 - compatible: must be "gpio-mouse" 8 - scan-interval-ms: The scanning interval in milliseconds 9 - up-gpios: GPIO line phandle to the line indicating "up" 10 - down-gpios: GPIO line phandle to the line indicating "down" 11 - left-gpios: GPIO line phandle to the line indicating "left" 12 - right-gpios: GPIO line phandle to the line indicating "right" 15 - button-left-gpios: GPIO line handle to the left mouse button [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/media/cec/ |
H A D | cec-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/media/cec/cec-gpio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: HDMI CEC GPIO 10 - Hans Verkuil <hverkuil-cisco@xs4all.nl> 13 The HDMI CEC GPIO module supports CEC implementations where the CEC line is 14 hooked up to a pull-up GPIO line and - optionally - the HPD line is hooked up 15 to another GPIO line. 17 Please note:: the maximum voltage for the CEC line is 3.63V, for the HPD and [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/mediatek/ |
H A D | pumpkin-common.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 7 #include <dt-bindings/gpio/gpio.h> 16 stdout-path = "serial0:921600n8"; 21 compatible = "linaro,optee-tz"; 26 gpio-keys { 27 compatible = "gpio-keys"; 28 pinctrl-names = "default"; 29 pinctrl-0 = <&gpio_keys_default>; 31 key-volume-up { 35 wakeup-source; [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/bitmain/ |
H A D | bm1880-sophon-edge.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 7 /dts-v1/; 12 * GPIO name legend: proper name = the GPIO line is used as GPIO 15 * "[PER]" = pin is muxed for [peripheral] (not GPIO) 19 * Line names are taken from the schematic "sophon-edge-schematics" 26 * When the 96Board naming of a line and the schematic name of 27 * the same line are in conflict, the 96Board specification 29 * lines i.e. "[FOO]", the GPIO named lines "GPIO-A" thru "GPIO-L" 30 * are the only ones actually used for GPIO. 34 compatible = "bitmain,sophon-edge", "bitmain,bm1880"; [all …]
|
/freebsd/sys/contrib/device-tree/src/arm/st/ |
H A D | ste-hrefv60plus.dtsi | 1 // SPDX-License-Identifier: GPL-2.0-or-later 3 * Copyright 2012 ST-Ericsson AB 6 #include "ste-href.dtsi" 9 model = "ST-Ericsson HREF (v60+) platform with Device Tree"; 10 compatible = "st-ericsson,hrefv60+", "st-ericsso [all...] |
/freebsd/sys/contrib/device-tree/src/arm/ti/omap/ |
H A D | am335x-netcom-plus-8xx.dts | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Copyright (C) 2012 Texas Instruments Incorporated - https://www.ti.com/ 11 /dts-v1/; 13 #include "am335x-baltos.dtsi" 20 pinctrl-names = "default"; 21 pinctrl-0 = <&dip_switches>; 23 dip_switches: dip-switches-pins { 24 pinctrl-single,pins = < 32 tca6416_pins: tca6416-pins { 33 pinctrl-single,pins = < [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/power/reset/ |
H A D | gpio-poweroff.txt | 1 Driver a GPIO line that can be used to turn the power off. 4 At driver load time, the driver will request the given gpio line and 6 'input' is not found, the GPIO line will be driven in the inactive 9 When the power-off handler is called, the gpio is configured as an 11 condition. This will also cause an inactive->active edge condition, so 13 the GPIO is set to inactive, thus causing an active->inactive edge, 15 delay the GPIO is driver active again. If the power is still on and 19 - compatible : should be "gpio-poweroff". 20 - gpios : The GPIO to set high/low, see "gpios property" in 21 Documentation/devicetree/bindings/gpio/gpio.txt. If the pin should be [all …]
|