From: Ralf Baechle <ralf@linux-mips.org>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Keguang Zhang <keguang.zhang@gmail.com>,
John Crispin <john@phrozen.org>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
James Hogan <james.hogan@imgtec.com>,
Andrea Gelmini <andrea.gelmini@gelma.net>,
Huacai Chen <chenhc@lemote.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: clockevent drivers: set ->min_delta_ticks and ->max_delta_ticks
Date: Wed, 12 Apr 2017 22:10:28 +0200 [thread overview]
Message-ID: <20170412201028.GA31873@linux-mips.org> (raw)
In-Reply-To: <20170330194732.7126-1-nicstange@gmail.com>
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@gmail.com>
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Feel free to push this to Linus.
Ralf
prev parent reply other threads:[~2017-04-12 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170326134403.16226-1-nicstange@gmail.com>
2017-03-30 19:47 ` [PATCH] MIPS: clockevent drivers: set ->min_delta_ticks and ->max_delta_ticks Nicolai Stange
2017-04-12 20:10 ` Ralf Baechle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170412201028.GA31873@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=andrea.gelmini@gelma.net \
--cc=chenhc@lemote.com \
--cc=james.hogan@imgtec.com \
--cc=john.stultz@linaro.org \
--cc=john@phrozen.org \
--cc=keguang.zhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=nicstange@gmail.com \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox