From: Fengquan Chen <fengquan.chen@mediatek.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
<dehui.sun@mediatek.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] clocksource/drivers/timer-mediatek: optimize systimer irq clear flow on Mediatek Socs
Date: Wed, 21 Apr 2021 18:07:52 +0800 [thread overview]
Message-ID: <1618999672.25707.13.camel@mhfsdcap03> (raw)
In-Reply-To: <c91e9afc-8b04-f35b-bcf9-1fcf9a6f425f@linaro.org>
On Mon, 2021-03-22 at 11:10 +0100, Daniel Lezcano wrote:
> On 02/03/2021 08:28, Fengquan Chen wrote:
> > 1)ensure systimer is enabled before clear and disable interrupt, which only
> > for systimer in Mediatek Socs.
> >
> > 2)clear any pending timer-irq when shutdown to keep suspend flow clean,
> > when use systimer as tick-broadcast timer
> >
> > Change-Id: Ia3eda83324af2fdaf5cbb3569a9bf020a11f8009
>
> Remove the above.
>
> Add a Fixes tag.
Thanks for review, has been fixed in V4:
https://patchwork.kernel.org/project/linux-mediatek/patch/1617960162-1988-2-git-send-email-Fengquan.Chen@mediatek.com/
>
> > Signed-off-by: Fengquan Chen <fengquan.chen@mediatek.com>
> > ---
> > drivers/clocksource/timer-mediatek.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/clocksource/timer-mediatek.c b/drivers/clocksource/timer-mediatek.c
> > index 9318edc..9f1f095dc 100644
> > --- a/drivers/clocksource/timer-mediatek.c
> > +++ b/drivers/clocksource/timer-mediatek.c
> > @@ -75,6 +75,7 @@
> > static void mtk_syst_ack_irq(struct timer_of *to)
> > {
> > /* Clear and disable interrupt */
> > + writel(SYST_CON_EN, SYST_CON_REG(to));
>
> SYST_CON_EN is set below, why do you have to do it before?
>
> Is that a hw bug ?
>
> It is confusing what the description of the SYST_CON_EN says:
>
> /*
> * SYST_CON_EN: Clock enable. Shall be set to
> * - Start timer countdown.
> * - Allow timeout ticks being updated.
> * - Allow changing interrupt functions.
>
> What means "interrupt functions" ?
>
> Does writing writel(SYST_CON_EN, SYST_CON_REG(to)) before
> SYST_CON_IRQ_CLR allows to clear the interrupt flag?
>
> Can you explain how the timer works regarding this part?
>
> It sounds to me a bit strange.
>
> *
> * SYST_CON_IRQ_EN: Set to allow interrupt.
> *
> * SYST_CON_IRQ_CLR: Set to clear interrupt.
> */
>
Thanks for review, descriptions about
SYST_CON_IRQ_CLR/SYST_CON_EN/SYST_CON_IRQ_EN have been updated in v4.
And for systimer, there's a hw limitation that before clearing pending
irqs, we must enable timer first. so we added a SYST_CON_EN write before
SYST_CON_IRQ_CLR write to ensure irq clear successfully.
Also, we cannot only write SYST_CON_IRQ_CLR without SYST_CON_EN bit,
because EN bit is also timer clock enable bit.
this is a hardward design limitation but not a bug.
>
> > writel(SYST_CON_IRQ_CLR | SYST_CON_EN, SYST_CON_REG(to));
> > }
> >
> > @@ -111,6 +112,9 @@ static int mtk_syst_clkevt_next_event(unsigned long ticks,
> >
> > static int mtk_syst_clkevt_shutdown(struct clock_event_device *clkevt)
> > {
> > + /* Clear any irq */
> > + mtk_syst_ack_irq(to_timer_of(clkevt));
> > +
> > /* Disable timer */
> > writel(0, SYST_CON_REG(to_timer_of(clkevt)));
> >
> >
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-21 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 7:28 [PATCH] clocksource/drivers/timer-mediatek: optimize systimer irq clear flow on Mediatek Socs Fengquan Chen
2021-03-02 7:28 ` Fengquan Chen
2021-03-22 10:10 ` Daniel Lezcano
2021-04-21 10:07 ` Fengquan Chen [this message]
2021-03-23 0:48 ` Evan Benn
2021-04-21 10:17 ` Fengquan Chen
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=1618999672.25707.13.camel@mhfsdcap03 \
--to=fengquan.chen@mediatek.com \
--cc=daniel.lezcano@linaro.org \
--cc=dehui.sun@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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