From: Nicolai Stange <nicstange@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Nicolai Stange <nicstange@gmail.com>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v6 01/23] clocksource: sh_cmt: compute rate before registration again
Date: Sat, 10 Sep 2016 21:11:34 +0200 [thread overview]
Message-ID: <87k2ejd0yh.fsf@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1609101416420.32361@nanos> (Thomas Gleixner's message of "Sat, 10 Sep 2016 14:56:47 +0200 (CEST)")
Thomas Gleixner <tglx@linutronix.de> writes:
> On Fri, 9 Sep 2016, Nicolai Stange wrote:
>> @@ -339,17 +339,14 @@ static int sh_cmt_enable(struct sh_cmt_channel *ch, unsigned long *rate)
>> sh_cmt_start_stop_ch(ch, 0);
>>
>> /* configure channel, periodic mode and maximum timeout */
>> - if (ch->cmt->info->width == 16) {
>> - *rate = clk_get_rate(ch->cmt->clk) / 512;
>> + if (ch->cmt->info->width == 16)
>> sh_cmt_write_cmcsr(ch, SH_CMT16_CMCSR_CMIE |
>> SH_CMT16_CMCSR_CKS512);
>> - } else {
>> - *rate = clk_get_rate(ch->cmt->clk) / 8;
>> + else
>> sh_cmt_write_cmcsr(ch, SH_CMT32_CMCSR_CMM |
>> SH_CMT32_CMCSR_CMTOUT_IE |
>> SH_CMT32_CMCSR_CMR_IRQ |
>> SH_CMT32_CMCSR_CKS_RCLK8);
>> - }
>
> Removing the braces here is just wrong.
Completely convinced, will redo.
>> @@ -824,6 +810,12 @@ static int sh_cmt_register_clockevent(struct sh_cmt_channel *ch,
>> ced->suspend = sh_cmt_clock_event_suspend;
>> ced->resume = sh_cmt_clock_event_resume;
>>
>> + /* TODO: calculate good shift from rate and counter bit width */
>> + ced->shift = 32;
>> + ced->mult = div_sc(ch->cmt->rate, NSEC_PER_SEC, ced->shift);
>
>
> Errm. clockevents_calc_mult_shift()
Or even clockevents_config_and_register()?
The reason why I left this mult/shift initialization as is (it has only
been moved from sh_cmt_clock_event_start() by this patch) is that I was
unsure about why this conversion hadn't been done before. That TODO
comment seems to imply that a shift value as calculated by
clockevents_config() isn't always the perfect choice...
However, do you want me to
a.) simply change this patch to use clockevents_config_and_register(),
b.) add a separate patch to this series doing this cleanup,
c.) send such a patch on its own
d.) or leave this initalization as is?
Thanks,
Nicolai Stange
next prev parent reply other threads:[~2016-09-10 19:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 20:00 [RFC v6 00/23] adapt clockevents frequencies to mono clock Nicolai Stange
2016-09-09 20:00 ` [RFC v6 01/23] clocksource: sh_cmt: compute rate before registration again Nicolai Stange
2016-09-10 12:56 ` Thomas Gleixner
2016-09-10 18:51 ` Joe Perches
2016-09-10 19:11 ` Nicolai Stange [this message]
2016-09-09 20:00 ` [RFC v6 02/23] clocksource: sh_tmu: " Nicolai Stange
2016-09-09 20:00 ` [RFC v6 03/23] clocksource: em_sti: split clock prepare and enable steps Nicolai Stange
2016-09-09 20:00 ` [RFC v6 04/23] clocksource: em_sti: compute rate before registration Nicolai Stange
2016-09-09 20:00 ` [RFC v6 05/23] clocksource: h8300_timer8: don't reset rate in ->set_state_oneshot() Nicolai Stange
2016-09-09 20:00 ` [RFC v6 06/23] clockevents: make clockevents_config() static Nicolai Stange
2016-09-09 20:00 ` [RFC v6 07/23] many clockevent drivers: set ->min_delta_ticks and ->max_delta_ticks Nicolai Stange
2016-09-09 20:00 ` [RFC v6 08/23] arch/s390/kernel/time: " Nicolai Stange
2016-09-09 20:00 ` [RFC v6 09/23] arch/x86/platform/uv/uv_time: " Nicolai Stange
2016-09-09 20:00 ` [RFC v6 10/23] arch/tile/kernel/time: " Nicolai Stange
2016-09-09 20:00 ` [RFC v6 11/23] clockevents: always initialize ->min_delta_ns and ->max_delta_ns Nicolai Stange
2016-09-09 20:00 ` [RFC v6 12/23] many clockevent drivers: don't set " Nicolai Stange
2016-09-09 20:00 ` [RFC v6 13/23] clockevents: introduce CLOCK_EVT_FEAT_NO_ADJUST flag Nicolai Stange
2016-09-09 20:00 ` [RFC v6 14/23] clockevents: decouple ->max_delta_ns from ->max_delta_ticks Nicolai Stange
2016-09-09 20:00 ` [RFC v6 15/23] clockevents: do comparison of delta against minimum in terms of cycles Nicolai Stange
2016-09-09 20:18 ` [RFC v6 16/23] clockevents: clockevents_program_min_delta(): don't set ->next_event Nicolai Stange
2016-09-09 20:18 ` [RFC v6 17/23] clockevents: use ->min_delta_ticks_adjusted to program minimum delta Nicolai Stange
2016-09-09 20:18 ` [RFC v6 18/23] clockevents: min delta increment: calculate min_delta_ns from ticks Nicolai Stange
2016-09-09 20:18 ` [RFC v6 19/23] timer_list: print_tickdevice(): calculate ->min_delta_ns dynamically Nicolai Stange
2016-09-09 20:18 ` [RFC v6 20/23] clockevents: purge ->min_delta_ns Nicolai Stange
2016-09-09 20:18 ` [RFC v6 21/23] clockevents: initial support for mono to raw time conversion Nicolai Stange
2016-09-09 20:18 ` [RFC v6 22/23] clockevents: make setting of ->mult and ->mult_adjusted atomic Nicolai Stange
2016-09-09 20:18 ` [RFC v6 23/23] timekeeping: inform clockevents about freq adjustments 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=87k2ejd0yh.fsf@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