From: "Shilimkar, Santosh" <santosh.shilimkar@ti.com> To: Arnd Bergmann <arnd@arndb.de> Cc: linux-arm-kernel@lists.infradead.org, Russell King <rmk+kernel@arm.linux.org.uk>, linux-kernel@vger.kernel.org, Kevin Hilman <khilman@ti.com>, Tony Lindgren <tony@atomide.com> Subject: Re: [PATCH 2/6] ARM: omap: allow building omap44xx without SMP Date: Wed, 22 Aug 2012 21:06:38 +0530 [thread overview] Message-ID: <CAMQu2gw0x6saWrK-M3teu49tJDGvS8RhGrVSh6JTs5DEy+22pA@mail.gmail.com> (raw) In-Reply-To: <1345648390-4234-3-git-send-email-arnd@arndb.de> On Wed, Aug 22, 2012 at 8:43 PM, Arnd Bergmann <arnd@arndb.de> wrote: > The new omap4 cpuidle implementation currently requires > ARCH_NEEDS_CPU_IDLE_COUPLED, which only works on SMP. > > This patch makes it possible to build a non-SMP kernel > for that platform. This is not normally desired for > end-users but can be useful for testing. > > Without this patch, building rand-0y2jSKT results in: > > drivers/cpuidle/coupled.c: In function 'cpuidle_coupled_poke': > drivers/cpuidle/coupled.c:317:3: error: implicit declaration of function '__smp_call_function_single' [-Werror=implicit-function-declaration] > > It's not clear if this patch is the best solution for > the problem at hand. I have made sure that we can now > build the kernel in all configurations, but that does > not mean it will actually work on an OMAP44xx. > Am not sure either about the subject patch. > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> > Cc: Kevin Hilman <khilman@ti.com> > Cc: Tony Lindgren <tony@atomide.com> > --- > arch/arm/mach-omap2/Kconfig | 2 +- > arch/arm/mach-omap2/cpuidle44xx.c | 3 ++- > include/linux/cpuidle.h | 4 ++++ > 3 files changed, 7 insertions(+), 2 deletions(-) > > diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig > index dd2db02..66a8be3 100644 > --- a/arch/arm/mach-omap2/Kconfig > +++ b/arch/arm/mach-omap2/Kconfig > @@ -62,7 +62,7 @@ config ARCH_OMAP4 > select PM_OPP if PM > select USB_ARCH_HAS_EHCI if USB_SUPPORT > select ARM_CPU_SUSPEND if PM > - select ARCH_NEEDS_CPU_IDLE_COUPLED > + select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP > > config SOC_OMAP5 > bool "TI OMAP5" > diff --git a/arch/arm/mach-omap2/cpuidle44xx.c b/arch/arm/mach-omap2/cpuidle44xx.c > index ee05e19..288bee6 100644 > --- a/arch/arm/mach-omap2/cpuidle44xx.c > +++ b/arch/arm/mach-omap2/cpuidle44xx.c > @@ -238,8 +238,9 @@ int __init omap4_idle_init(void) > for_each_cpu(cpu_id, cpu_online_mask) { > dev = &per_cpu(omap4_idle_dev, cpu_id); > dev->cpu = cpu_id; > +#ifdef CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED > dev->coupled_cpus = *cpu_online_mask; > - > +#endif Was just thinking whether we should just take care of it at core cpuidle level itself. Will below be enough to kill the build error what you mentioned in the change log ? diff --git a/drivers/cpuidle/coupled.c b/drivers/cpuidle/coupled.c index 2c9bf26..df34534 100644 --- a/drivers/cpuidle/coupled.c +++ b/drivers/cpuidle/coupled.c @@ -314,7 +314,9 @@ static void cpuidle_coupled_poke(int cpu) struct call_single_data *csd = &per_cpu(cpuidle_coupled_poke_cb, cpu); if (!cpumask_test_and_set_cpu(cpu, &cpuidle_coupled_poked_mask)) +#ifdef CONFIG_SMP __smp_call_function_single(cpu, csd, 0); +#endif } /** Regards Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Shilimkar, Santosh) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/6] ARM: omap: allow building omap44xx without SMP Date: Wed, 22 Aug 2012 21:06:38 +0530 [thread overview] Message-ID: <CAMQu2gw0x6saWrK-M3teu49tJDGvS8RhGrVSh6JTs5DEy+22pA@mail.gmail.com> (raw) In-Reply-To: <1345648390-4234-3-git-send-email-arnd@arndb.de> On Wed, Aug 22, 2012 at 8:43 PM, Arnd Bergmann <arnd@arndb.de> wrote: > The new omap4 cpuidle implementation currently requires > ARCH_NEEDS_CPU_IDLE_COUPLED, which only works on SMP. > > This patch makes it possible to build a non-SMP kernel > for that platform. This is not normally desired for > end-users but can be useful for testing. > > Without this patch, building rand-0y2jSKT results in: > > drivers/cpuidle/coupled.c: In function 'cpuidle_coupled_poke': > drivers/cpuidle/coupled.c:317:3: error: implicit declaration of function '__smp_call_function_single' [-Werror=implicit-function-declaration] > > It's not clear if this patch is the best solution for > the problem at hand. I have made sure that we can now > build the kernel in all configurations, but that does > not mean it will actually work on an OMAP44xx. > Am not sure either about the subject patch. > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> > Cc: Kevin Hilman <khilman@ti.com> > Cc: Tony Lindgren <tony@atomide.com> > --- > arch/arm/mach-omap2/Kconfig | 2 +- > arch/arm/mach-omap2/cpuidle44xx.c | 3 ++- > include/linux/cpuidle.h | 4 ++++ > 3 files changed, 7 insertions(+), 2 deletions(-) > > diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig > index dd2db02..66a8be3 100644 > --- a/arch/arm/mach-omap2/Kconfig > +++ b/arch/arm/mach-omap2/Kconfig > @@ -62,7 +62,7 @@ config ARCH_OMAP4 > select PM_OPP if PM > select USB_ARCH_HAS_EHCI if USB_SUPPORT > select ARM_CPU_SUSPEND if PM > - select ARCH_NEEDS_CPU_IDLE_COUPLED > + select ARCH_NEEDS_CPU_IDLE_COUPLED if SMP > > config SOC_OMAP5 > bool "TI OMAP5" > diff --git a/arch/arm/mach-omap2/cpuidle44xx.c b/arch/arm/mach-omap2/cpuidle44xx.c > index ee05e19..288bee6 100644 > --- a/arch/arm/mach-omap2/cpuidle44xx.c > +++ b/arch/arm/mach-omap2/cpuidle44xx.c > @@ -238,8 +238,9 @@ int __init omap4_idle_init(void) > for_each_cpu(cpu_id, cpu_online_mask) { > dev = &per_cpu(omap4_idle_dev, cpu_id); > dev->cpu = cpu_id; > +#ifdef CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED > dev->coupled_cpus = *cpu_online_mask; > - > +#endif Was just thinking whether we should just take care of it at core cpuidle level itself. Will below be enough to kill the build error what you mentioned in the change log ? diff --git a/drivers/cpuidle/coupled.c b/drivers/cpuidle/coupled.c index 2c9bf26..df34534 100644 --- a/drivers/cpuidle/coupled.c +++ b/drivers/cpuidle/coupled.c @@ -314,7 +314,9 @@ static void cpuidle_coupled_poke(int cpu) struct call_single_data *csd = &per_cpu(cpuidle_coupled_poke_cb, cpu); if (!cpumask_test_and_set_cpu(cpu, &cpuidle_coupled_poked_mask)) +#ifdef CONFIG_SMP __smp_call_function_single(cpu, csd, 0); +#endif } /** Regards Santosh
next prev parent reply other threads:[~2012-08-22 15:37 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-22 15:13 [PATCH 0/6] ARM: randconfig bugs Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-22 15:13 ` [PATCH 1/6] ARM: ux500: don't select LEDS_GPIO for snowball Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-23 14:26 ` Arnd Bergmann 2012-08-23 14:26 ` Arnd Bergmann 2012-08-27 23:40 ` Linus Walleij 2012-08-27 23:40 ` Linus Walleij 2012-08-22 15:13 ` [PATCH 2/6] ARM: omap: allow building omap44xx without SMP Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-22 15:36 ` Shilimkar, Santosh [this message] 2012-08-22 15:36 ` Shilimkar, Santosh 2012-08-22 17:22 ` Arnd Bergmann 2012-08-22 17:22 ` Arnd Bergmann 2012-08-23 7:05 ` Shilimkar, Santosh 2012-08-23 7:05 ` Shilimkar, Santosh 2012-08-23 12:12 ` Arnd Bergmann 2012-08-23 12:12 ` Arnd Bergmann 2012-08-23 13:00 ` Shilimkar, Santosh 2012-08-23 13:00 ` Shilimkar, Santosh 2012-08-23 13:32 ` Arnd Bergmann 2012-08-23 13:32 ` Arnd Bergmann 2012-08-22 15:13 ` [PATCH 3/6] ARM: imx: build pm-imx5 code only when PM is enabled Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-23 2:07 ` Shawn Guo 2012-08-23 2:07 ` Shawn Guo 2012-08-22 15:13 ` [PATCH 4/6] ARM: imx: fix ksz9021rn_phy_fixup Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-23 2:10 ` Shawn Guo 2012-08-23 2:10 ` Shawn Guo 2012-08-22 15:13 ` [PATCH 5/6] ARM: imx: select CPU_FREQ_TABLE when needed Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-23 2:13 ` Shawn Guo 2012-08-23 2:13 ` Shawn Guo 2012-08-22 15:13 ` [PATCH 6/6] ARM: imx: select ARM_CPU_SUSPEND when necessary Arnd Bergmann 2012-08-22 15:13 ` Arnd Bergmann 2012-08-23 2:41 ` Shawn Guo 2012-08-23 2:41 ` Shawn Guo 2012-08-23 14:20 ` Arnd Bergmann 2012-08-23 14:20 ` Arnd Bergmann 2012-08-23 14:55 ` Shawn Guo 2012-08-23 14:55 ` Shawn Guo
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=CAMQu2gw0x6saWrK-M3teu49tJDGvS8RhGrVSh6JTs5DEy+22pA@mail.gmail.com \ --to=santosh.shilimkar@ti.com \ --cc=arnd@arndb.de \ --cc=khilman@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rmk+kernel@arm.linux.org.uk \ --cc=tony@atomide.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.