Re: [PATCH] m68k/coldfire/pit: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Greg Ungerer
Hi Nicolai, On 31/03/17 05:44, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to

Re: [PATCH] m68k/coldfire/pit: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Greg Ungerer
Hi Nicolai, On 31/03/17 05:44, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to

[PATCH] m68k/coldfire/pit: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Nicolai Stange
In preparation for making the clockevents core NTP correction aware, all clockevent device drivers must set ->min_delta_ticks and ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a clockevent device's rate is going to change dynamically and thus, the ratio of ns to ticks ceases to

[PATCH] m68k/coldfire/pit: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Nicolai Stange
In preparation for making the clockevents core NTP correction aware, all clockevent device drivers must set ->min_delta_ticks and ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a clockevent device's rate is going to change dynamically and thus, the ratio of ns to ticks ceases to