mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org,
	Nicolai Stange <nicstange@gmail.com>
Subject: [RFC v8 05/28] clocksource: h8300_timer8: don't reset rate in ->set_state_oneshot()
Date: Sat, 19 Nov 2016 17:00:32 +0100	[thread overview]
Message-ID: <20161119160055.12491-6-nicstange@gmail.com> (raw)
In-Reply-To: <20161119160055.12491-1-nicstange@gmail.com>

With the upcoming NTP correction related rate adjustments to be implemented
in the clockevents core, the latter needs to get informed about every rate
change of a clockevent device made after its registration.

Currently, h8300_timer8 violates this requirement in that it registers its
clockevent device with the correct rate, but resets its ->mult and ->rate
values in timer8_clock_event_start(), called from its ->set_state_oneshot()
function.

It seems like
  commit 4633f4cac85a ("clocksource/drivers/h8300: Cleanup startup and
                        remove module code."),
which introduced the rate initialization at registration, missed to remove
the manual setting of ->mult and ->shift from timer8_clock_event_start().

Purge the setting of ->mult, ->shift, ->min_delta_ns and ->max_delta_ns
from timer8_clock_event_start().

Signed-off-by: Nicolai Stange <nicstange@gmail.com>
---

Notes:
    Compile-only tested on ARCH=h8300.

 drivers/clocksource/h8300_timer8.c | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/drivers/clocksource/h8300_timer8.c b/drivers/clocksource/h8300_timer8.c
index 546bb18..804c489 100644
--- a/drivers/clocksource/h8300_timer8.c
+++ b/drivers/clocksource/h8300_timer8.c
@@ -101,15 +101,7 @@ static inline struct timer8_priv *ced_to_priv(struct clock_event_device *ced)
 
 static void timer8_clock_event_start(struct timer8_priv *p, unsigned long delta)
 {
-	struct clock_event_device *ced = &p->ced;
-
 	timer8_start(p);
-
-	ced->shift = 32;
-	ced->mult = div_sc(p->rate, NSEC_PER_SEC, ced->shift);
-	ced->max_delta_ns = clockevent_delta2ns(0xffff, ced);
-	ced->min_delta_ns = clockevent_delta2ns(0x0001, ced);
-
 	timer8_set_next(p, delta);
 }
 
-- 
2.10.2

  parent reply	other threads:[~2016-11-19 16:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 16:00 [RFC v8 00/28] adapt clockevents frequencies to mono clock Nicolai Stange
2016-11-19 16:00 ` [RFC v8 01/28] clocksource: sh_cmt: compute rate before registration again Nicolai Stange
2016-11-19 16:00 ` [RFC v8 02/28] clocksource: sh_tmu: " Nicolai Stange
2016-11-19 16:00 ` [RFC v8 03/28] clocksource: em_sti: split clock prepare and enable steps Nicolai Stange
2016-11-19 16:00 ` [RFC v8 04/28] clocksource: em_sti: compute rate before registration Nicolai Stange
2016-11-19 16:00 ` Nicolai Stange [this message]
2016-11-19 16:00 ` [RFC v8 06/28] clockevents: make clockevents_config() static Nicolai Stange
2016-11-19 16:00 ` [RFC v8 07/28] many clockevent drivers: set ->min_delta_ticks and ->max_delta_ticks Nicolai Stange
2016-11-19 16:00 ` [RFC v8 08/28] arch/s390/kernel/time: " Nicolai Stange
2016-11-19 16:00 ` [RFC v8 09/28] arch/x86/platform/uv/uv_time: " Nicolai Stange
2016-11-19 16:00 ` [RFC v8 10/28] arch/tile/kernel/time: " Nicolai Stange
2016-11-19 16:00 ` [RFC v8 11/28] clockevents: always initialize ->min_delta_ns and ->max_delta_ns Nicolai Stange
2016-11-19 16:10 ` [RFC v8 12/28] many clockevent drivers: don't set " Nicolai Stange
2016-11-19 16:10 ` [RFC v8 13/28] clockevents: do comparison of delta against minimum in terms of cycles Nicolai Stange
2016-11-19 16:10 ` [RFC v8 14/28] clockevents: clockevents_program_min_delta(): don't set ->next_event Nicolai Stange
2016-11-19 16:10 ` [RFC v8 15/28] clockevents: use ->min_delta_ticks_adjusted to program minimum delta Nicolai Stange
2016-11-19 16:10 ` [RFC v8 16/28] clockevents: min delta increment: calculate min_delta_ns from ticks Nicolai Stange
2016-11-19 16:10 ` [RFC v8 17/28] timer_list: print_tickdevice(): calculate ->min_delta_ns dynamically Nicolai Stange
2016-11-19 16:10 ` [RFC v8 18/28] clockevents: purge ->min_delta_ns Nicolai Stange
2016-11-19 16:10 ` [RFC v8 19/28] clockevents: introduce CLOCK_EVT_FEAT_NO_ADJUST flag Nicolai Stange
2016-11-19 16:10 ` [RFC v8 20/28] clockevents: degrade ->min_delta_ticks to unsigned int Nicolai Stange
2016-11-19 16:10 ` [RFC v8 21/28] clockevents: pack ->state_use_accessors and ->features together Nicolai Stange
2016-11-19 16:10 ` [RFC v8 22/28] clockevents: decouple ->max_delta_ns from ->max_delta_ticks Nicolai Stange
2016-11-19 16:10 ` [RFC v8 23/28] clockevents: initial support for mono to raw time conversion Nicolai Stange
2016-11-19 16:10 ` [RFC v8 24/28] clockevents: make setting of ->mult and ->mult_adjusted atomic Nicolai Stange
2016-11-19 16:10 ` [RFC v8 25/28] timekeeping: inform clockevents about freq adjustments Nicolai Stange
2016-11-19 16:10 ` [RFC v8 26/28] clockevents: degrade ->retries to unsigned int Nicolai Stange
2016-11-19 16:10 ` [RFC v8 27/28] clockevents: optimize struct clock_event_device layout Nicolai Stange
2016-11-19 16:10 ` [RFC v8 28/28] clockevents: move non-adjustable devices to the tail of the list 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=20161119160055.12491-6-nicstange@gmail.com \
    --to=nicstange@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®