From: Nicolai Stange <nicstange@gmail.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Magnus Damm <damm@opensource.se>,
linux-kernel@vger.kernel.org,
uclinux-h8-devel@lists.sourceforge.jp,
Nicolai Stange <nicstange@gmail.com>
Subject: [PATCH 0/6] adapt clockevents frequencies to mono clock: prerequisites 1
Date: Mon, 6 Feb 2017 22:11:58 +0100 [thread overview]
Message-ID: <20170206211204.25251-1-nicstange@gmail.com> (raw)
Hi,
in order to facilitate review, this (sub-)series has been split off from
a larger effort to be found at [1].
The overall goal is to adjust the clockevent devices' frequencies to the
NTP controlled monotonic time.
As a prerequisite, ced drivers must not alter the rate by any means other
than clockevents_update_freq() after registration.
The four drivers touched here are the only ones currently violating this.
What's more, altering the ced rates after registration isn't really
necessary for any of them. This series cleans this up.
John signaled willingness to deal with all of this and thus, it would be
best if all the patches herein would get picked by him only...
Based on v4.10-rc2.
Thanks,
Nicolai
[1] Current version:
git://nicst.de/linux.git cev-freq-adj.v9.4.10-rc2
http://nicst.de/git/?p=linux.git;a=shortlog;h=refs/heads/cev-freq-adj.v9.4.10-rc2
Slightly outdated LKML submission:
http://lkml.kernel.org/r/20161119160055.12491-1-nicstange@gmail.com
Nicolai Stange (6):
clocksource: sh_cmt: compute rate before registration again
clocksource: sh_tmu: compute rate before registration again
clocksource: em_sti: split clock prepare and enable steps
clocksource: em_sti: compute rate before registration
clocksource: h8300_timer8: don't reset rate in ->set_state_oneshot()
clockevents: make clockevents_config() static
drivers/clocksource/em_sti.c | 46 +++++++++++++++++++++-----------------
drivers/clocksource/h8300_timer8.c | 8 -------
drivers/clocksource/sh_cmt.c | 45 ++++++++++++++++++++-----------------
drivers/clocksource/sh_tmu.c | 26 ++++++++++-----------
include/linux/clockchips.h | 1 -
kernel/time/clockevents.c | 2 +-
6 files changed, 65 insertions(+), 63 deletions(-)
--
2.11.1
next reply other threads:[~2017-02-06 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 21:11 Nicolai Stange [this message]
2017-02-06 21:11 ` [PATCH 1/6] clocksource: sh_cmt: compute rate before registration again Nicolai Stange
2017-02-14 4:35 ` John Stultz
2017-02-06 21:12 ` [PATCH 2/6] clocksource: sh_tmu: " Nicolai Stange
2017-02-06 21:12 ` [PATCH 3/6] clocksource: em_sti: split clock prepare and enable steps Nicolai Stange
2017-02-06 21:12 ` [PATCH 4/6] clocksource: em_sti: compute rate before registration Nicolai Stange
2017-02-06 21:12 ` [PATCH 5/6] clocksource: h8300_timer8: don't reset rate in ->set_state_oneshot() Nicolai Stange
2017-02-06 21:12 ` [PATCH 6/6] clockevents: make clockevents_config() static Nicolai Stange
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=20170206211204.25251-1-nicstange@gmail.com \
--to=nicstange@gmail.com \
--cc=damm@opensource.se \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®