x86/numachip timer: Set ->min_delta_ticks and ->max_delta_ticks
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 numachip 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. Cc: Ingo Molnar <mingo@redhat.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Daniel Lezcano <daniel.lezcano@linaro.org> Cc: Richard Cochran <richardcochran@gmail.com> Cc: Prarit Bhargava <prarit@redhat.com> Cc: Stephen Boyd <sboyd@codeaurora.org> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org> Signed-off-by: Nicolai Stange <nicstange@gmail.com> Signed-off-by: John Stultz <john.stultz@linaro.org>
This commit is contained in:
parent
c7438ba113
commit
6cf57ae8cd
|
@ -51,7 +51,9 @@ static struct clock_event_device numachip2_clockevent = {
|
|||
.mult = 1,
|
||||
.shift = 0,
|
||||
.min_delta_ns = 1250,
|
||||
.min_delta_ticks = 1250,
|
||||
.max_delta_ns = LONG_MAX,
|
||||
.max_delta_ticks = LONG_MAX,
|
||||
};
|
||||
|
||||
static void numachip_timer_interrupt(void)
|
||||
|
|
Loading…
Reference in New Issue