linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: formalize an IPI for CPU wake-ups
Date: Wed, 22 Aug 2012 12:05:38 -0700	[thread overview]
Message-ID: <50352D82.2050509@codeaurora.org> (raw)
In-Reply-To: <50297B34.5090504@codeaurora.org>

On 08/13/12 15:09, Stephen Boyd wrote:
> On 08/07/12 23:52, Magnus Damm wrote:
>> So I finally managed to try this out on my KZM9D board. The SMP bring
>> up code continues to work as expected, so it seems that SGI0 can be
>> used instead of SGI1 on EMEV2. Let's just say that the boot protocol
>> implemented by the mask ROM is rather poorly documented. Anyway, to
>> test I used the following patch on top of linux git 42a579a.
>>
>> --- 0001/arch/arm/mach-shmobile/smp-emev2.c
>> +++ work/arch/arm/mach-shmobile/smp-emev2.c	2012-08-08 15:42:54.000000000 +0900
>> @@ -82,7 +82,7 @@ int __cpuinit emev2_boot_secondary(unsig
>>  	/* Tell ROM loader about our vector (in headsmp.S) */
>>  	emev2_set_boot_vector(__pa(shmobile_secondary_vector));
>>
>> -	gic_raise_softirq(cpumask_of(cpu), 1);
>> +	gic_raise_softirq(cpumask_of(cpu), 0);
>>  	return 0;
>>  }
>>
>> So if/where needed, please add my:
>>
>> Acked-by: Magnus Damm <damm@opensource.se>
>>
> Thanks Magnus, would you be able to merge this through the shmobile
> tree? Otherwise I can put it in the patch tracker.
>

Ok, I've put it in the patch tracker.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2012-08-22 19:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 15:54 [PATCH] ARM: formalize an IPI for CPU wake-ups Nicolas Pitre
2012-06-11 15:57 ` Russell King - ARM Linux
2012-06-11 16:44   ` Nicolas Pitre
2012-06-11 16:51     ` Russell King - ARM Linux
2012-06-11 17:18       ` Nicolas Pitre
2012-06-11 17:41         ` Stephen Boyd
2012-06-11 19:25           ` Russell King - ARM Linux
2012-06-20 16:32             ` Stephen Boyd
2012-07-11  6:34               ` Kukjin Kim
2012-07-30 18:19                 ` Stephen Boyd
2012-08-01  9:42                   ` Kukjin Kim
2012-08-06 20:41                     ` Colin Cross
2012-08-07 17:00                       ` Russell King - ARM Linux
2012-08-08  7:04                         ` Shilimkar, Santosh
2012-08-08 10:39                       ` Kukjin Kim
2012-08-08  6:52                   ` Magnus Damm
2012-08-13 22:09                     ` Stephen Boyd
2012-08-22 19:05                       ` Stephen Boyd [this message]
2012-08-22 21:23                         ` Magnus Damm
2012-08-29  7:21                         ` Stephen Boyd
2012-09-08 14:47                           ` Nicolas Pitre
2012-06-11 18:26         ` Russell King - ARM Linux
2012-06-11 18:40           ` Nicolas Pitre
2012-06-11 18:41             ` Russell King - ARM Linux
2012-06-11 19:11               ` Nicolas Pitre
2012-06-11 19:20                 ` Russell King - ARM Linux
2012-06-11 19:56                   ` 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=50352D82.2050509@codeaurora.org \
    --to=sboyd@codeaurora.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).