linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Nicolai Stange <nicstange@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH] microblaze/timer: set ->min_delta_ticks and ->max_delta_ticks
Date: Mon, 29 May 2017 11:03:27 +0200	[thread overview]
Message-ID: <b47fb594-d413-0398-116c-f8b0f70ecc97@monstr.eu> (raw)
In-Reply-To: <20170330194528.7047-1-nicstange@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2937 bytes --]

On 30.3.2017 21:45, 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 microblaze arch's clockevent driver 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 this
> driver.
> 
> Signed-off-by: Nicolai Stange <nicstange@gmail.com>
> ---
> 
> Notes:
>     This prerequisite patch is part of a larger effort to feed NTP
>     corrections into the clockevent devices' frequencies and thus
>     avoiding their notion of time to diverge from the system's
>     one. If you're interested, the current state of the whole series
>     can be found at [1].
>     
>     If you haven't got any objections and these prerequisites get
>     merged by 4.12 everywhere, I'll proceed with the remainder of
>     this series in 4.13.
>     
>     Applicable to next-20170324 as well as to John' Stultz tree [2].
>     
>     [1]
>       git://nicst.de/linux.git cev-freq-adj.v10.fortglx-4.12-time
>       https://nicst.de/git/?p=linux.git;a=shortlog;h=refs/heads/cev-freq-adj.v10.fortglx-4.12-time
>     
>     [2]
>       https://git.linaro.org/people/john.stultz/linux.git fortglx/4.12/time
> 
>  arch/microblaze/kernel/timer.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/microblaze/kernel/timer.c b/arch/microblaze/kernel/timer.c
> index 999066192715..545ccd46edb3 100644
> --- a/arch/microblaze/kernel/timer.c
> +++ b/arch/microblaze/kernel/timer.c
> @@ -178,8 +178,10 @@ static __init int xilinx_clockevent_init(void)
>  				clockevent_xilinx_timer.shift);
>  	clockevent_xilinx_timer.max_delta_ns =
>  		clockevent_delta2ns((u32)~0, &clockevent_xilinx_timer);
> +	clockevent_xilinx_timer.max_delta_ticks = (u32)~0;
>  	clockevent_xilinx_timer.min_delta_ns =
>  		clockevent_delta2ns(1, &clockevent_xilinx_timer);
> +	clockevent_xilinx_timer.min_delta_ticks = 1;
>  	clockevent_xilinx_timer.cpumask = cpumask_of(0);
>  	clockevents_register_device(&clockevent_xilinx_timer);
>  
> 

Applied as
microblaze: Set ->min_delta_ticks and ->max_delta_ticks for timer

With Daniel's ACK.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2017-05-29  9:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 13:44 [PATCH] x86/apic/timer: set ->min_delta_ticks and ->max_delta_ticks Nicolai Stange
2017-03-30 19:39 ` [PATCH] avr32/time: " Nicolai Stange
2017-04-03  6:42   ` Hans-Christian Noren Egtvedt
2017-03-30 19:41 ` [PATCH] blackfin: time-ts: " Nicolai Stange
2017-03-30 19:42 ` [PATCH] c6x/timer64: " Nicolai Stange
2017-03-30 19:43 ` [PATCH] hexagon/time: " Nicolai Stange
2017-04-03 15:49   ` Richard Kuo
2017-03-30 19:44 ` [PATCH] m68k/coldfire/pit: " Nicolai Stange
2017-03-31  1:10   ` Greg Ungerer
2017-03-30 19:45 ` [PATCH] microblaze/timer: " Nicolai Stange
2017-04-07 13:14   ` Daniel Lezcano
2017-04-16  2:47     ` Nicolai Stange
2017-04-16  9:46       ` Daniel Lezcano
2017-05-29  9:03   ` Michal Simek [this message]
2017-03-30 19:47 ` [PATCH] MIPS: clockevent drivers: " Nicolai Stange
2017-04-12 20:10   ` Ralf Baechle
2017-03-30 19:48 ` [PATCH] mn10300/cevt-mn10300: " Nicolai Stange
2017-03-30 19:53 ` [PATCH] powerpc/time: " Nicolai Stange
2017-03-31  3:03   ` Michael Ellerman
2017-03-30 19:54 ` [PATCH] s390/time: " Nicolai Stange
2017-03-30 19:55 ` [PATCH] score/time: " Nicolai Stange
2017-03-30 19:56 ` [PATCH] sparc/time: " Nicolai Stange
2017-04-01 19:18   ` David Miller
2017-03-30 19:57 ` [PATCH] tile/time: " Nicolai Stange
2017-03-30 19:59 ` [PATCH] um/time: " Nicolai Stange
2017-03-30 20:01 ` [PATCH] unicore32/time: " Nicolai Stange
2017-03-31  1:59   ` Xuetao Guan
2017-03-30 20:03 ` [PATCH] x86/lguest/timer: " Nicolai Stange
2017-04-02  1:35   ` Rusty Russell
2017-03-30 20:04 ` [PATCH] x86/uv/time: " Nicolai Stange
2017-03-30 20:06 ` [PATCH] x86/xen/time: " Nicolai Stange
2017-03-30 22:59   ` Boris Ostrovsky
2017-04-06  9:11   ` Juergen Gross
2017-04-11  5:09   ` Juergen Gross
2017-03-30 20:07 ` [PATCH] clockevents/drivers/dw_apb: " Nicolai Stange
2017-04-07 13:20   ` Daniel Lezcano
2017-03-30 20:08 ` [PATCH] clockevents/drivers/metag: " Nicolai Stange
2017-04-07 13:20   ` Daniel Lezcano
2017-03-30 20:08 ` [PATCH] x86/numachip timer: " Nicolai Stange
2017-04-07 13:21   ` Daniel Lezcano
2017-03-30 20:09 ` [PATCH] clockevents/drivers/sh_cmt: " Nicolai Stange
2017-04-07 13:22   ` Daniel Lezcano
2017-03-30 20:10 ` [PATCH] clockevents/drivers/atlas7: " Nicolai Stange
2017-04-07 13:23   ` Daniel Lezcano

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=b47fb594-d413-0398-116c-f8b0f70ecc97@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=daniel.lezcano@linaro.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicstange@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).