From mboxrd@z Thu Jan 1 00:00:00 1970 From: ananaza@iki.fi (Antti Miettinen) Date: Fri, 17 Jan 2014 12:30:48 +0200 Subject: [PATCH] arch_timer: Move delay timer to drivers clocksource In-Reply-To: <52D8F403.9070602@linaro.org> (Daniel Lezcano's message of "Fri, 17 Jan 2014 10:12:35 +0100") References: <1389791227-24097-1-git-send-email-pgaikwad@nvidia.com> <20140115154526.GC3571@mudshark.cambridge.arm.com> <52D76BC8.6080405@nvidia.com> <20140116121649.GG30257@mudshark.cambridge.arm.com> <878uufyo13.fsf@iki.fi> <52D8F403.9070602@linaro.org> Message-ID: <874n52zyqv.fsf@iki.fi> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Daniel Lezcano writes: > On 01/17/2014 10:07 AM, Antti Miettinen wrote: >> Will Deacon writes: >>> Why can't you use the C3STOP feature so that the arch-timer isn't used when >>> you go idle? >> >> That would mean falling back to broadcast timer, right? That's not >> necessarily on the local CPU so wakeups would often wake two CPUs. > > You can prevent that if the hardware supports it with the > CLOCK_EVT_DYNIRQ flag on the broadcast timer. CLOCK_EVT_FEAT_DYNIRQ seems to be the flag. Cool, thanks. --Antti