[PATCH v2 00/15] Make SMP timers standalone

johlstei johlstei at codeaurora.org
Thu Jan 5 14:34:14 EST 2012


On 01/05/2012 02:26 AM, Linus Walleij wrote:
> On Thu, Jan 5, 2012 at 2:17 AM, David Brown<davidb at codeaurora.org>  wrote:
>> On Wed, Jan 04, 2012 at 05:39:16PM +0000, Marc Zyngier wrote:
>>> I do. But on some non-SMP platforms, the local timer and the global
>>> timer can actually be the same (MSM is one example of this, and the UP
>>> version of the Cortex A15 is another).
>> On SMP MSM, we use the CPU0 local timer as the global timer.  They are
>> the same on non-SMP as well,
> Does this mean your CPU0 local timer is always on, always clocked?
> And do you use ARMs SMP TWD IP block for that?
>
Yes, CPU0's local timer is always on. We use it as a global clocksource, 
as well
as for udelay on both cores. It is not ARM's SMP TWD block, it is our 
own. The
timer blocks can each be read from both CPUs, but can only generate IRQs 
to one
or the other.

Jeff



More information about the linux-arm-kernel mailing list