Home
last modified time | relevance | path

Searched +full:foo +full:- +full:gpios (Results 1 – 25 of 55) sorted by relevance

123

/kernel/linux/linux-4.19/Documentation/driver-api/gpio/
Dboard.rst5 This document explains how GPIOs can be assigned to given devices and functions.
7 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
9 gpio-legacy.txt (actually, there is no real mapping possible with the old
15 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
20 -----------
21 GPIOs can easily be mapped to devices and functions in the device tree. The
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
25 GPIOs mappings are defined in the consumer device's node, in a property named
26 <function>-gpios, where <function> is the function the driver will request
[all …]
/kernel/linux/linux-5.10/Documentation/driver-api/gpio/
Dboard.rst5 This document explains how GPIOs can be assigned to given devices and functions.
7 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
9 gpio-legacy.txt (actually, there is no real mapping possible with the old
15 Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
20 -----------
21 GPIOs can easily be mapped to devices and functions in the device tree. The
22 exact way to do it depends on the GPIO controller providing the GPIOs, see the
25 GPIOs mappings are defined in the consumer device's node, in a property named
26 <function>-gpios, where <function> is the function the driver will request
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/
Dgpio.txt4 1) gpios property
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
9 for compatibility reasons (resolving to the "gpios" property), it is not allowed
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
15 cases should they contain more than one. If your device uses several GPIOs with
17 meaningful name. The only case where an array of GPIOs is accepted is when
18 several GPIOs serve the same function (e.g. a parallel data line).
20 The exact purpose of each gpios property must be documented in the device tree
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dbcm2837-rpi-3-b-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2836-rpi.dtsi"
5 #include "bcm283x-rpi-lan7515.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,3-model-b-plus", "brcm,bcm2837";
14 stdout-path = "serial1:115200n8";
23 led-act {
24 gpios = <&gpio 29 GPIO_ACTIVE_HIGH>;
27 led-pwr {
[all …]
Dbcm2836-rpi-2-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2836-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9514.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,2-model-b", "brcm,bcm2836";
18 led-act {
19 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
22 led-pwr {
24 gpios = <&gpio 35 GPIO_ACTIVE_HIGH>;
[all …]
Dbcm2835-rpi-zero-w.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
8 #include "bcm2835-rpi.dtsi"
9 #include "bcm283x-rpi-usb-otg.dtsi"
12 compatible = "raspberrypi,model-zero-w", "brcm,bcm2835";
22 stdout-path = "serial1:115200n8";
26 led-act {
27 gpios = <&gpio 47 GPIO_ACTIVE_LOW>;
31 wifi_pwrseq: wifi-pwrseq {
32 compatible = "mmc-pwrseq-simple";
[all …]
Dbcm2835-rpi-b-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9514.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,model-b-plus", "brcm,bcm2835";
18 led-act {
19 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
22 led-pwr {
24 gpios = <&gpio 35 GPIO_ACTIVE_HIGH>;
[all …]
Dbcm2835-rpi-a-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-usb-host.dtsi"
8 compatible = "raspberrypi,model-a-plus", "brcm,bcm2835";
17 led-act {
18 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
21 led-pwr {
23 gpios = <&gpio 35 GPIO_ACTIVE_HIGH>;
24 default-state = "keep";
[all …]
Dbcm2837-rpi-3-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2836-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9514.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,3-model-b", "brcm,bcm2837";
14 stdout-path = "serial1:115200n8";
23 led-act {
24 gpios = <&expgpio 2 GPIO_ACTIVE_HIGH>;
28 wifi_pwrseq: wifi-pwrseq {
[all …]
Dbcm2837-rpi-3-a-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2836-rpi.dtsi"
5 #include "bcm283x-rpi-usb-host.dtsi"
8 compatible = "raspberrypi,3-model-a-plus", "brcm,bcm2837";
13 stdout-path = "serial1:115200n8";
22 led-act {
23 gpios = <&gpio 29 GPIO_ACTIVE_HIGH>;
26 led-pwr {
28 gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
[all …]
Dbcm2835-rpi-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9512.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,model-b", "brcm,bcm2835";
18 led-act {
19 gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
26 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
31 * "FOO" = GPIO line named "FOO" on the schematic
[all …]
Dbcm2835-rpi-zero.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
8 #include "bcm2835-rpi.dtsi"
9 #include "bcm283x-rpi-usb-otg.dtsi"
12 compatible = "raspberrypi,model-zero", "brcm,bcm2835";
21 led-act {
22 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
33 * "FOO" = GPIO line named "FOO" on the schematic
34 * "FOO_N" = GPIO line named "FOO" on schematic, active low
36 gpio-line-names = "ID_SDA",
[all …]
Dbcm2835-rpi-b-rev2.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9512.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,model-b-rev2", "brcm,bcm2835";
18 led-act {
19 gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
26 * Taken from Raspberry-Pi-Rev-2.0-Model-AB-Schematics.pdf
31 * "FOO" = GPIO line named "FOO" on the schematic
[all …]
Dbcm2835-rpi-a.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-usb-host.dtsi"
8 compatible = "raspberrypi,model-a", "brcm,bcm2835";
17 led-act {
18 gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
25 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
30 * "FOO" = GPIO line named "FOO" on the schematic
31 * "FOO_N" = GPIO line named "FOO" on schematic, active low
[all …]
Dbcm2711-rpi-4-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-usb-peripheral.dtsi"
7 #include <dt-bindings/reset/raspberrypi,firmware-reset.h>
10 compatible = "raspberrypi,4-model-b", "brcm,bcm2711";
15 stdout-path = "serial1:115200n8";
31 led-act {
32 gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
35 led-pwr {
[all …]
/kernel/linux/linux-4.19/arch/arm/boot/dts/
Dbcm2835-rpi-a-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-usb-host.dtsi"
8 compatible = "raspberrypi,model-a-plus", "brcm,bcm2835";
13 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
18 gpios = <&gpio 35 GPIO_ACTIVE_HIGH>;
19 default-state = "keep";
20 linux,default-trigger = "default-on";
31 * "FOO" = GPIO line named "FOO" on the schematic
[all …]
Dbcm2835-rpi-b-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9514.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,model-b-plus", "brcm,bcm2835";
14 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
19 gpios = <&gpio 35 GPIO_ACTIVE_HIGH>;
20 default-state = "keep";
21 linux,default-trigger = "default-on";
[all …]
Dbcm2835-rpi-zero-w.dts8 * http://www.opensource.org/licenses/gpl-license.html
12 /dts-v1/;
14 #include "bcm2835-rpi.dtsi"
15 #include "bcm283x-rpi-usb-otg.dtsi"
18 compatible = "raspberrypi,model-zero-w", "brcm,bcm2835";
23 stdout-path = "serial1:115200n8";
28 gpios = <&gpio 47 GPIO_ACTIVE_LOW>;
32 wifi_pwrseq: wifi-pwrseq {
33 compatible = "mmc-pwrseq-simple";
34 pinctrl-names = "default";
[all …]
Dbcm2835-rpi-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9512.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,model-b", "brcm,bcm2835";
14 gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
21 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
26 * "FOO" = GPIO line named "FOO" on the schematic
27 * "FOO_N" = GPIO line named "FOO" on schematic, active low
[all …]
Dbcm2835-rpi-b-rev2.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-smsc9512.dtsi"
6 #include "bcm283x-rpi-usb-host.dtsi"
9 compatible = "raspberrypi,model-b-rev2", "brcm,bcm2835";
14 gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
21 * Taken from Raspberry-Pi-Rev-2.0-Model-AB-Schematics.pdf
26 * "FOO" = GPIO line named "FOO" on the schematic
27 * "FOO_N" = GPIO line named "FOO" on schematic, active low
[all …]
Dbcm2835-rpi-a.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2835-rpi.dtsi"
5 #include "bcm283x-rpi-usb-host.dtsi"
8 compatible = "raspberrypi,model-a", "brcm,bcm2835";
13 gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
20 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
25 * "FOO" = GPIO line named "FOO" on the schematic
26 * "FOO_N" = GPIO line named "FOO" on schematic, active low
28 gpio-line-names = "SDA0",
[all …]
Dbcm2835-rpi-zero.dts8 * http://www.opensource.org/licenses/gpl-license.html
12 /dts-v1/;
14 #include "bcm2835-rpi.dtsi"
15 #include "bcm283x-rpi-usb-otg.dtsi"
18 compatible = "raspberrypi,model-zero", "brcm,bcm2835";
23 gpios = <&gpio 47 GPIO_ACTIVE_HIGH>;
34 * "FOO" = GPIO line named "FOO" on the schematic
35 * "FOO_N" = GPIO line named "FOO" on schematic, active low
37 gpio-line-names = "SDA0",
94 pinctrl-0 = <&gpioout &alt0 &i2s_alt0>;
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/clock/
Dmaxim,max9485.txt5 - MAX9485_MCLKOUT: A gated, buffered output of the input clock of 27 MHz
6 - MAX9485_CLKOUT: A PLL that can be configured to 16 different discrete
8 - MAX9485_CLKOUT[1,2]: Two gated outputs for MAX9485_CLKOUT
14 - compatible: "maxim,max9485"
15 - clocks: Input clock, must provice 27.000 MHz
16 - clock-names: Must be set to "xclk"
17 - #clock-cells: From common clock binding; shall be set to 1
20 - reset-gpios: GPIO descriptor connected to the #RESET input pin
21 - vdd-supply: A regulator node for Vdd
22 - clock-output-names: Name of output clocks, as defined in common clock
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/
Dmaxim,max9485.txt5 - MAX9485_MCLKOUT: A gated, buffered output of the input clock of 27 MHz
6 - MAX9485_CLKOUT: A PLL that can be configured to 16 different discrete
8 - MAX9485_CLKOUT[1,2]: Two gated outputs for MAX9485_CLKOUT
14 - compatible: "maxim,max9485"
15 - clocks: Input clock, must provice 27.000 MHz
16 - clock-names: Must be set to "xclk"
17 - #clock-cells: From common clock binding; shall be set to 1
20 - reset-gpios: GPIO descriptor connected to the #RESET input pin
21 - vdd-supply: A regulator node for Vdd
22 - clock-output-names: Name of output clocks, as defined in common clock
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpio/
Dgpio.txt4 1) gpios property
5 -----------------
7 Nodes that makes use of GPIOs should specify them using one or more
8 properties, each containing a 'gpio-list':
10 gpio-list ::= <single-gpio> [gpio-list]
11 single-gpio ::= <gpio-phandle> <gpio-specifier>
12 gpio-phandle : phandle to gpio controller node
13 gpio-specifier : Array of #gpio-cells specifying specific gpio
16 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
17 of this GPIO for the device. While a non-existent <name> is considered valid
[all …]

123