Lines Matching +full:gpio +full:- +full:controller
1 NVIDIA Tegra186 GPIO controllers
3 Tegra186 contains two GPIO controllers; a main controller and an "AON"
4 controller. This binding document applies to both controllers. The register
9 The Tegra186 GPIO controller allows software to set the IO direction of, and
10 read/write the value of, numerous GPIO signals. Routing of GPIO signals to
11 package balls is under the control of a separate pin controller HW block. Two
14 a) Security registers, which allow configuration of allowed access to the GPIO
17 varies between the different GPIO controllers.
20 that wishes to configure access to the GPIO registers needs access to these
21 registers to do so. Code which simply wishes to read or write GPIO data does not
24 b) GPIO registers, which allow manipulation of the GPIO signals. In some GPIO
27 documentation for rationale. Any particular GPIO client is expected to access
31 implemented by the SoC. Each GPIO is assigned to a port, and a port may control
32 a number of GPIOs. Thus, each GPIO is named according to an alphabetical port
33 name and an integer GPIO name within the port. For example, GPIO_PA0, GPIO_PN6,
36 The number of ports implemented by each GPIO controller varies. The number of
37 implemented GPIOs within each port varies. GPIO registers within a controller
40 The mapping from port name to the GPIO controller that implements that port, and
41 the mapping from port name to register offset within a controller, are both
42 extremely non-linear. The header file <dt-bindings/gpio/tegra186-gpio.h>
43 describes the port-level mapping. In that file, the naming convention for ports
45 sorted within a particular controller. Drivers need to map between the DT GPIO
48 Each GPIO controller can generate a number of interrupt signals. Each signal
50 number of interrupt signals generated by a controller varies as a rough function
52 both the overall controller HW module and the sets-of-ports as "controllers".
54 Each GPIO controller in fact generates multiple interrupts signals for each set
55 of ports. Each GPIO may be configured to feed into a specific one of the
56 interrupt signals generated by a set-of-ports. The intent is for each generated
59 per-port-set signals is reported via a separate register. Thus, a driver needs
66 - compatible
69 - "nvidia,tegra186-gpio".
70 - "nvidia,tegra186-gpio-aon".
71 - reg-names
75 - "gpio": Mandatory. GPIO control registers. This may cover either:
77 b) All physical aliases that exist in the controller. This is
80 - "security": Optional. Security configuration registers.
82 using this reg-names property to do so.
83 - reg
85 Must contain one entry per entry in the reg-names property, in a matching
87 - interrupts
92 - "nvidia,tegra186-gpio": 6 entries.
93 - "nvidia,tegra186-gpio-aon": 1 entry.
94 - gpio-controller
96 Marks the device node as a GPIO controller/provider.
97 - #gpio-cells
98 Single-cell integer.
100 Indicates how many cells are used in a consumer's GPIO specifier.
102 - The first cell is the pin number.
103 See <dt-bindings/gpio/tegra186-gpio.h>.
104 - The second cell contains flags:
105 - Bit 0 specifies polarity
106 - 0: Active-high (normal).
107 - 1: Active-low (inverted).
108 - interrupt-controller
110 Marks the device node as an interrupt controller/provider.
111 - #interrupt-cells
112 Single-cell integer.
116 - The first cell is the GPIO number.
117 See <dt-bindings/gpio/tegra186-gpio.h>.
118 - The second cell is contains flags:
119 - Bits [3:0] indicate trigger type and level:
120 - 1: Low-to-high edge triggered.
121 - 2: High-to-low edge triggered.
122 - 4: Active high level-sensitive.
123 - 8: Active low level-sensitive.
128 #include <dt-bindings/interrupt-controller/irq.h>
130 gpio@2200000 {
131 compatible = "nvidia,tegra186-gpio";
132 reg-names = "security", "gpio";
143 gpio-controller;
144 #gpio-cells = <2>;
145 interrupt-controller;
146 #interrupt-cells = <2>;
149 gpio@c2f0000 {
150 compatible = "nvidia,tegra186-gpio-aon";
151 reg-names = "security", "gpio";
157 gpio-controller;
158 #gpio-cells = <2>;
159 interrupt-controller;
160 #interrupt-cells = <2>;