From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>, devicetree@vger.kernel.org
Subject: [PATCH 06/12] ARM: dts: Configure interconnect target module for omap4 mpu
Date: Mon, 8 Mar 2021 15:39:04 +0200 [thread overview]
Message-ID: <20210308133910.12454-7-tony@atomide.com> (raw)
In-Reply-To: <20210308133910.12454-1-tony@atomide.com>
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>
---
arch/arm/boot/dts/omap4.dtsi | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -90,19 +90,6 @@ wakeupgen: interrupt-controller@48281000 {
interrupt-parent = <&gic>;
};
- /*
- * 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.
@@ -131,6 +118,21 @@ l4_cfg: interconnect@4a000000 {
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 {
};
--
2.30.1
next prev parent reply other threads:[~2021-03-08 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:38 [PATCH 00/12] Update omap4 devicetree files to probe with genpd Tony Lindgren
2021-03-08 13:38 ` [PATCH 01/12] ARM: dts: Configure power-domain for omap4 gfx Tony Lindgren
2021-03-08 13:39 ` [PATCH 02/12] ARM: dts: Configure power-domain for omap4 dts iss Tony Lindgren
2021-03-08 13:39 ` [PATCH 03/12] ARM: dts: Configure interconnect target module for omap4 dmm Tony Lindgren
2021-03-08 13:39 ` [PATCH 04/12] ARM: dts: Configure interconnect target module for omap4 emif Tony Lindgren
2021-03-08 13:39 ` [PATCH 05/12] ARM: dts: Configure interconnect target module for omap4 debugss Tony Lindgren
2021-03-08 13:39 ` Tony Lindgren [this message]
2021-03-08 13:39 ` [PATCH 07/12] ARM: dts: Move omap4 mmio-sram out of l3 interconnect Tony Lindgren
2021-03-08 13:39 ` [PATCH 08/12] ARM: dts: Move omap4 l3-noc to a separate node Tony Lindgren
2021-03-08 13:39 ` [PATCH 09/12] ARM: dts: Configure simple-pm-bus for omap4 l4_wkup Tony Lindgren
2021-03-08 13:39 ` [PATCH 10/12] ARM: dts: Configure simple-pm-bus for omap4 l4_per Tony Lindgren
2021-03-08 13:39 ` [PATCH 11/12] ARM: dts: Configure simple-pm-bus for omap4 l4_cfg Tony Lindgren
2021-03-08 13:39 ` [PATCH 12/12] ARM: dts: Prepare for simple-pm-bus for omap4 l3 Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210308133910.12454-7-tony@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).