All of lore.kernel.org
 help / color / mirror / Atom feed
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 07/11] ARM: dts: Move omap5 l3-noc to a separate node
Date: Mon,  8 Mar 2021 17:11:39 +0200	[thread overview]
Message-ID: <20210308151143.27793-8-tony@atomide.com> (raw)
In-Reply-To: <20210308151143.27793-1-tony@atomide.com>

In preparation for probing l3 with simple-pm-bus and genpd, we must move
l3 noc to a separate node. This is to prevent omap_l3_noc.c driver from
claiming the whole l3 instance before simple-pm-bus has a chance to probe.

Signed-off-by: Tony Lindgren <tony@atomide.com>
---
 arch/arm/boot/dts/omap5.dtsi | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -142,17 +142,21 @@ wakeupgen: interrupt-controller@48281000 {
 	 * hierarchy.
 	 */
 	ocp {
-		compatible = "ti,omap5-l3-noc", "simple-bus";
+		compatible = "simple-bus";
 		#address-cells = <1>;
 		#size-cells = <1>;
 		ranges = <0 0 0 0xc0000000>;
 		dma-ranges = <0x80000000 0x0 0x80000000 0x80000000>;
 		ti,hwmods = "l3_main_1", "l3_main_2", "l3_main_3";
-		reg = <0 0x44000000 0 0x2000>,
-		      <0 0x44800000 0 0x3000>,
-		      <0 0x45000000 0 0x4000>;
-		interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>,
-			     <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;
+
+		l3-noc@44000000 {
+			compatible = "ti,omap5-l3-noc";
+			reg = <0x44000000 0x2000>,
+			      <0x44800000 0x3000>,
+			      <0x45000000 0x4000>;
+			interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>,
+				     <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>;
+		};
 
 		l4_wkup: interconnect@4ae00000 {
 		};
-- 
2.30.1

  parent reply	other threads:[~2021-03-08 15:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 15:11 [PATCH 00/11] Update omap5 dts files to probe with genpd Tony Lindgren
2021-03-08 15:11 ` [PATCH 01/11] ARM: dts: Configure interconnect target module for omap5 dmm Tony Lindgren
2021-03-08 15:11 ` [PATCH 02/11] ARM: dts: Configure interconnect target module for omap5 emif Tony Lindgren
2021-03-08 15:11 ` [PATCH 03/11] ARM: dts: Configure interconnect target module for omap5 mpu Tony Lindgren
2021-03-08 15:11 ` [PATCH 04/11] ARM: dts: Configure interconnect target module for omap5 gpmc Tony Lindgren
2021-03-09  6:58   ` kernel test robot
2021-03-09  6:59     ` kernel test robot
2021-03-09  9:59     ` Tony Lindgren
2021-03-09  9:59       ` Tony Lindgren
2021-03-08 15:11 ` [PATCH 05/11] ARM: dts: Configure interconnect target module for omap5 sata Tony Lindgren
2021-03-08 15:11 ` [PATCH 06/11] ARM: dts: Move omap5 mmio-sram out of l3 interconnect Tony Lindgren
2021-03-08 15:11 ` Tony Lindgren [this message]
2021-03-08 15:11 ` [PATCH 08/11] ARM: dts: Configure simple-pm-bus for omap5 l4_wkup Tony Lindgren
2021-03-08 15:11 ` [PATCH 09/11] ARM: dts: Configure simple-pm-bus for omap5 l4_per Tony Lindgren
2021-03-08 15:11 ` [PATCH 10/11] ARM: dts: Configure simple-pm-bus for omap5 l4_cfg Tony Lindgren
2021-03-08 15:11 ` [PATCH 11/11] ARM: dts: Configure simple-pm-bus for omap5 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=20210308151143.27793-8-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.