linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentine <valentine.barshak@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.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] gpio: rcar: Fix level interrupt handling
Date: Fri, 29 Nov 2013 19:15:58 +0400	[thread overview]
Message-ID: <5298AFAE.2050802@cogentembedded.com> (raw)
In-Reply-To: <2847875.sxPRWEJTjc@avalon>

On 11/29/2013 07:00 PM, Laurent Pinchart wrote:
> Hi Valentine,

Hi Laurent,

>
> Thank you for the patch.
>
> On Friday 29 November 2013 17:32:20 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.
>>
>> Workaround the issue by dropping level interrupts from the pending
>> mask once the interrupt is handled. If the IRQ is not cleared by the
>> handler, it will be invoked again when the interrupt is re-enabled.
>
> Isn't it an issue common to all IRQ chip drivers that should be handled by the
> IRQ core ?

No, it isn't.

> When using level-triggered interrupts with threaded IRQ handlers,
> the core should disable the interrupt and re-enable it after executing the
> threaded handler.

The problem is not in disabling/re-enabling interrupts.
Even when the interrupt is disabled, the corresponding INTDT bit is not cleared.
Thus, the "while" loop never ends if a level interrupt happens since its bit is
always set in the "pending" mask.
In this case we never start deferred interrupt service routine, and never de-assert it.

The patch fixes this issue by dropping the IRQ bit from the "pending" mask
once the IRQ is handled at low-level.

>
>> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
>> ---
>>   drivers/gpio/gpio-rcar.c | 10 ++++++++--
>>   1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-rcar.c b/drivers/gpio/gpio-rcar.c
>> index d3f15ae..918a1de 100644
>> --- a/drivers/gpio/gpio-rcar.c
>> +++ b/drivers/gpio/gpio-rcar.c
>> @@ -166,12 +166,18 @@ static int gpio_rcar_irq_set_type(struct irq_data *d,
>> unsigned int type) static irqreturn_t gpio_rcar_irq_handler(int irq, void
>> *dev_id)
>>   {
>>   	struct gpio_rcar_priv *p = dev_id;
>> -	u32 pending;
>> +	u32 pending, mask = 0;
>>   	unsigned int offset, irqs_handled = 0;
>>
>> -	while ((pending = gpio_rcar_read(p, INTDT))) {
>> +	/*
>> +	 * Level interrupts cannot be cleared in the INTDT,
>> +	 * so we just drop them from the pending mask when
>> +	 * the interrupt is handled.
>> +	 */
>> +	while ((pending = gpio_rcar_read(p, INTDT) & ~mask)) {
>>   		offset = __ffs(pending);
>>   		gpio_rcar_write(p, INTCLR, BIT(offset));
>> +		mask |= BIT(offset) & ~gpio_rcar_read(p, EDGLEVEL);
>>   		generic_handle_irq(irq_find_mapping(p->irq_domain, offset));
>>   		irqs_handled++;
>>   	}

Thanks,
Val.

  reply	other threads:[~2013-11-29 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 13:32 [PATCH] gpio: rcar: Fix level interrupt handling Valentine Barshak
2013-11-29 15:00 ` Laurent Pinchart
2013-11-29 15:15   ` Valentine [this message]
2013-11-29 15:39     ` Laurent Pinchart
2013-11-29 17:36       ` Valentine
2013-11-29 18:06         ` Laurent Pinchart
2013-11-29 18:26           ` Valentine
2013-11-29 19:22             ` Laurent Pinchart
2013-11-29 19:42               ` Valentine

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=5298AFAE.2050802@cogentembedded.com \
    --to=valentine.barshak@cogentembedded.com \
    --cc=horms@verge.net.au \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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).