linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: Add platform support for LSI AXM55xx SoC
Date: Thu, 24 Apr 2014 10:04:44 +0100	[thread overview]
Message-ID: <20140424090444.GF26756@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <80a2523d3e266ed12d5b70ac5518e963e47b27f4.1397552154.git.anders.berg@lsi.com>

On Tue, Apr 15, 2014 at 02:06:10PM +0200, Anders Berg wrote:
> +	adr	r4, 2f
> +	ldmia	r4, {r5, r6}
> +	sub	r4, r4, r5
> +	add	r6, r6, r4
> +1:	ldr	r7, [r6]
> +	cmp	r7, r0
> +	wfene
> +	bne	1b
...
> +2:	.long	.
> +	.long	pen_release
> diff --git a/arch/arm/mach-axxia/platsmp.c b/arch/arm/mach-axxia/platsmp.c
...
> +/*
> + * Write pen_release in a way that is guaranteed to be visible to all
> + * observers, irrespective of whether they're taking part in coherency
> + * or not.  This is necessary for the hotplug code to work reliably.
> + */
> +static void write_pen_release(int val)
> +{
> +	pen_release = val;
> +	/* Make sure this store is visible to other CPUs */
> +	smp_wmb();
> +	__cpuc_flush_dcache_area((void *)&pen_release, sizeof(pen_release));
> +}

Do you /really/ need to do this pen_release thing on your platform?

> +static void __init axxia_smp_prepare_cpus(unsigned int max_cpus)
> +{
...
> +		/*
> +		 * Release all physical cpus when not in hyp mode since we
> +		 * might want to bring them online later.
> +		 *
> +		 * Also we need to get the execution into kernel code (it's
> +		 * currently executing in u-boot).  u-boot releases the cores
> +		 * from reset in hyp mode.
> +		 */
> +		if (!is_hyp_mode_available()) {
> +			if (cpu != 0) {
> +				u32 tmp = readl(syscon + 0x1010);
> +				writel(0xab, syscon + 0x1000);
> +				tmp &= ~(1 << cpu);
> +				writel(tmp, syscon + 0x1010);
> +			}

As this implies that you can control the release of each CPU from u-boot
individually.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  parent reply	other threads:[~2014-04-24  9:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 12:06 [PATCH 0/5] Add platform support for LSI AXM55xx Anders Berg
2014-04-15 12:06 ` [PATCH 1/5] ARM: Add platform support for LSI AXM55xx SoC Anders Berg
2014-04-15 12:30   ` Arnd Bergmann
2014-04-24  8:58     ` Anders Berg
2014-04-24  9:04   ` Russell King - ARM Linux [this message]
2014-04-15 12:06 ` [PATCH 2/5] ARM: dts: Device tree for AXM55xx Anders Berg
2014-04-15 12:42   ` Marc Zyngier
2014-04-15 14:56     ` Anders Berg
2014-04-15 12:45   ` Arnd Bergmann
2014-04-15 15:20     ` Anders Berg
2014-04-15 15:23       ` Arnd Bergmann
2014-04-22 21:21         ` Linus Walleij
2014-04-22 21:31     ` Linus Walleij
2014-04-22 21:39     ` Russell King - ARM Linux
2014-04-15 12:06 ` [PATCH 3/5] ARM: axxia: Adding defconfig " Anders Berg
2014-04-15 12:06 ` [PATCH 4/5] power: reset: Add Axxia system reset driver Anders Berg
2014-04-15 12:06 ` [PATCH 5/5] ARM: dts: axxia: Add reset controller Anders Berg

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=20140424090444.GF26756@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).