From: "Andreas Färber" <afaerber@suse.de>
To: linux-realtek-soc@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
"James Tai" <james.tai@realtek.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH v2 5/9] arm64: dts: realtek: rtd16xx: Carve out boot ROM from memory
Date: Mon, 2 Dec 2019 11:29:06 +0100 [thread overview]
Message-ID: <20191202102910.26916-6-afaerber@suse.de> (raw)
In-Reply-To: <20191202102910.26916-1-afaerber@suse.de>
Update Mjolnir /memory node to exclude 0..0x2dfff from reg entry.
Add this region to /soc ranges instead.
Suggested-by: Rob Herring <robh@kernel.org>
Cc: James Tai <james.tai@realtek.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
TODO: Add Fixes header once RTD1619 has a stable -rc1 based commit hash.
To be followed up by patch unshadowing more RAM from /soc 0x98000000..0xffffffff,
once we know the higher RAM windows.
v2: New
arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts | 5 +++--
arch/arm64/boot/dts/realtek/rtd16xx.dtsi | 4 +++-
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts b/arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts
index 44dd67e04335..90ed6681468f 100644
--- a/arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts
+++ b/arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts
@@ -1,6 +1,7 @@
// SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
/*
* Copyright (c) 2019 Realtek Semiconductor Corp.
+ * Copyright (c) 2019 Andreas Färber
*/
/dts-v1/;
@@ -11,9 +12,9 @@
compatible = "realtek,mjolnir", "realtek,rtd1619";
model = "Realtek Mjolnir EVB";
- memory@0 {
+ memory@2e000 {
device_type = "memory";
- reg = <0x0 0x80000000>;
+ reg = <0x2e000 0x7ffd2000>; /* boot ROM to 2 GiB */
};
chosen {
diff --git a/arch/arm64/boot/dts/realtek/rtd16xx.dtsi b/arch/arm64/boot/dts/realtek/rtd16xx.dtsi
index c7bbf2c7bb7c..69cc0d941c8d 100644
--- a/arch/arm64/boot/dts/realtek/rtd16xx.dtsi
+++ b/arch/arm64/boot/dts/realtek/rtd16xx.dtsi
@@ -3,6 +3,7 @@
* Realtek RTD16xx SoC family
*
* Copyright (c) 2019 Realtek Semiconductor Corp.
+ * Copyright (c) 2019 Andreas Färber
*/
#include <dt-bindings/interrupt-controller/arm-gic.h>
@@ -107,7 +108,8 @@
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
- ranges = <0x98000000 0x98000000 0x68000000>;
+ ranges = <0x00000000 0x00000000 0x0002e000>, /* boot ROM */
+ <0x98000000 0x98000000 0x68000000>;
rbus: bus@98000000 {
compatible = "simple-bus";
--
2.16.4
next prev parent reply other threads:[~2019-12-02 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 10:29 [PATCH v2 0/9] arm64: dts: realtek: Initial RTD1395 and BPi-M4 / Lion Skin support Andreas Färber
2019-12-02 10:29 ` [PATCH v2 1/9] arm64: dts: realtek: rtd129x: Fix GIC CPU masks for RTD1293 Andreas Färber
2019-12-02 10:29 ` [PATCH v2 2/9] arm64: dts: realtek: rtd129x: Use reserved-memory for RPC regions Andreas Färber
2019-12-02 10:29 ` [PATCH v2 3/9] arm64: dts: realtek: rtd129x: Introduce r-bus Andreas Färber
2019-12-02 10:29 ` [PATCH v2 4/9] arm64: dts: realtek: rtd129x: Carve out boot ROM from memory Andreas Färber
2019-12-02 10:29 ` Andreas Färber [this message]
2019-12-02 10:29 ` [PATCH v2 6/9] dt-bindings: arm: realtek: Add RTD1395 and Banana Pi BPI-M4 Andreas Färber
2019-12-02 10:29 ` [PATCH v2 7/9] arm64: dts: realtek: Add RTD1395 and BPi-M4 Andreas Färber
2019-12-02 10:29 ` [PATCH v2 8/9] dt-bindings: arm: realtek: Add Realtek Lion Skin EVB Andreas Färber
2019-12-13 22:29 ` Rob Herring
2019-12-02 10:29 ` [PATCH v2 9/9] arm64: dts: realtek: rtd1395: " Andreas Färber
2019-12-28 14:08 ` [PATCH v2 0/9] arm64: dts: realtek: Initial RTD1395 and BPi-M4 / Lion Skin support Andreas Färber
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=20191202102910.26916-6-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=james.tai@realtek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).