From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kukjin Kim Subject: RE: [PATCH 1/2] ARM: EXYNOS: Map SYSRAM through generic SRAM bindings Date: Fri, 02 May 2014 11:25:26 +0900 Message-ID: <045301cf65ad$c95badd0$5c130970$@samsung.com> References: <1398941085-10224-1-git-send-email-sachin.kamat@linaro.org> <11106990.1tS5A7pf5r@diego> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-reply-to: <11106990.1tS5A7pf5r@diego> Content-language: ko Sender: linux-samsung-soc-owner@vger.kernel.org To: =?ISO-8859-1?Q?'Heiko_St=FCbner'?= , 'Sachin Kamat' Cc: linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, arnd@arndb.de, t.figa@samsung.com, robh+dt@kernel.org, a.hajda@samsung.com List-Id: devicetree@vger.kernel.org Heiko St=FCbner wrote: >=20 > Hi Sachin, >=20 > Am Donnerstag, 1. Mai 2014, 16:14:44 schrieb Sachin Kamat: > > Instead of hardcoding the SYSRAM details for each SoC, > > pass this information through device tree (DT) and make > > the code SoC agnostic. Generic SRAM bindings are used > > for achieving this. > > > > Signed-off-by: Sachin Kamat > > Cc: Heiko Stuebner > > Cc: Arnd Bergmann >=20 > very cool :-). >=20 > I've found one little thing I do not understand, which I describe bel= ow. > Otherwise > Acked-by: Heiko Stuebner >=20 > > --- > > This patch is based on linux next (next-20140501) on top of > > my Kconfig consolidation patch > > http://comments.gmane.org/gmane.linux.kernel.samsung-soc/28642 > > > > Tested on 4210/4412 Origen, 5250/5420 Arndale and SMDK5420 boards. > > --- > > arch/arm/Kconfig | 1 + > > arch/arm/boot/dts/exynos4210-universal_c210.dts | 17 ++++++ > > arch/arm/boot/dts/exynos4210.dtsi | 18 +++++++ > > arch/arm/boot/dts/exynos4x12.dtsi | 18 +++++++ > > arch/arm/boot/dts/exynos5250.dtsi | 18 +++++++ > > arch/arm/boot/dts/exynos5420.dtsi | 18 +++++++ > > arch/arm/mach-exynos/common.h | 1 + > > arch/arm/mach-exynos/exynos.c | 64 > > ----------------------- arch/arm/mach-exynos/firmware.c | > > 5 +- > > arch/arm/mach-exynos/include/mach/map.h | 7 --- > > arch/arm/mach-exynos/platsmp.c | 39 +++++++++++= ++- > > 11 files changed, 133 insertions(+), 73 deletions(-) > > > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > > index a6aaaad19b1a..f66ea9453df9 100644 > > --- a/arch/arm/Kconfig > > +++ b/arch/arm/Kconfig > > @@ -855,6 +855,7 @@ config ARCH_EXYNOS > > select S5P_DEV_MFC > > select SAMSUNG_DMADEV > > select SPARSE_IRQ > > + select SRAM > > select USE_OF > > help > > Support for SAMSUNG's EXYNOS SoCs (EXYNOS4/5) > > diff --git a/arch/arm/boot/dts/exynos4210-universal_c210.dts > > b/arch/arm/boot/dts/exynos4210-universal_c210.dts index > > 63e34b24b04f..8d4de5c0d0c7 100644 > > --- a/arch/arm/boot/dts/exynos4210-universal_c210.dts > > +++ b/arch/arm/boot/dts/exynos4210-universal_c210.dts > > @@ -28,6 +28,23 @@ > > bootargs =3D "console=3DttySAC2,115200N8 root=3D/dev/mmcblk0p5 r= w > rootwait > > earlyprintk panic=3D5 maxcpus=3D1"; }; > > > > + sram@02020000 { > > + status =3D "disabled"; > > + }; > > + > > + sram@02025000 { > > + compatible =3D "mmio-sram"; > > + reg =3D <0x02025000 0x1000>; > > + #address-cells =3D <1>; > > + #size-cells =3D <1>; > > + ranges =3D <0 0x02025000 0x1000>; > > + > > + smp-sram@0 { > > + compatible =3D "samsung,exynos4210-sram"; > > + reg =3D <0x0 0x1000>; > > + }; > > + }; >=20 > exynos_smp_prepare_sram returns -ENODEV if it can't find > samsung,exynos4210-sram-ns, so are you sure your universal_c210 will = run > without it? I didn't dig to deep into this, so it can also simply be > something > I overlooked :-) >=20 Hi Andrzej and Tomasz, Can you please check above? - Kukjin