Lines Matching refs:gpio
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
19 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
36 gpio-controller
37 #gpio-cells = <2>;
40 gpio-controller
41 #gpio-cells = <1>;
51 Note that gpio-specifier length is controller dependent. In the
52 above example, &gpio1 uses 2 cells to specify a gpio, while &gpio2
55 gpio-specifier may encode: bank, pin position inside the bank,
63 include/dt-bindings/gpio/gpio.h whenever possible:
71 GPIO_ACTIVE_HIGH is 0, so in this example gpio-specifier is "18 0" and encodes
72 GPIO pin number, and GPIO flags as accepted by the "qe_pio_e" gpio-controller.
86 A gpio-specifier should contain a flag indicating the GPIO polarity; active-
90 The gpio-specifier's polarity flag should represent the physical level at the
94 the GPIO controller and the device, then the gpio-specifier will represent the
112 In particular, the polarity cannot be derived from the gpio-specifier, since
120 in the binding. The gpio-specifier should represent the polarity of the signal
127 2) gpio-controller nodes
130 Every GPIO controller node must contain both an empty "gpio-controller"
131 property, and a #gpio-cells integer property, which indicates the number of
132 cells in a gpio-specifier.
150 gpio-controller@00000000 {
153 gpio-controller;
154 #gpio-cells = <2>;
160 gpio-controller's driver probe function.
164 - gpio-hog: A property specifying that this child node represent a GPIO hog.
181 Example of two SOC GPIO banks defined as gpio-controller nodes:
183 qe_pio_a: gpio-controller@1400 {
186 gpio-controller;
187 #gpio-cells = <2>;
190 gpio-hog;
193 line-name = "foo-bar-gpio";
197 qe_pio_e: gpio-controller@1460 {
200 gpio-controller;
201 #gpio-cells = <2>;
204 2.1) gpio- and pin-controller interaction
212 controllers. The gpio-ranges property described below represents this, and
215 gpio-range-list ::= <single-gpio-range> [gpio-range-list]
216 single-gpio-range ::= <numeric-gpio-range> | <named-gpio-range>
217 numeric-gpio-range ::=
218 <pinctrl-phandle> <gpio-base> <pinctrl-base> <count>
219 named-gpio-range ::= <pinctrl-phandle> <gpio-base> '<0 0>'
221 gpio-base : Base GPIO ID in the GPIO controller
228 In case named gpio ranges are used (ranges with both <pinctrl-base> and
229 <count> set to 0), the property gpio-ranges-group-names contains one string
230 for every single-gpio-range in gpio-ranges:
242 were referenced by any gpio-ranges property to contain a property named
243 #gpio-range-cells with value <3>. This requirement is now deprecated.
250 qe_pio_e: gpio-controller@1460 {
251 #gpio-cells = <2>;
254 gpio-controller;
255 gpio-ranges = <&pinctrl1 0 20 10>, <&pinctrl2 10 50 20>;
264 gpio_pio_i: gpio-controller@14B0 {
265 #gpio-cells = <2>;
268 gpio-controller;
269 gpio-ranges = <&pinctrl1 0 20 10>,
273 gpio-ranges-group-names = "",