On Wednesday 22 January 2014 11:46:16 Mark Rutland wrote: > On Mon, Jan 20, 2014 at 09:08:32AM +0000, Hanjun Guo wrote: > > On 2014-1-17 22:21, Arnd Bergmann wrote: > > > On Friday 17 January 2014, Hanjun Guo wrote: > > >> > > >> From: Amit Daniel Kachhap <amit.daniel@xxxxxxxxxxx> > > >> > > >> This macro does the same job as CLOCKSOURCE_OF_DECLARE. The device > > >> name from the ACPI timer table is matched with all the registered > > >> timer controllers and matching initialisation routine is invoked. > > > > > > I wouldn't anticipate this infrastructure to be required. Shouldn't all > > > ARMv8 machines have an architected timer? > > > > I not sure of this, could anyone can give some guidance? if only arch > > timer is available for ARM64, this will make thing very simple. > > All ARMv8 systems should have an architected timer. > > However, they may also have other timers (e.g. global timers for use > when CPUs are in low power states and their local architected timers > aren't active). But all other timers could be regular platform drivers I suppose. No need for special infrastructure for those. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
