This works on my A9x4 coretile, bringing CPUs up and down via /sys/devices/system/cpu/*/online, so: Tested-by: Mark Rutland <mark.rutland@xxxxxxx> Otherwise, is there any reason we couldn't now use the twd driver on a UP system? Or would the overhead of handling frequency change make this pointless? On Wed, Mar 13, 2013 at 06:17:49PM +0000, Stephen Boyd wrote: > Separate the smp_twd timers from the local timer API. This will > allow us to remove ARM local timer support in the near future and > gets us closer to moving this driver to drivers/clocksource. > > Cc: Russell King <linux@xxxxxxxxxxxxxxxx> > Cc: Tony Lindgren <tony@xxxxxxxxxxx> > Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> > --- > > Changes since v2: > * Fix booting on qemu and omap > > arch/arm/Kconfig | 2 +- > arch/arm/kernel/smp_twd.c | 64 +++++++++++++++++++++++++++++++---------------- > 2 files changed, 44 insertions(+), 22 deletions(-) > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > index 5b71469..5ad2ccf 100644 > --- a/arch/arm/Kconfig > +++ b/arch/arm/Kconfig > @@ -1527,6 +1527,7 @@ config SMP > depends on HAVE_SMP > depends on MMU > select HAVE_ARM_SCU if !ARCH_MSM_SCORPIONMP > + select HAVE_ARM_TWD if (!ARCH_MSM_SCORPIONMP && !EXYNOS4_MCT) Could you not depend on your "Push selects for TWD/SCU into machine entries" for this? Mark. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
