blob: 8d950522e7fa4220f0d018636650cfb104a2c272 [file] [log] [blame]
Kyle Swenson8d8f6542021-03-15 11:02:55 -06001OMAP GPIO controller bindings
2
3Required properties:
4- compatible:
5 - "ti,omap2-gpio" for OMAP2 controllers
6 - "ti,omap3-gpio" for OMAP3 controllers
7 - "ti,omap4-gpio" for OMAP4 controllers
8- gpio-controller : Marks the device node as a GPIO controller.
9- #gpio-cells : Should be two.
10 - first cell is the pin number
11 - second cell is used to specify optional parameters (unused)
12- interrupt-controller: Mark the device node as an interrupt controller.
13- #interrupt-cells : Should be 2.
14 The first cell is the GPIO number.
15 The second cell is used to specify flags:
16 bits[3:0] trigger type and level flags:
17 1 = low-to-high edge triggered.
18 2 = high-to-low edge triggered.
19 4 = active high level-sensitive.
20 8 = active low level-sensitive.
21
22OMAP specific properties:
23- ti,hwmods: Name of the hwmod associated to the GPIO:
24 "gpio<X>", <X> being the 1-based instance number
25 from the HW spec.
26- ti,gpio-always-on: Indicates if a GPIO bank is always powered and
27 so will never lose its logic state.
28
29
30Example:
31
32gpio4: gpio4 {
33 compatible = "ti,omap4-gpio";
34 ti,hwmods = "gpio4";
35 gpio-controller;
36 #gpio-cells = <2>;
37 interrupt-controller;
38 #interrupt-cells = <2>;
39};