Re: clocksource with changing frequency?

[John Stultz <john.stultz@linaro.org>]

On 06/20/2013 05:01 PM, Sören Brinkmann wrote:
> Hi all,
>
> I have a question/problem with a clocksource whose input frequency can
> change.

That behavior isn't supported by the clocksource core. We expect 
frequency changing clocksources to be detected and disqualified (as we 
do w/ freq changing TSCs on older laptops).


> On Zynq we use the cadece_ttc timer as clocksource. Its input clock is
> tightly coupled to the CPU clock. I.e. it changes when cpufreq scales
> the CPU clocks.
> To compensate this, I added a clock notifier doing this on a frequency
> change:
> 	clocksource_unregister(&ttccs->cs);
> 	clocksource_register_hz(&ttccs->cs, ndata->new_rate / PRESCALE);

This will definitely have problems if this is the only high-res capable 
clocksource.

> This just seems not to be the most elegant way, a heavy weight operation
> and results in a couple of locking errors in combination with
> suspend/hotplug.
>
> Is there a sane solution for such a case? E.g. for clockevent devices
> there is a 'clockevents_update_freq()' to adjust to changing
> frequencies.

If you want to experiment with things, my suggestion would be to try to 
fake a constant frequency clocksource in the clocksource driver(tracking 
the change intervals and multiplying them up as needed). However, I 
worry the quality of timekeeping won't be very good, as any latency in 
the detection of the freq change will cause time error.


> I assume the sanest solution is an external oscillator as clock input,
> but I think our platforms don't provide that :(

I suspect your best bet, if there really is no other consistent clocks, 
would be to disable highres timers and use the jiffies clocksource for 
timekeeping, allowing you to change cpufreq to save power or increase 
performance as you need. This will result in coarse timekeeping and 
larger timer latency. But the only other approach is to fix the cpu freq 
so the clocksource freq doesn't change (at the cost of cpu performance 
or battery life - both of which I suspect are bigger issues then coarse 
time).

thanks
-john