From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: oxnas: Add OX820 SMP support
Date: Mon, 17 Oct 2016 11:06:20 +0200 [thread overview]
Message-ID: <14513531.isB50DxNJf@wuerfel> (raw)
In-Reply-To: <20161017084303.20078-2-narmstrong@baylibre.com>
On Monday, October 17, 2016 10:43:02 AM CEST Neil Armstrong wrote:
> +
> + /*
> + * This is really belt and braces; we hold unintended secondary
> + * CPUs in the holding pen until we're ready for them. However,
> + * since we haven't sent them a soft interrupt, they shouldn't
> + * be there.
> + */
> + write_pen_release(cpu);
> +
> + /*
> + * Enable GIC cpu interface in CPU Interface Control Register
> + */
> + writel(GIC_CPU_CTRL_ENABLE,
> + gic_cpu_ctrl + GIC_NCPU_OFFSET(cpu) + GIC_CPU_CTRL);
> +
> + /*
> + * Send the secondary CPU a soft interrupt, thereby causing
> + * the boot monitor to read the system wide flags register,
> + * and branch to the address found there.
> + */
> +
> + arch_send_wakeup_ipi_mask(cpumask_of(cpu));
> + timeout = jiffies + (1 * HZ);
> + while (time_before(jiffies, timeout)) {
> + smp_rmb();
> + if (read_pen_release() == -1)
> + break;
> +
> + udelay(10);
> + }
>
This seems to have been copied from plat-versatile, but is really
not needed here since you apparently have proper hardware support for
starting up the CPUs.
Any reason you can't just write to the cpu_ctrl register
once and keep going without that whole holding_pen loop
and spinlock?
Arnd
next prev parent reply other threads:[~2016-10-17 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 8:43 [PATCH 0/2] ARM: oxnas: Add SMP support for OX820 Neil Armstrong
2016-10-17 8:43 ` [PATCH 1/2] ARM: oxnas: Add OX820 SMP support Neil Armstrong
2016-10-17 9:06 ` Arnd Bergmann [this message]
2016-10-17 9:34 ` Neil Armstrong
2016-10-31 8:18 ` Russell King - ARM Linux
2016-10-17 8:43 ` [PATCH 2/2] ARM: oxnas: Add OX820 config and makefile entry Neil Armstrong
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=14513531.isB50DxNJf@wuerfel \
--to=arnd@arndb.de \
--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