From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Tao Ren <taoren@fb.com>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Cc: openbmc@lists.ozlabs.org, cov@fb.com, tfang@fb.com,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] clocksource/drivers/fttmr010: fix set_next_event handler
Date: Thu, 20 Sep 2018 01:16:32 +0200 [thread overview]
Message-ID: <bb452948-0a9e-140d-57d5-85c1732fca86@linaro.org> (raw)
In-Reply-To: <20180919221331.2511558-1-taoren@fb.com>
On 20/09/2018 00:13, Tao Ren wrote:
> Currently, the aspeed MATCH1 register is updated to <current_count -
> cycles> in set_next_event handler, with the assumption that COUNT
> register value is preserved when the timer is disabled and it continues
> decrementing after the timer is enabled. But the assumption is wrong:
> RELOAD register is loaded into COUNT register when the aspeed timer is
> enabled, which means the next event may be delayed because timer
> interrupt won't be generated until <0xFFFFFFFF - current_count +
> cycles>.
>
> The problem can be fixed by updating RELOAD register to <cycles>, and
> COUNT register will be re-loaded when the timer is enabled and interrupt
> is generated when COUNT register overflows.
>
> The test result on Facebook Backpack-CMM BMC hardware (AST2500) shows
> the issue is fixed: without the patch, usleep(100) suspends the process
> for several milliseconds (and sometimes even over 40 milliseconds);
> after applying the fix, usleep(100) takes averagely 240 microseconds to
> return under the same workload level.
>
> Signed-off-by: Tao Ren <taoren@fb.com>
Linus, any comments ?
> ---
> drivers/clocksource/timer-fttmr010.c | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/clocksource/timer-fttmr010.c b/drivers/clocksource/timer-fttmr010.c
> index c020038ebfab..cf93f6419b51 100644
> --- a/drivers/clocksource/timer-fttmr010.c
> +++ b/drivers/clocksource/timer-fttmr010.c
> @@ -130,13 +130,17 @@ static int fttmr010_timer_set_next_event(unsigned long cycles,
> cr &= ~fttmr010->t1_enable_val;
> writel(cr, fttmr010->base + TIMER_CR);
>
> - /* Setup the match register forward/backward in time */
> - cr = readl(fttmr010->base + TIMER1_COUNT);
> - if (fttmr010->count_down)
> - cr -= cycles;
> - else
> - cr += cycles;
> - writel(cr, fttmr010->base + TIMER1_MATCH1);
> + if (fttmr010->count_down) {
> + /*
> + * ASPEED Timer Controller will load TIMER1_LOAD register
> + * into TIMER1_COUNT register when the timer is re-enabled.
> + */
> + writel(cycles, fttmr010->base + TIMER1_LOAD);
> + } else {
> + /* Setup the match register forward in time */
> + cr = readl(fttmr010->base + TIMER1_COUNT);
> + writel(cr + cycles, fttmr010->base + TIMER1_MATCH1);
> + }
>
> /* Start */
> cr = readl(fttmr010->base + TIMER_CR);
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-09-19 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 22:13 Tao Ren
2018-09-19 23:16 ` Daniel Lezcano [this message]
2018-09-20 15:45 ` Linus Walleij
2018-09-20 21:09 ` Tao Ren
2018-09-21 3:32 ` Joel Stanley
2018-09-21 6:22 ` Lei YU
2018-09-21 18:11 ` Tao Ren
2018-09-21 18:11 ` Tao Ren
2018-09-24 23:20 ` Joel Stanley
2018-09-25 0:40 ` Tao Ren
2018-09-25 17:13 ` Sai Dasari
2018-09-25 19:16 ` Linus Walleij
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=bb452948-0a9e-140d-57d5-85c1732fca86@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=cov@fb.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
--cc=tfang@fb.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
all inboxes | Powered by JetHome®