forked from Qortal/Brooklyn
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
45 lines
1.4 KiB
45 lines
1.4 KiB
OMAP GPIO controller bindings |
|
|
|
Required properties: |
|
- compatible: |
|
- "ti,omap2-gpio" for OMAP2 controllers |
|
- "ti,omap3-gpio" for OMAP3 controllers |
|
- "ti,omap4-gpio" for OMAP4 controllers |
|
- reg : Physical base address of the controller and length of memory mapped |
|
region. |
|
- gpio-controller : Marks the device node as a GPIO controller. |
|
- #gpio-cells : Should be two. |
|
- first cell is the pin number |
|
- second cell is used to specify optional parameters (unused) |
|
- interrupt-controller: Mark the device node as an interrupt controller. |
|
- #interrupt-cells : Should be 2. |
|
The first cell is the GPIO number. |
|
The second cell is used to specify flags: |
|
bits[3:0] trigger type and level flags: |
|
1 = low-to-high edge triggered. |
|
2 = high-to-low edge triggered. |
|
4 = active high level-sensitive. |
|
8 = active low level-sensitive. |
|
- interrupts : The interrupt the controller is rising as output when an |
|
interrupt occures |
|
|
|
OMAP specific properties: |
|
- ti,hwmods: Name of the hwmod associated to the GPIO: |
|
"gpio<X>", <X> being the 1-based instance number |
|
from the HW spec. |
|
- ti,gpio-always-on: Indicates if a GPIO bank is always powered and |
|
so will never lose its logic state. |
|
|
|
|
|
Example: |
|
|
|
gpio0: gpio@44e07000 { |
|
compatible = "ti,omap4-gpio"; |
|
reg = <0x44e07000 0x1000>; |
|
ti,hwmods = "gpio1"; |
|
gpio-controller; |
|
#gpio-cells = <2>; |
|
interrupt-controller; |
|
#interrupt-cells = <2>; |
|
interrupts = <96>; |
|
};
|
|
|