[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170412201028.GA31873@linux-mips.org>
Date: Wed, 12 Apr 2017 22:10:28 +0200
From: Ralf Baechle <ralf@...ux-mips.org>
To: Nicolai Stange <nicstange@...il.com>
Cc: Keguang Zhang <keguang.zhang@...il.com>,
John Crispin <john@...ozen.org>,
John Stultz <john.stultz@...aro.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
James Hogan <james.hogan@...tec.com>,
Andrea Gelmini <andrea.gelmini@...ma.net>,
Huacai Chen <chenhc@...ote.com>, linux-mips@...ux-mips.org
Subject: Re: [PATCH] MIPS: clockevent drivers: set ->min_delta_ticks and
->max_delta_ticks
On Thu, Mar 30, 2017 at 09:47:32PM +0200, 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 MIPS arch's clockevent drivers 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 these
> drivers.
>
> Signed-off-by: Nicolai Stange <nicstange@...il.com>
Acked-by: Ralf Baechle <ralf@...ux-mips.org>
Feel free to push this to Linus.
Ralf
Powered by blists - more mailing lists