linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Valentine <valentine.barshak@cogentembedded.com>
Cc: linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH V2] gpio: rcar: Fix level interrupt handling
Date: Tue, 10 Dec 2013 01:39:49 +0000	[thread overview]
Message-ID: <2145029.4685npYTTl@avalon> (raw)
In-Reply-To: <52A6190C.200@cogentembedded.com>

Hi Valentine,

On Monday 09 December 2013 23:25:00 Valentine wrote:
> On 11/29/2013 10:04 PM, Valentine Barshak wrote:
> > According to the manual, if a port is set for level detection using
> > the corresponding bit in the edge/level select register and an external
> > level interrupt signal is asserted, the corresponding bit in INTDT
> > does not use the FF to hold the input.
> > Thus, writing 1 to the corresponding bits in INTCLR cannot clear the
> > corresponding bits in the INTDT register. Instead, when an external
> > input signal is stopped, the corresponding bit in INTDT is cleared
> > automatically.
> > 
> > Since the INTDT bit cannot be cleared for the level interrupts until
> > the interrupt signal is stopped, we end up with the infinite loop
> > when using deferred (threaded) IRQ handling.
> > 
> > Since a deferred interrupt is disabled by the low-level handler and
> > re-enabled only when the deferred handler is completed, Fix the issue
> > by dropping disabled interrupts from the pending mask as suggested by
> > Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> > Changes in V2:
> > * Drop disabled interrupts from pending mask altogether instead of
> > 
> >    dropping level interrupts one by one once they get handled.
> > 
> > Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> > ---
> > 
> >   drivers/gpio/gpio-rcar.c | 3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpio/gpio-rcar.c b/drivers/gpio/gpio-rcar.c
> > index d3f15ae..fd2d827 100644
> > --- a/drivers/gpio/gpio-rcar.c
> > +++ b/drivers/gpio/gpio-rcar.c
> > @@ -169,7 +169,8 @@ static irqreturn_t gpio_rcar_irq_handler(int irq, void
> > *dev_id)
> >   	u32 pending;
> >   	unsigned int offset, irqs_handled = 0;
> > 
> > -	while ((pending = gpio_rcar_read(p, INTDT))) {
> > +	while ((pending = gpio_rcar_read(p, INTDT) &
> > +			  gpio_rcar_read(p, INTMSK))) {
> >   		offset = __ffs(pending);
> >   		gpio_rcar_write(p, INTCLR, BIT(offset));
> >   		generic_handle_irq(irq_find_mapping(p->irq_domain, offset));
> 
> Laurent, Magnus,
> do you have any concerns about fixing the level IRQ's as proposed here?
> 
> I'm more inclined to re-read the registers instead of caching the pending
> value pending = gpio_rcar_read(p, INTDT) & gpio_rcar_read(p, INTMSK)); and
> dropping bits inside the while loop
>   pending &= ~BIT(offset);
> 
> I think this could help to catch new interrupts while processing previous
> ones. It also makes minimum change to the original logic.
> 
> Please let me know if you think it's not good enough and the cached
> "pending" value (or any other approach) should be used instead.

I would have used the caching approach myself as it makes the loop simpler and 
any external interrupt occuring after the registers are read would be 
processed by a new interrupt handler call, but your approach should work fine 
as well, so I have no reason to complain.

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-12-10  1:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 18:04 [PATCH V2] gpio: rcar: Fix level interrupt handling Valentine Barshak
2013-12-09 19:25 ` Valentine
2013-12-10  1:39   ` Laurent Pinchart [this message]
2013-12-11  9:44   ` Magnus Damm
2013-12-12 19:54 ` Linus Walleij
2013-12-13 12:31   ` Magnus Damm

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=2145029.4685npYTTl@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=horms@verge.net.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=valentine.barshak@cogentembedded.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 NNTP newsgroup(s).