From: Lukasz Luba <l.luba@partner.samsung.com>
To: linux-kernel@vger.kernel.org, lukasz.luba@polnum.com
Cc: b.zolnierkie@samsung.com, m.szyprowski@samsung.com,
s.nawrocki@samsung.com, Lukasz Luba <l.luba@partner.samsung.com>
Subject: [RFC 1/2] DT: ARM: exynos: change SRAM device node
Date: Fri, 4 Oct 2019 15:38:54 +0200 [thread overview]
Message-ID: <20191004133855.17474-2-l.luba@partner.samsung.com> (raw)
In-Reply-To: <20191004133855.17474-1-l.luba@partner.samsung.com>
Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
---
arch/arm/boot/dts/exynos54xx.dtsi | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/arch/arm/boot/dts/exynos54xx.dtsi b/arch/arm/boot/dts/exynos54xx.dtsi
index 0b27bebf9528..1e43ad9f2d89 100644
--- a/arch/arm/boot/dts/exynos54xx.dtsi
+++ b/arch/arm/boot/dts/exynos54xx.dtsi
@@ -47,21 +47,11 @@
soc: soc {
sysram@2020000 {
- compatible = "mmio-sram";
+ compatible = "direct-sram";
reg = <0x02020000 0x54000>;
#address-cells = <1>;
#size-cells = <1>;
ranges = <0 0x02020000 0x54000>;
-
- smp-sysram@0 {
- compatible = "samsung,exynos4210-sysram";
- reg = <0x0 0x1000>;
- };
-
- smp-sysram@53000 {
- compatible = "samsung,exynos4210-sysram-ns";
- reg = <0x53000 0x1000>;
- };
};
mct: mct@101c0000 {
--
2.17.1
next prev parent reply other threads:[~2019-10-04 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191004133905eucas1p1f002c9e76ceaef205b48e941707af726@eucas1p1.samsung.com>
2019-10-04 13:38 ` [RFC 0/2] SRAMFS a direct mapped SRAM pages into user space Lukasz Luba
[not found] ` <CGME20191004133905eucas1p18363c8c5f98cc5e7dfaa046d405808cf@eucas1p1.samsung.com>
2019-10-04 13:38 ` Lukasz Luba [this message]
[not found] ` <CGME20191004133906eucas1p11441753ba77a4f8568da5b265b27fa1c@eucas1p1.samsung.com>
2019-10-04 13:38 ` [RFC 2/2] dirvers & fs: add sram driver and sramfs Lukasz Luba
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=20191004133855.17474-2-l.luba@partner.samsung.com \
--to=l.luba@partner.samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@polnum.com \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@samsung.com \
/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).