summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTony Lindgren <tony@atomide.com>2021-03-10 14:04:30 +0200
committerTony Lindgren <tony@atomide.com>2021-03-10 14:04:30 +0200
commite55cc3f0404c6bb22ca843a6d16fae2ca193ca09 (patch)
tree686688f7a5946a5ea663c360ff5f6a352ba99485
parent932ddde183185b33c92c5b7810cbdbb792cfcafd (diff)
downloadlinux-e55cc3f0404c6bb22ca843a6d16fae2ca193ca09.tar.bz2
ARM: dts: Configure interconnect target module for omap4 mpu
We can now probe devices with device tree only configuration using ti-sysc interconnect target module driver. Signed-off-by: Tony Lindgren <tony@atomide.com>
-rw-r--r--arch/arm/boot/dts/omap4.dtsi28
1 files changed, 15 insertions, 13 deletions
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 675d29748480..5fe4dcaa24c5 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -91,19 +91,6 @@
};
/*
- * The soc node represents the soc top level view. It is used for IPs
- * that are not memory mapped in the MPU view or for the MPU itself.
- */
- soc {
- compatible = "ti,omap-infra";
- mpu {
- compatible = "ti,omap4-mpu";
- ti,hwmods = "mpu";
- sram = <&ocmcram>;
- };
- };
-
- /*
* XXX: Use a flat representation of the OMAP4 interconnect.
* The real OMAP interconnect network is quite complex.
* Since it will not bring real advantage to represent that in DT for
@@ -131,6 +118,21 @@
l4_per: interconnect@48000000 {
};
+ target-module@48210000 {
+ compatible = "ti,sysc-omap4-simple", "ti,sysc";
+ power-domains = <&prm_mpu>;
+ clocks = <&mpuss_clkctrl OMAP4_MPU_CLKCTRL 0>;
+ clock-names = "fck";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0 0x48210000 0x1f0000>;
+
+ mpu {
+ compatible = "ti,omap4-mpu";
+ sram = <&ocmcram>;
+ };
+ };
+
l4_abe: interconnect@40100000 {
};