From: mtk15103 <hailong.fan@mediatek.com>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: Sean Wang <sean.wang@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>, <youlin.pei@mediatek.com>,
srv_heupstream <srv_heupstream@mediatek.com>,
Chen-Tsung Hsieh <chentsung@chromium.org>,
<gtk_pangao@mediatek.com>, Hanks Chen <hanks.chen@mediatek.com>,
Yong Wu <yong.wu@mediatek.com>, <zhengnan.chen@mediatek.com>
Subject: Re: [PATCH RESEND] pinctrl: mediatek: Fix trigger type setting follow for unexpected interrupt
Date: Fri, 22 Jan 2021 10:43:58 +0800 [thread overview]
Message-ID: <1611283438.2493.23.camel@mhfsdcap03> (raw)
In-Reply-To: <CANMq1KCXrEGrNrOwivrchXyawzKySVzQoxA1goYC-eh-auNFCA@mail.gmail.com>
On Thu, 2021-01-21 at 20:13 +0800, Nicolas Boichat wrote:
> On Thu, Jan 21, 2021 at 8:09 PM mtk15103 <hailong.fan@mediatek.com> wrote:
> >
> > On Thu, 2021-01-21 at 16:55 +0800, Nicolas Boichat wrote:
> > > On Thu, Jan 21, 2021 at 3:52 PM Hailong Fan <hailong.fan@mediatek.com> wrote:
> > > >
> > > > When flipping the polarity will be generated interrupt under certain
> > > > circumstances, but GPIO external signal has not changed.
> > > > Then, mask the interrupt before polarity setting, and clear the
> > > > unexpected interrupt after trigger type setting completed.
> > > >
> > > > Signed-off-by: Hailong Fan <hailong.fan@mediatek.com>
> > > > ---
> > > > Resend since some server reject.
> > > > ---
> > > > drivers/pinctrl/mediatek/mtk-eint.c | 13 +++++++++++--
> > > > 1 file changed, 11 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/pinctrl/mediatek/mtk-eint.c b/drivers/pinctrl/mediatek/mtk-eint.c
> > > > index 22736f60c16c..3acda6bb401e 100644
> > > > --- a/drivers/pinctrl/mediatek/mtk-eint.c
> > > > +++ b/drivers/pinctrl/mediatek/mtk-eint.c
> > > > @@ -157,6 +157,7 @@ static void mtk_eint_ack(struct irq_data *d)
> > > > static int mtk_eint_set_type(struct irq_data *d, unsigned int type)
> > > > {
> > > > struct mtk_eint *eint = irq_data_get_irq_chip_data(d);
> > > > + unsigned int unmask;
> > >
> > > bool?
> > Yes,thanks.
> > >
> > > > u32 mask = BIT(d->hwirq & 0x1f);
> > > > void __iomem *reg;
> > > >
> > > > @@ -173,6 +174,13 @@ static int mtk_eint_set_type(struct irq_data *d, unsigned int type)
> > > > else
> > > > eint->dual_edge[d->hwirq] = 0;
> > > >
> > > > + if (!mtk_eint_get_mask(eint, d->hwirq)) {
> > > > + mtk_eint_mask(d);
> > > > + unmask = 1;
> > > > + } else {
> > > > + unmask = 0;
> > > > + }
> > > > +
> > > > if (type & (IRQ_TYPE_LEVEL_LOW | IRQ_TYPE_EDGE_FALLING)) {
> > > > reg = mtk_eint_get_offset(eint, d->hwirq, eint->regs->pol_clr);
> > > > writel(mask, reg);
> > > > @@ -189,8 +197,9 @@ static int mtk_eint_set_type(struct irq_data *d, unsigned int type)
> > > > writel(mask, reg);
> > > > }
> > > >
> > > > - if (eint->dual_edge[d->hwirq])
> > > > - mtk_eint_flip_edge(eint, d->hwirq);
> > >
> > > Why are you dropping this? Aren't we at risk to miss the first edge
> > > after mtk_eint_set_type is called?
> > mtk_eint_unmask() will do it.
> > If unmask != 1, user need to call mtk_eint_unmask() to enable the
> > interrupt before use it, thanks.
>
> Makes sense, I just have one more worry:
> https://elixir.bootlin.com/linux/latest/source/drivers/pinctrl/mediatek/mtk-eint.c#L122
>
> mtk_eint_unmask unmasks the interrupt _before_ the edge is flipped,
> could this cause a spurious interrupt? On any unmask operation -- not
> just on mtk_eint_set_type (so this is technically another problem,
> that should be fixed as a separate patch)
This situation will not happen.
Spurious interrupt occur condition: edge irq polarity value is same with
input signal.
e.g.
Default value: GPIO input is high, trigger type is falling_edge.
User want modify trigger type is rising_edge under some certain
circumstances, it will generate spurious interrupt but external signal
maintain high.
So we need ack interrupt after trigger_type setting is completed.
mtk_eint_flip_edge is for dual_edge, the polarity setting based on
current gpio input signal:
if (input == high)
polarity = low; /* falling_edge */
else
polarity = high; /* rising_edge */
Then it's not cause a spurious interrupt.
> > > > + mtk_eint_ack(d);
> > > > + if (unmask == 1)
> > >
> > > Just `if (unmask)`
> > Yes,thanks.
> > > > + mtk_eint_unmask(d);
> > > >
> > > > return 0;
> > > > }
> > > > --
> > > > 2.18.0
> >
next prev parent reply other threads:[~2021-01-22 2:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 7:51 Hailong Fan
2021-01-21 8:55 ` Nicolas Boichat
2021-01-21 12:09 ` mtk15103
2021-01-21 12:13 ` Nicolas Boichat
2021-01-22 2:43 ` mtk15103 [this message]
2021-01-22 10:54 ` Nicolas Boichat
2021-01-25 3:16 ` mtk15103
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=1611283438.2493.23.camel@mhfsdcap03 \
--to=hailong.fan@mediatek.com \
--cc=chentsung@chromium.org \
--cc=drinkcat@chromium.org \
--cc=gtk_pangao@mediatek.com \
--cc=hanks.chen@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=yong.wu@mediatek.com \
--cc=youlin.pei@mediatek.com \
--cc=zhengnan.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
all inboxes | Powered by JetHome®