On Fri, Apr 11, 2014 at 11:31:49PM +0530, Abhilash Kesavan wrote: > On the Exynos5420 non-secure SYSRAM is used for secondary CPU bring-up, > so add a mapping for it. > > Signed-off-by: Thomas Abraham <[email protected]> > Signed-off-by: Abhilash Kesavan <[email protected]> > --- > arch/arm/mach-exynos/exynos.c | 11 +++++++++++ > arch/arm/mach-exynos/include/mach/map.h | 1 + > 2 files changed, 12 insertions(+) > > diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c > index b32a907..b1cf9d5 100644 > --- a/arch/arm/mach-exynos/exynos.c > +++ b/arch/arm/mach-exynos/exynos.c > @@ -159,6 +159,15 @@ static struct map_desc exynos5250_iodesc[] __initdata = { > }, > }; > > +static struct map_desc exynos5420_iodesc[] __initdata = { > + { > + .virtual = (unsigned long)S5P_VA_SYSRAM_NS, > + .pfn = __phys_to_pfn(EXYNOS5420_PA_SYSRAM_NS), > + .length = SZ_4K, > + .type = MT_DEVICE, > + }, > +}; > +
Regarding Arnd's NAK in http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/246936.html, this looks like another instance of the same thing. Arnd, what was your preferred solution? Should this be described in DT? Cheers ---Dave -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
