Home
last modified time | relevance | path

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

12

/Linux-v6.1/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
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
30 compatible = "acme,foo";
[all …]
/Linux-v6.1/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"
7 #include "bcm283x-rpi-wifi-bt.dtsi"
10 compatible = "raspberrypi,3-model-b-plus", "brcm,bcm2837";
15 stdout-path = "serial1:115200n8";
24 led-act {
25 gpios = <&gpio 29 GPIO_ACTIVE_HIGH>;
[all …]
Dbcm2837-rpi-zero-2-w.dts1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
8 #include "bcm2836-rpi.dtsi"
9 #include "bcm283x-rpi-usb-otg.dtsi"
10 #include "bcm283x-rpi-wifi-bt.dtsi"
13 compatible = "raspberrypi,model-zero-2-w", "brcm,bcm2837";
23 stdout-path = "serial1:115200n8";
27 led-act {
28 gpios = <&gpio 29 GPIO_ACTIVE_LOW>;
34 shutdown-gpios = <&gpio 42 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"
10 #include "bcm283x-rpi-wifi-bt.dtsi"
13 compatible = "raspberrypi,model-zero-w", "brcm,bcm2835";
23 stdout-path = "serial1:115200n8";
27 led-act {
28 gpios = <&gpio 47 GPIO_ACTIVE_LOW>;
34 shutdown-gpios = <&gpio 45 GPIO_ACTIVE_HIGH>;
[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"
7 #include "bcm283x-rpi-wifi-bt.dtsi"
10 compatible = "raspberrypi,3-model-b", "brcm,bcm2837";
15 stdout-path = "serial1:115200n8";
24 led-act {
25 gpios = <&expgpio 2 GPIO_ACTIVE_HIGH>;
[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-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-a-plus.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2836-rpi.dtsi"
5 #include "bcm283x-rpi-usb-host.dtsi"
6 #include "bcm283x-rpi-wifi-bt.dtsi"
9 compatible = "raspberrypi,3-model-a-plus", "brcm,bcm2837";
14 stdout-path = "serial1:115200n8";
23 led-act {
24 gpios = <&gpio 29 GPIO_ACTIVE_HIGH>;
27 led-pwr {
[all …]
Dbcm2711-rpi-cm4-io.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
3 #include "bcm2711-rpi-cm4.dtsi"
4 #include "bcm283x-rpi-usb-host.dtsi"
10 led-act {
11 gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
14 led-pwr {
16 gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
17 default-state = "keep";
18 linux,default-trigger = "default-on";
[all …]
Dbcm2711-rpi-4-b.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include "bcm2711-rpi.dtsi"
5 #include "bcm283x-rpi-usb-peripheral.dtsi"
6 #include "bcm283x-rpi-wifi-bt.dtsi"
9 compatible = "raspberrypi,4-model-b", "brcm,bcm2711";
14 stdout-path = "serial1:115200n8";
18 led-act {
19 gpios = <&gpio 42 GPIO_ACTIVE_HIGH>;
22 led-pwr {
[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
30 * "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>;
32 * "FOO" = GPIO line named "FOO" on the schematic
33 * "FOO_N" = GPIO line named "FOO" on schematic, active low
35 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
30 * "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
29 * "FOO" = GPIO line named "FOO" on the schematic
30 * "FOO_N" = GPIO line named "FOO" on schematic, active low
[all …]
Dbcm2837-rpi-cm3-io3.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
3 #include "bcm2837-rpi-cm3.dtsi"
4 #include "bcm283x-rpi-usb-host.dtsi"
7 compatible = "raspberrypi,3-compute-module", "brcm,bcm2837";
16 * "FOO" = GPIO line named "FOO" on the schematic
17 * "FOO_N" = GPIO line named "FOO" on schematic, active low
19 gpio-line-names = "GPIO0",
75 pinctrl-0 = <&gpioout &alt0>;
79 hpd-gpios = <&expgpio 1 GPIO_ACTIVE_LOW>;
[all …]
Dbcm2835-rpi-cm1-io1.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
3 #include "bcm2835-rpi-cm1.dtsi"
4 #include "bcm283x-rpi-usb-host.dtsi"
7 compatible = "raspberrypi,compute-module", "brcm,bcm2835";
16 * "FOO" = GPIO line named "FOO" on the schematic
17 * "FOO_N" = GPIO line named "FOO" on schematic, active low
19 gpio-line-names = "GPIO0",
76 pinctrl-0 = <&gpioout &alt0>;
80 hpd-gpios = <&gpio 46 GPIO_ACTIVE_LOW>;
[all …]
/Linux-v6.1/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 …]
/Linux-v6.1/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 …]
/Linux-v6.1/Documentation/driver-api/
Dpin-control.rst9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up/down, open drain,
17 Top-level interface
22 - A pin controller is a piece of hardware, usually a set of registers, that
28 - PINS are equal to pads, fingers, balls or whatever packaging input or
32 be sparse - i.e. there may be gaps in the space with numbers where no
75 .name = "foo",
98 See for example arch/arm/mach-ux500/Kconfig for an example.
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/display/panel/
Dsamsung,s6d16d0.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: panel-common.yaml#
21 reset-gpios: true
23 vdd1-supply:
27 - compatible
28 - reg
29 - vdd1-supply
[all …]
Dsony,acx424akp.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Linus Walleij <linus.walleij@linaro.org>
18 - $ref: panel-common.yaml#
23 - sony,acx424akp
24 - sony,acx424akm
26 reset-gpios: true
27 vddi-supply:
29 enforce-video-mode: true
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/iio/amplifiers/
Dadi,hmc425a.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: HMC425A 6-bit Digital Step Attenuator
10 - Michael Hennerich <michael.hennerich@analog.com>
14 HMC425A 0.5 dB LSB GaAs MMIC 6-BIT DIGITAL POSITIVE CONTROL ATTENUATOR, 2.2 - 8.0 GHz
15 https://www.analog.com/media/en/technical-documentation/data-sheets/hmc425A.pdf
20 - adi,hmc425a
22 vcc-supply: true
24 ctrl-gpios:
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/usb/
Dusb251xb.txt1 Microchip USB 2.0 Hi-Speed Hub Controller
4 Hi-Speed Controller.
7 - compatible : Should be "microchip,usb251xb" or one of the specific types:
11 - reg : I2C address on the selected bus (default is <0x2C>)
14 - reset-gpios : Should specify the gpio for hub reset
15 - vdd-supply : Should specify the phandle to the regulator supplying vdd
16 - skip-config : Skip Hub configuration, but only send the USB-Attach command
17 - vendor-id : Set USB Vendor ID of the hub (16 bit, default is 0x0424)
18 - product-id : Set USB Product ID of the hub (16 bit, default depends on type)
19 - device-id : Set USB Device ID of the hub (16 bit, default is 0x0bb3)
[all …]
/Linux-v6.1/drivers/gpio/
Dgpiolib-of.c1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright (c) 2007-2008 MontaVista Software, Inc.
24 #include "gpiolib-of.h"
27 * of_gpio_spi_cs_get_count() - special GPIO counting for SPI
33 * established "cs-gpios" for chip selects but instead rely on
34 * "gpios" for the chip select lines. If we detect this, we redirect
35 * the counting of "cs-gpios" to count "gpios" transparent to the
40 struct device_node *np = dev->of_node; in of_gpio_spi_cs_get_count()
48 !of_device_is_compatible(np, "ibm,ppc4xx-spi")) in of_gpio_spi_cs_get_count()
50 return of_gpio_named_count(np, "gpios"); in of_gpio_spi_cs_get_count()
[all …]

12