Skip to contentSkip to conversation

ARM: dts: Add l4 abe interconnect hierarchy and ti-sysc data for omap5

PATCH New Tony Lindgren 1 participant 1 message Apr 8, 2019 Device tree bindings

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ARM: dts: Add l4 abe interconnect hierarchy and ti-sysc data for omap5

We can now add l4 abe interconnect hierarchy and ti-sysc data with ti-sysc driver supporting external optional clocks needed by mcpdm.

This data is generated based on platform data from a booted system and the interconnect acces protection registers for ranges. To avoid regressions, we initially validate the device tree provided data against the existing platform data on boot.

Note that mcpdm we now need to enable at module level only for devices that have the external pdmclk wired from the PMIC as the clock is needed for the module to be accessible.

Also note that abe seems to be the same as on omap4 except for domains and clocks and we may be able to combine the l4 abe data later on. But let's play it safe and just initially use what we have already defined in the platform data.

---
 arch/arm/boot/dts/omap5-board-common.dtsi |   8 +-
 arch/arm/boot/dts/omap5-l4-abe.dtsi       | 447 ++++++++++++++++++++++
 arch/arm/boot/dts/omap5.dtsi              | 115 +-----
 3 files changed, 458 insertions(+), 112 deletions(-)
 create mode 100644 arch/arm/boot/dts/omap5-l4-abe.dtsi
arch/arm/boot/dts/omap5-board-common.dtsi +5 -3
@@ -667,14 +667,16 @@
 	};
 };
 
-&mcpdm {
+&mcpdm_module {
+	/* Module on the SoC needs external clock from the PMIC */
 	pinctrl-names = "default";
 	pinctrl-0 = <&mcpdm_pins>;
+	status = "okay";
+};
 
+&mcpdm {
 	clocks = <&twl6040>;
 	clock-names = "pdmclk";
-
-	status = "okay";
 };
 
 &mcbsp1 {
arch/arm/boot/dts/omap5-l4-abe.dtsi new file +447 -0

447 lines not on this page · raw message

arch/arm/boot/dts/omap5.dtsi +6 -109

130 lines not on this page · raw message

Signature · 1 line
2.21.0