From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/8] ARM: vexpress/dcscb: select multi-cluster SMP operations
Date: Wed, 29 May 2013 11:48:24 +0100 [thread overview]
Message-ID: <1369824504.3715.23.camel@linaro1.home> (raw)
In-Reply-To: <1369374311-21260-9-git-send-email-nicolas.pitre@linaro.org>
On Fri, 2013-05-24 at 01:45 -0400, Nicolas Pitre wrote:
> When the DCSCB code is successfully probed and initialized, then the
> generic MCPM SPM ops should be used as those operations need to be
> arbitrated through the MCPM layer.
>
> Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
> ---
> arch/arm/mach-vexpress/dcscb.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/mach-vexpress/dcscb.c b/arch/arm/mach-vexpress/dcscb.c
> index 1acc975360..ce3118dc05 100644
> --- a/arch/arm/mach-vexpress/dcscb.c
> +++ b/arch/arm/mach-vexpress/dcscb.c
> @@ -239,6 +239,8 @@ static int __init dcscb_init(void)
> return ret;
> }
>
> + mcpm_smp_set_ops();
> +
This is going to change the platform's smp_ops after setup_arch() has
already set them, is that OK and not too late?
I ask, because for me, RTSM doesn't boot the secondary CPUs if we rely
on this change to set the smp_ops, but having a hook in setup_arch() to
select instead of the standard vexpress ops does work.
I haven't investigated this more fully yet.
--
Tixy
next prev parent reply other threads:[~2013-05-29 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 5:45 [PATCH 0/8] MCPM support for big.LITTLE Virtual Express RTSM Nicolas Pitre
2013-05-24 5:45 ` [PATCH 1/8] drivers: bus: add ARM CCI support Nicolas Pitre
2013-05-29 12:11 ` Jon Medhurst (Tixy)
2013-05-29 14:49 ` Nicolas Pitre
2013-05-24 5:45 ` [PATCH 2/8] drivers/bus: arm-cci: function to enable CCI ports from early boot code Nicolas Pitre
2013-05-24 18:23 ` Dave Martin
2013-05-24 5:45 ` [PATCH 3/8] ARM: introduce common set_auxcr/get_auxcr functions Nicolas Pitre
2013-05-29 13:42 ` Jon Medhurst (Tixy)
2013-05-29 15:28 ` Nicolas Pitre
2013-05-24 5:45 ` [PATCH 4/8] ARM: vexpress: introduce DCSCB support Nicolas Pitre
2013-05-24 5:45 ` [PATCH 5/8] ARM: vexpress/dcscb: add CPU use counts to the power up/down API implementation Nicolas Pitre
2013-05-24 5:45 ` [PATCH 6/8] ARM: vexpress/dcscb: do not hardcode number of CPUs per cluster Nicolas Pitre
2013-05-24 5:45 ` [PATCH 7/8] ARM: vexpress/dcscb: handle platform coherency exit/setup and CCI Nicolas Pitre
2013-05-29 12:29 ` Jon Medhurst (Tixy)
2013-05-29 14:25 ` Javi Merino
2013-05-24 5:45 ` [PATCH 8/8] ARM: vexpress/dcscb: select multi-cluster SMP operations Nicolas Pitre
2013-05-29 10:48 ` Jon Medhurst (Tixy) [this message]
2013-05-29 15:17 ` Nicolas Pitre
2013-05-29 16:37 ` Jon Medhurst (Tixy)
2013-05-29 16:59 ` Nicolas Pitre
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=1369824504.3715.23.camel@linaro1.home \
--to=tixy@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).