From: Ian Campbell <ian.campbell@citrix.com>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [XEN/ARM PATCH v2 1/1] Add support for Exynos secure firmware
Date: Thu, 18 Sep 2014 20:06:02 +0100 [thread overview]
Message-ID: <1411067162.1920.31.camel@citrix.com> (raw)
In-Reply-To: <CANoR_OCm0d5un6uXpgoWpTA4dyW1CnazQvXOJdD3-Ypb2g-urg@mail.gmail.com>
On Thu, 2014-09-18 at 11:44 -0700, Suriyan Ramasami wrote:
> >> @@ -135,7 +168,7 @@ static int __init exynos5_smp_init(void)
> >> static int exynos_cpu_power_state(void __iomem *power, int cpu)
> >> {
> >> return __raw_readl(power + EXYNOS_ARM_CORE_STATUS(cpu)) &
> >> - S5P_CORE_LOCAL_PWR_EN;
> >> + S5P_CORE_LOCAL_PWR_EN;
> >
> > Please avoid spurious whitespace changes (especially since this one is
> > wrong...)
> >
>
> Julien had commented on this too. My response was:
> "We are anding the result of the readl, and hence as its outside of the
> readl (and not a parameter to it), I aligned it as such. Is that not
> right? Cause, if I align it under the ( of readl, it will appear as if
> it was a parameter to readl. Please let me know."
Hrm, ok. But it's still a spurious change as far as this commit goes, we
generally try and avoid such things (and this patch is already skirting
close to changing too much in one go)
> >> +static void exynos_smc(u32 cmd, u32 arg1, u32 arg2, u32 arg3)
> >> +{
> >> + asm(
> >> + "dsb;"
> >> + "smc #0;"
> >> + );
> >
> > I don't think this will work reliably in the face of compiler
> > optimisations. You need something like __invoke_psci_fn_smc. In fact it
> > would probably be best to refactor that into a common function for
> > calling into firmware (which looks like it might be a case of renaming
> > the existing fn and moving it somewhere more appropriate).
> >
>
> Julien had commented on this too, and he too recommended I take a look
> at __invoke_psci_fn_smc in xen/arch/arm/psci.c
>
> I had taken these into consideration and submitted a v3 of this patch.
Oh, I seem to have missed that, sorry.
prev parent reply other threads:[~2014-09-18 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 23:01 [XEN/ARM PATCH v2 1/1] Add support for Exynos secure firmware Suriyan Ramasami
2014-09-12 23:52 ` Julien Grall
2014-09-13 2:08 ` Suriyan Ramasami
2014-09-17 8:37 ` Tamas K Lengyel
2014-09-17 15:38 ` Suriyan Ramasami
2014-09-17 22:17 ` Suriyan Ramasami
2014-09-17 22:23 ` Julien Grall
2014-09-17 22:39 ` Suriyan Ramasami
2014-09-18 18:30 ` Ian Campbell
2014-09-18 18:44 ` Suriyan Ramasami
2014-09-18 19:06 ` Ian Campbell [this message]
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=1411067162.1920.31.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).