From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ladislav Michl <ladis@linux-mips.org>
Subject: Re: [RESEND PATCH] gpio: omap: Fix lost edge interrupts
Date: Sat, 7 Oct 2017 19:34:14 -0700 [thread overview]
Message-ID: <fe58a38c-6fa7-793d-ffd8-427f25c26770@oracle.com> (raw)
In-Reply-To: <CACRpkdYj1+_J+-EN6QQOJzWzXNB_3N6hPPfa1sqzERZb8gsdLw@mail.gmail.com>
On 10/7/17 4:18 AM, Linus Walleij wrote:
> On Tue, Oct 3, 2017 at 6:17 PM, Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>
>> Now acking of edge irqs happens the following way:
>> - omap_gpio_irq_handler
>> - "isr" = read irq status
>> - omap_clear_gpio_irqbank(bank, isr_saved & ~level_mask);
>> ^ clear edge status, so irq can be accepted
>> - loop while "isr"
>> generic_handle_irq()
>> - handle_edge_irq()
>> - desc->irq_data.chip->irq_ack(&desc->irq_data);
>> - omap_gpio_ack_irq()
>> it might be that at this moment edge IRQ was triggered again and it will be
>> cleared and IRQ will be lost.
>>
>> Use handle_simple_irq and clear edge interrupts early without disabling them in
>> omap_gpio_irq_handler to avoid loosing interrupts.
>>
>> [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__marc.info_-3Fl-3Dlinux-2Domap-26m-3D149004465313534-26w-3D2&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=XBn1JQGPwR8CsE7xpP3wPlG6DQU7qw8ym65xieNZ4hY&m=GC9UD4RPcq1Ss-JanXn4japAFhT1w4RZlq9WqDLSw_o&s=smHFYjIN3O5THK4qP413bHMnr8PaWUv4xyUbbTwXHk4&e=
This link doesn't need to be part of the changelog.
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
>
> Patch applied for fixes.
>
> I guess it is the right thing to do?
>
> Other maintainers need to tell me if I should hold it back.
>
Am fine with it after Grygorii's reasoning.
Regards,
Santosh
prev parent reply other threads:[~2017-10-08 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 16:17 Grygorii Strashko
2017-10-03 16:41 ` Santosh Shilimkar
2017-10-03 16:52 ` Grygorii Strashko
2017-10-03 17:22 ` Ladislav Michl
2017-10-04 15:48 ` Tony Lindgren
2017-10-03 18:15 ` Santosh Shilimkar
2017-10-07 11:18 ` Linus Walleij
2017-10-08 2:34 ` santosh.shilimkar [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=fe58a38c-6fa7-793d-ffd8-427f25c26770@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=grygorii.strashko@ti.com \
--cc=ladis@linux-mips.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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®