diff options
author | Lokesh Vutla <lokeshvutla@ti.com> | 2019-08-09 13:59:43 +0530 |
---|---|---|
committer | Tero Kristo <t-kristo@ti.com> | 2019-08-29 16:04:59 +0300 |
commit | 248f3eae99485bb0a860d66212374f7312b18b57 (patch) | |
tree | e4dd262575604e9ad546a19664d02c3d282e3354 /arch/arm64/boot/dts/amlogic/meson-g12b.dtsi | |
parent | bf146a1a7cd4855696859bd6cd3f470b96f1bea9 (diff) | |
download | linux-stable-248f3eae99485bb0a860d66212374f7312b18b57.tar.gz linux-stable-248f3eae99485bb0a860d66212374f7312b18b57.tar.bz2 linux-stable-248f3eae99485bb0a860d66212374f7312b18b57.zip |
arm64: dts: ti: k3-j721e: Add gpio nodes in main domain
There are 8 instances of gpio modules in main domain divided into 2 groups:
- Group1: gpio0, gpio2, gpio4, gpio6
- Group2: gpio1, gpio3, gpio5, gpio7
Groups are created to provide protection between two different processor
virtual worlds. There are x gpio lines coming out of each group. Each module
in a group has equal x gpio lines pinned out. There is a top level mux for
selecting the module instance for each pin coming out of group. Exactly
one module can be selected to control the corresponding pin. This muxing
can be controlled along the pad mux configuration registers.
Group1 pins out 128 lines(8 banks). Group 2 pins out 36 lines(2 banks).
Add DT nodes for each module instance in the main domain. Users should
make sure that correct gpio instance is selected in their pad configuration.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Keerthy <j-keerthy@ti.com>
Signed-off-by: Tero Kristo <t-kristo@ti.com>
Diffstat (limited to 'arch/arm64/boot/dts/amlogic/meson-g12b.dtsi')
0 files changed, 0 insertions, 0 deletions