From: mchehab@s-opensource.com (Mauro Carvalho Chehab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 15/17] media: st_rc: Don't stay on an IRQ handler forever
Date: Fri, 13 Apr 2018 06:06:46 -0300 [thread overview]
Message-ID: <20180413060646.25b8a19d@vento.lan> (raw)
In-Reply-To: <20180412222132.z7g5enhin2uodbk7@gofer.mess.org>
Hi Sean,
Em Thu, 12 Apr 2018 23:21:32 +0100
Sean Young <sean@mess.org> escreveu:
> On Thu, Apr 12, 2018 at 11:24:07AM -0400, Mauro Carvalho Chehab wrote:
> > As warned by smatch:
> > drivers/media/rc/st_rc.c:110 st_rc_rx_interrupt() warn: this loop depends on readl() succeeding
> >
> > If something goes wrong at readl(), the logic will stay there
> > inside an IRQ code forever. This is not the nicest thing to
> > do :-)
> >
> > So, add a timeout there, preventing staying inside the IRQ
> > for more than 10ms.
>
> If we knew how large the fifo was, then we could limit the loop to that many
> iterations (maybe a few extra in case IR arrives while we a reading, but
> IR is much slower than a cpu executing this loop of course).
IR is slower, but this code is called at IRQ time, e. g. when the
controller already received the IR data. Also, it reads directly
via a memory mapped register, with should be fast. I suspect that
10ms is a lot more time than what would be required to go though
all the FIFO data.
>
> Patrice is something you could help with?
>
> Thanks
>
> Sean
>
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> > ---
> > drivers/media/rc/st_rc.c | 16 ++++++++++------
> > 1 file changed, 10 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/media/rc/st_rc.c b/drivers/media/rc/st_rc.c
> > index d2efd7b2c3bc..c855b177103c 100644
> > --- a/drivers/media/rc/st_rc.c
> > +++ b/drivers/media/rc/st_rc.c
> > @@ -96,19 +96,24 @@ static void st_rc_send_lirc_timeout(struct rc_dev *rdev)
> >
> > static irqreturn_t st_rc_rx_interrupt(int irq, void *data)
> > {
> > + unsigned long timeout;
> > unsigned int symbol, mark = 0;
> > struct st_rc_device *dev = data;
> > int last_symbol = 0;
> > - u32 status;
> > + u32 status, int_status;
> > DEFINE_IR_RAW_EVENT(ev);
> >
> > if (dev->irq_wake)
> > pm_wakeup_event(dev->dev, 0);
> >
> > - status = readl(dev->rx_base + IRB_RX_STATUS);
> > + /* FIXME: is 10ms good enough ? */
> > + timeout = jiffies + msecs_to_jiffies(10);
> > + do {
> > + status = readl(dev->rx_base + IRB_RX_STATUS);
> > + if (!(status & (IRB_FIFO_NOT_EMPTY | IRB_OVERFLOW)))
> > + break;
> >
> > - while (status & (IRB_FIFO_NOT_EMPTY | IRB_OVERFLOW)) {
> > - u32 int_status = readl(dev->rx_base + IRB_RX_INT_STATUS);
> > + int_status = readl(dev->rx_base + IRB_RX_INT_STATUS);
> > if (unlikely(int_status & IRB_RX_OVERRUN_INT)) {
> > /* discard the entire collection in case of errors! */
> > ir_raw_event_reset(dev->rdev);
> > @@ -148,8 +153,7 @@ static irqreturn_t st_rc_rx_interrupt(int irq, void *data)
> >
> > }
> > last_symbol = 0;
> > - status = readl(dev->rx_base + IRB_RX_STATUS);
> > - }
> > + } while (time_is_after_jiffies(timeout));
> >
> > writel(IRB_RX_INTS, dev->rx_base + IRB_RX_INT_CLEAR);
> >
> > --
> > 2.14.3
Thanks,
Mauro
next prev parent reply other threads:[~2018-04-13 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d20ab7176b2af82d6b679211edb5f151629d4033.1523546545.git.mchehab@s-opensource.com>
2018-04-12 15:24 ` [PATCH 15/17] media: st_rc: Don't stay on an IRQ handler forever Mauro Carvalho Chehab
2018-04-12 22:21 ` Sean Young
2018-04-13 7:32 ` Patrice CHOTARD
2018-04-13 9:06 ` Mauro Carvalho Chehab [this message]
2018-04-13 9:40 ` Sean Young
2018-04-13 10:00 ` Mauro Carvalho Chehab
2018-04-13 13:20 ` Sean Young
2018-04-13 14:08 ` Mauro Carvalho Chehab
2018-04-13 8:03 ` Patrice CHOTARD
2018-04-13 9:15 ` Mason
2018-04-13 9:25 ` Mauro Carvalho Chehab
2018-04-13 9:36 ` Mason
2018-04-13 9:52 ` Mauro Carvalho Chehab
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=20180413060646.25b8a19d@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).