devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Palmer <daniel@0x0f.com>
To: soc@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de, robh@kernel.org,
	Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH v2 3/9] ARM: mstar: Add IMI SRAM region
Date: Tue, 28 Jul 2020 19:03:15 +0900	[thread overview]
Message-ID: <20200728100321.1691745-4-daniel@0x0f.com> (raw)
In-Reply-To: <20200728100321.1691745-1-daniel@0x0f.com>

All MStar v7 SoCs have an internal SRAM region that is between 64KB
(infinity2m) and 128KB(infinity3, mercury5).

The region is always at the same base address and is used for the
second stage loader (MStar IPL or u-boot SPL) and will be used for
the DDR self-refresh entry code within the kernel eventually.

This patch adds a 128KB region to the SoC and the minimum 64KB SRAM
region to the base dtsi. Families with more SRAM will override the
size in their family level dtsi.

Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
 arch/arm/boot/dts/mstar-v7.dtsi | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/mstar-v7.dtsi b/arch/arm/boot/dts/mstar-v7.dtsi
index 3b99bb435bb5..1941f88a69a5 100644
--- a/arch/arm/boot/dts/mstar-v7.dtsi
+++ b/arch/arm/boot/dts/mstar-v7.dtsi
@@ -45,7 +45,8 @@ soc: soc {
 		#address-cells = <1>;
 		#size-cells = <1>;
 		ranges = <0x16001000 0x16001000 0x00007000>,
-			 <0x1f000000 0x1f000000 0x00400000>;
+			 <0x1f000000 0x1f000000 0x00400000>,
+			 <0xa0000000 0xa0000000 0x20000>;
 
 		gic: interrupt-controller@16001000 {
 			compatible = "arm,cortex-a7-gic";
@@ -79,5 +80,10 @@ pm_uart: uart@221000 {
 				status = "disabled";
 			};
 		};
+
+		imi: sram@a0000000 {
+			compatible = "mmio-sram";
+			reg = <0xa0000000 0x10000>;
+		};
 	};
 };
-- 
2.27.0


  parent reply	other threads:[~2020-07-28 10:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 10:03 [PATCH v2 0/9] ARM: mstar: DT filling out Daniel Palmer
2020-07-28 10:03 ` [PATCH v2 1/9] dt-bindings: arm: mstar: Add binding details for mstar,pmsleep Daniel Palmer
2020-07-28 19:16   ` [PATCH v2 1/9] dt-bindings: arm: mstar: Add binding details for mstar, pmsleep Rob Herring
2020-07-28 19:18   ` [PATCH v2 1/9] dt-bindings: arm: mstar: Add binding details for mstar,pmsleep Rob Herring
2020-07-29  9:13     ` Daniel Palmer
2020-07-29 12:13       ` Arnd Bergmann
2020-07-29 12:34         ` Daniel Palmer
2020-07-29 14:17           ` Arnd Bergmann
2020-07-28 10:03 ` [PATCH v2 2/9] dt-bindings: arm: mstar: Move existing MStar binding descriptions Daniel Palmer
2020-07-28 10:03 ` Daniel Palmer [this message]
2020-07-28 10:03 ` [PATCH v2 4/9] ARM: mstar: Adjust IMI size of infinity Daniel Palmer
2020-07-28 10:03 ` [PATCH v2 5/9] ARM: mstar: Adjust IMI size for mercury5 Daniel Palmer
2020-07-28 10:03 ` [PATCH v2 6/9] ARM: mstar: Adjust IMI size for infinity3 Daniel Palmer
2020-07-28 10:03 ` [PATCH v2 7/9] ARM: mstar: Add PMU Daniel Palmer
2020-07-28 10:03 ` [PATCH v2 8/9] ARM: mstar: Add "pmsleep" node to base dtsi Daniel Palmer
2020-07-28 10:03 ` [PATCH v2 9/9] ARM: mstar: Add reboot support Daniel Palmer

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=20200728100321.1691745-4-daniel@0x0f.com \
    --to=daniel@0x0f.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=soc@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).