device-tree-bindings/gpio/gpio.txt

4 1) gpios property
7 Nodes that makes use of GPIOs should specify them using one or more
16 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
18 for compatibility reasons (resolving to the "gpios" property), it is not allowed
22 cases should they contain more than one. If your device uses several GPIOs with
24 meaningful name. The only case where an array of GPIOs is accepted is when
25 several GPIOs serve the same function (e.g. a parallel data line).
27 The exact purpose of each gpios property must be documented in the device tree
43 	enable-gpios = <&gpio2 2>;
44 	data-gpios = <&gpio1 12 0>,
59 Example of a node using GPIOs:
62 		enable-gpios = <&qe_pio_e 18 GPIO_ACTIVE_HIGH>;
138 Some or all of the GPIOs provided by a GPIO controller may be routed to pins
142 It is useful to represent which GPIOs correspond to which pins on which pin
154 	count : The number of GPIOs/pins in this range
169 controller. The number of pins/GPIOs in the range is the number of pins in
189 Here, a single GPIO controller has GPIOs 0..9 routed to pin controller
190 pinctrl1's pins 20..29, and GPIOs 10..19 routed to pin controller pinctrl2's
224 - gpios:      Store the GPIO information (id, flags) for the GPIO to
250                         gpios = <6 GPIO_ACTIVE_LOW>;
256                         gpios = <7 GPIO_ACTIVE_LOW>;