Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755600Ab3FQAVA (ORCPT ); Sun, 16 Jun 2013 20:21:00 -0400 Received: from mail-pb0-f43.google.com ([209.85.160.43]:58898 "EHLO mail-pb0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754621Ab3FQAU6 (ORCPT ); Sun, 16 Jun 2013 20:20:58 -0400 From: Magnus Damm To: linux-kernel@vger.kernel.org Cc: mark.rutland@arm.com, linux-sh@vger.kernel.org, marc.zyngier@arm.com, catalin.marinas@arm.com, horms@verge.net.au, john.stultz@linaro.org, shinya.kuribayashi.px@renesas.com, Magnus Damm , tglx@linutronix.de Date: Mon, 17 Jun 2013 09:20:56 +0900 Message-Id: <20130617002056.7646.54131.sendpatchset@w520> Subject: [PATCH/RFC] arm: arch_timer: Do not set C3STOP in case CPU_IDLE=n Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2246 Lines: 55 From: Magnus Damm Modify the ARM architected timer driver to not set C3STOP in case CPU_IDLE is disabled. This is a short term fix that allows use of high resolution timers even though no additional clock event is registered. Not-really-Signed-off-by: Magnus Damm --- If someone cares about this case then perhaps it should be moved up to the clock event main code. The same issue should in theory trigger on all architectures, perhaps x86 people hunting for low latency may try to disable CPU_IDLE? I propose carrying this patch locally to enable high resolution timers until CPU_IDLE and an additional clock event is supported. Observed on r8a73a4 and APE6EVM. drivers/clocksource/arm_arch_timer.c | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) --- 0001/drivers/clocksource/arm_arch_timer.c +++ work/drivers/clocksource/arm_arch_timer.c 2013-06-17 09:03:44.000000000 +0900 @@ -125,7 +125,23 @@ static int arch_timer_set_next_event_phy static int __cpuinit arch_timer_setup(struct clock_event_device *clk) { - clk->features = CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_C3STOP; + clk->features = CLOCK_EVT_FEAT_ONESHOT; +#ifdef CONFIG_CPU_IDLE + /* By not setting the C3STOP flag it is possible to let the + * ARM architected timer to be the only clock event installed + * on the system and have working high resolution timers. + * + * If the C3STOP flag is set unconditionally then the kernel + * will always prevent using the high resoultion timer feature + * unless an additional clock event is registered. + * + * In the case where CPU_IDLE is enabled then there is a chance + * that deeper sleep states will be handled by software, but + * if CPU_IDLE is disabled then deep sleep states cannot be + * entered and the feature flagged by C3STOP is not needed. + */ + clk->features |= CLOCK_EVT_FEAT_C3STOP; +#endif clk->name = "arch_sys_timer"; clk->rating = 450; if (arch_timer_use_virtual) { -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/