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 06/11] ARM: dts: Move omap5 mmio-sram out of l3 interconnect
Date: Mon,  8 Mar 2021 17:11:38 +0200	[thread overview]
Message-ID: <20210308151143.27793-7-tony@atomide.com> (raw)
In-Reply-To: <20210308151143.27793-1-tony@atomide.com>

We need mmio-sram early for omap4_sram_init() for IO barrier init, and
will be moving l3 interconnect to probe with simple-pm-bus that probes
at module_init() time. So let's move mmio-sram out of l3 to prepare for
that.

Otherwise we will get the following after probing the interconnects with
simple-pm-bus:

omap4_sram_init:Unable to get sram pool needed to handle errata I688

Signed-off-by: Tony Lindgren <tony@atomide.com>
---
 arch/arm/boot/dts/omap5.dtsi | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 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
@@ -106,6 +106,15 @@ pmu {
 			     <GIC_SPI 132 IRQ_TYPE_LEVEL_HIGH>;
 	};
 
+	/*
+	 * Needed early by omap4_sram_init() for barrier, do not move to l3
+	 * interconnect as simple-pm-bus probes at module_init() time.
+	 */
+	ocmcram: sram@40300000 {
+		compatible = "mmio-sram";
+		reg = <0 0x40300000 0 0x20000>; /* 128k */
+	};
+
 	gic: interrupt-controller@48211000 {
 		compatible = "arm,cortex-a15-gic";
 		interrupt-controller;
@@ -172,11 +181,6 @@ mpu {
 		l4_abe: interconnect@40100000 {
 		};
 
-		ocmcram: sram@40300000 {
-			compatible = "mmio-sram";
-			reg = <0x40300000 0x20000>; /* 128k */
-		};
-
 		target-module@50000000 {
 			compatible = "ti,sysc-omap2", "ti,sysc";
 			reg = <0x50000000 4>,
-- 
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 ` Tony Lindgren [this message]
2021-03-08 15:11 ` [PATCH 07/11] ARM: dts: Move omap5 l3-noc to a separate node Tony Lindgren
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-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 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.