From: Ian Campbell <ian.campbell@citrix.com>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: keir@xen.org, julien.grall@linaro.org, tim@xen.org,
xen-devel@lists.xen.org, jbeulich@suse.com,
ian.jackson@citrix.com
Subject: Re: [XEN/ARM PATCH v2 1/1] Add support for Exynos secure firmware
Date: Thu, 18 Sep 2014 19:30:29 +0100 [thread overview]
Message-ID: <1411065029.1920.23.camel@citrix.com> (raw)
In-Reply-To: <1410562915-16761-1-git-send-email-suriyan.r@gmail.com>
On Fri, 2014-09-12 at 16:01 -0700, Suriyan Ramasami wrote:
Mostly looks good, couple of comments below. I'll also try and give it a
spin on arndale when I'm back in the office early next week.
> +/* This corresponds to CONFIG_NR_CPUS in linux config */
> +#define EXYNOS_CONFIG_NR_CPUS 0x08
This doesn't appear to be used, which is good because it would be wrong
to hardcode such things into Xen.
> @@ -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...)
> +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).
Ian.
next prev parent reply other threads:[~2014-09-18 18:30 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 [this message]
2014-09-18 18:44 ` Suriyan Ramasami
2014-09-18 19:06 ` Ian Campbell
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=1411065029.1920.23.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=keir@xen.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).