Re: [PATCH] avr32/time: set ->min_delta_ticks and ->max_delta_ticks

From: Hans-Christian Noren Egtvedt
Date: Mon Apr 03 2017 - 02:42:48 EST


Around Thu 30 Mar 2017 21:39:33 +0200 or thereabout, 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 change dynamically and thus, the
> ratio of ns to ticks ceases to stay invariant.
>
> Make the avr32 arch's clockevent driver initialize these fields properly.
>
> This patch alone doesn't introduce any change in functionality as the
> clockevents core still looks exclusively at the (untouched) ->min_delta_ns
> and ->max_delta_ns. As soon as this has changed, a followup patch will
> purge the initialization of ->min_delta_ns and ->max_delta_ns from this
> driver.
>
> Signed-off-by: Nicolai Stange <nicstange@xxxxxxxxx>

-1

Please do not spend time on AVR32 architecture. It will be removed in the
next merge window.

<snipp diff>

--
Best regards,
Hans-Christian Noren Egtvedt