[PATCH v2] arm: zynq: Fix system clock with multi_v7_defconfig

[Sören Brinkmann]

On Fri, 2015-04-10 at 10:59PM +0200, Arnd Bergmann wrote:
> On Friday 10 April 2015 13:41:34 Sören Brinkmann wrote:
> > On Fri, 2015-04-10 at 10:04PM +0200, Arnd Bergmann wrote:
> > > I've just had another idea: how about introducing a new compatible string
> > > for the global timer that gets used for timers that have their frequency
> > > tied to the CPU (alternatively a bool property in that node). This can
> > > be checked by the clocksource driver, which will then be able to either
> > > skip the device if cpufreq is in use, or implement a more sophisticated
> > > workaround.
> > 
> > If this is the only available clocksource, you'd still want to use it
> > though. A bad clocksource is still better than none. But I guess that
> > would just mean to lie in the DT.
> 
> On zynq, you always have a local time, right?

Yes, we have the cadence_ttc as clocksource.

> If we get a platform that has no reliable clocksource, it's probably
> time to implement scaling in the global timer driver.

IIRC, the person submitting the driver for the arm_gt said something
like that those days: https://lkml.org/lkml/2013/5/8/250
No clue what the current status of that is today though.

	Sören