From: Evan Benn <evanbenn@chromium.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Evan Benn <evanbenn@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Alexey Klimov <alexey.klimov@linaro.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Thomas Gleixner <tglx@linutronix.de>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Fabien Parent <fparent@baylibre.com>
Subject: Re: [PATCH v2] drivers/clocksource/mediatek: Ack and disable interrupts on shutdown
Date: Tue, 6 Apr 2021 11:01:04 +1000 [thread overview]
Message-ID: <CAKz_xw1ZSuvqnBHDRVLAV3FZKuen0F9L+gjjP=Hedo6G74ow4w@mail.gmail.com> (raw)
In-Reply-To: <67eed9a2-2b97-be1b-3290-948da662ea65@linaro.org>
On Sat, Apr 3, 2021 at 1:15 AM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
> >
> > That said I am happy to upload that version if people think it is better.
>
> IMO, it is not in the normal flow to disable/enable the interrupts.
Hi Daniel, no problem.
I will upload the suspend/resume version. Please note the similar fix
to the other timer in this file:
https://patchwork.kernel.org/project/linux-mediatek/patch/1614670085-26229-2-git-send-email-Fengquan.Chen@mediatek.com/
Is doing the same ack/disable.
>
> Does this timer belong to an always-on power domain ?
>
I'm not sure sorry, the datasheet does not seem to say. Maybe mediatek
can answer.
prev parent reply other threads:[~2021-04-06 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 1:35 [PATCH v2] drivers/clocksource/mediatek: Ack and disable interrupts on shutdown Evan Benn
2021-03-25 8:07 ` Daniel Lezcano
2021-03-27 1:31 ` Evan Benn
2021-04-02 14:15 ` Daniel Lezcano
2021-04-06 1:01 ` Evan Benn [this message]
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='CAKz_xw1ZSuvqnBHDRVLAV3FZKuen0F9L+gjjP=Hedo6G74ow4w@mail.gmail.com' \
--to=evanbenn@chromium.org \
--cc=Julia.Lawall@lip6.fr \
--cc=alexey.klimov@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=evanbenn@gmail.com \
--cc=fparent@baylibre.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=stanley.chu@mediatek.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=yingjoe.chen@mediatek.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 read-only IMAP folder(s) and NNTP newsgroup(s).