From mboxrd@z Thu Jan  1 00:00:00 1970
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
Date: Thu, 5 Jan 2012 12:10:26 +0000
Subject: [PATCH v2 00/15] Make SMP timers standalone
In-Reply-To: <4F058B1C.2070109@arm.com>
References: <1324574865-5367-1-git-send-email-marc.zyngier@arm.com>
 <20111222193216.GO2577@n2100.arm.linux.org.uk> <4F048EC4.40900@arm.com>
 <20120104214748.GH11810@n2100.arm.linux.org.uk>
 <CACRpkdZPEYc3xNNb1w4st86bLGMW0ePbEA6+V4opHXe6Sk=u2g@mail.gmail.com>
 <4F0584B5.60908@arm.com>
 <CAMQu2gxuBNRWYKyKRdzvv_m49DyLoODVbC=rKDHDAMTnxe+6+A@mail.gmail.com>
 <4F058744.4030503@arm.com> <20120105112602.GQ11810@n2100.arm.linux.org.uk>
 <4F058B1C.2070109@arm.com>
Message-ID: <20120105121026.GS11810@n2100.arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On Thu, Jan 05, 2012 at 11:35:56AM +0000, Marc Zyngier wrote:
> On 05/01/12 11:26, Russell King - ARM Linux wrote:
> > Look, local timers *are* special.  They're not the same as global timers.
> > They're treated differently.  Ripping out the local timer setup stuff
> > from the SMP code is not the right solution, especially when we've
> > already got a separation of the local timer core from the hardware
> > implementation.
> 
> OK. I'll try to work out something different.

Why?  What's wrong with the existing structure?

If you want to use the TWD as a global timer, that's easy to do:

static struct clock_event_device twd_global_ce = {
	.irq = whatever_irq,
	.cpumask = cpu_mask_all,
};

static int __init twd_global_timer(void)
{
	twd_base = ioremap(twd_phys, SZ_4K);
	if (!twd_base)
		return -ENOMEM;
	twd_timer_setup(&twd_global_ce);
	return 0;
}

And no need to mess around with the local timer structure in
arch/arm/kernel/smp.c.