From: Magnus Damm <magnus.damm@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 02/05] ARM: shmobile: Use shmobile_smp_cpu_disable() on sh73a0
Date: Wed, 07 Aug 2013 22:13:39 +0000 [thread overview]
Message-ID: <20130807221339.22251.99940.sendpatchset@w520> (raw)
In-Reply-To: <20130807221321.22251.22774.sendpatchset@w520>
From: Magnus Damm <damm@opensource.se>
Use shmobile_smp_cpu_disable() on sh73a0 since it
allows CPU Hotplug of any CPU.
Signed-off-by: Magnus Damm <damm@opensource.se>
---
arch/arm/mach-shmobile/smp-sh73a0.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
--- 0008/arch/arm/mach-shmobile/smp-sh73a0.c
+++ work/arch/arm/mach-shmobile/smp-sh73a0.c 2013-07-29 22:21:29.000000000 +0900
@@ -71,18 +71,11 @@ static void __init sh73a0_smp_prepare_cp
shmobile_smp_scu_prepare_cpus(max_cpus);
}
-#ifdef CONFIG_HOTPLUG_CPU
-static int sh73a0_cpu_disable(unsigned int cpu)
-{
- return 0; /* CPU0 and CPU1 supported */
-}
-#endif /* CONFIG_HOTPLUG_CPU */
-
struct smp_operations sh73a0_smp_ops __initdata = {
.smp_prepare_cpus = sh73a0_smp_prepare_cpus,
.smp_boot_secondary = sh73a0_boot_secondary,
#ifdef CONFIG_HOTPLUG_CPU
- .cpu_disable = sh73a0_cpu_disable,
+ .cpu_disable = shmobile_smp_cpu_disable,
.cpu_die = shmobile_smp_scu_cpu_die,
.cpu_kill = shmobile_smp_scu_cpu_kill,
#endif
next prev parent reply other threads:[~2013-08-07 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 22:13 [PATCH 00/05] ARM: shmobile: Yet another SMP series Magnus Damm
2013-08-07 22:13 ` [PATCH 01/05] ARM: shmobile: Introduce shmobile_smp_cpu_disable() Magnus Damm
2013-08-07 22:13 ` Magnus Damm [this message]
2013-08-07 22:13 ` [PATCH 03/05] ARM: shmobile: Remove unused shmobile_smp_init_cpus() Magnus Damm
2013-08-07 22:13 ` [PATCH 04/05] ARM: shmobile: Expose shmobile_invalidate_start() Magnus Damm
2013-08-07 22:14 ` [PATCH 05/05] ARM: shmobile: Introduce shmobile_boot_size Magnus Damm
2013-08-21 8:59 ` [PATCH 00/05] ARM: shmobile: Yet another SMP series Simon Horman
2013-08-22 6:32 ` Simon Horman
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=20130807221339.22251.99940.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--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).