From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Chanwoo Choi'" <cw00.choi@samsung.com>
Cc: t.figa@samsung.com, linux@arm.linux.org.uk,
kyungmin.park@samsung.com, inki.dae@samsung.com,
sw0312.kim@samsung.com, hyunhee.kim@samsung.com,
yj44.cho@samsung.com, chanho61.park@samsung.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCHv5] ARM: EXYNOS: Support secondary CPU boot of Exynos4212
Date: Fri, 09 May 2014 11:14:49 +0900 [thread overview]
Message-ID: <034d01cf6b2c$748bdd50$5da397f0$@samsung.com> (raw)
In-Reply-To: <5369B88E.9030901@samsung.com>
Chanwoo Choi wrote:
>
> Dear Kukjin,
>
> Could you please pick this patch?
>
I've applied.
Thanks,
Kukjin
> Best Regards,
> Chanwoo Choi
>
> On 04/29/2014 10:37 AM, Chanwoo Choi wrote:
> > From: Kyungmin Park <kyungmin.park@samsung.com>
> >
> > This patch fix the offset of CPU boot address and change parameter of
> smc call
> > of SMC_CMD_CPU1BOOT command for Exynos4212.
> >
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> > Reviewed-by: Tomasz Figa <t.figa@samsung.com>
> > ---
> > Changes from v4:
> > - Post only this patch separated from following patchset[1]
> > [1] https://lkml.org/lkml/2014/4/24/873
> >
> > arch/arm/mach-exynos/firmware.c | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-exynos/firmware.c b/arch/arm/mach-
> exynos/firmware.c
> > index 932129e..aa01c42 100644
> > --- a/arch/arm/mach-exynos/firmware.c
> > +++ b/arch/arm/mach-exynos/firmware.c
> > @@ -18,6 +18,8 @@
> >
> > #include <mach/map.h>
> >
> > +#include <plat/cpu.h>
> > +
> > #include "smc.h"
> >
> > static int exynos_do_idle(void)
> > @@ -28,13 +30,24 @@ static int exynos_do_idle(void)
> >
> > static int exynos_cpu_boot(int cpu)
> > {
> > + /*
> > + * The second parameter of SMC_CMD_CPU1BOOT command means CPU id.
> > + * But, Exynos4212 has only one secondary CPU so second parameter
> > + * isn't used for informing secure firmware about CPU id.
> > + */
> > + if (soc_is_exynos4212())
> > + cpu = 0;
> > +
> > exynos_smc(SMC_CMD_CPU1BOOT, cpu, 0, 0);
> > return 0;
> > }
> >
> > static int exynos_set_cpu_boot_addr(int cpu, unsigned long boot_addr)
> > {
> > - void __iomem *boot_reg = S5P_VA_SYSRAM_NS + 0x1c + 4*cpu;
> > + void __iomem *boot_reg = S5P_VA_SYSRAM_NS + 0x1c;
> > +
> > + if (!soc_is_exynos4212())
> > + boot_reg += 4*cpu;
> >
> > __raw_writel(boot_addr, boot_reg);
> > return 0;
> >
next prev parent reply other threads:[~2014-05-09 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 1:37 [PATCHv5] ARM: EXYNOS: Support secondary CPU boot of Exynos4212 Chanwoo Choi
2014-05-07 4:37 ` Chanwoo Choi
2014-05-09 2:14 ` Kukjin Kim [this message]
2014-05-09 2:20 ` Chanwoo Choi
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='034d01cf6b2c$748bdd50$5da397f0$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=hyunhee.kim@samsung.com \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sw0312.kim@samsung.com \
--cc=t.figa@samsung.com \
--cc=yj44.cho@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