From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-omap@vger.kernel.org>, <linux-gpio@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: Tue, 3 Oct 2017 11:52:01 -0500 [thread overview]
Message-ID: <81906eda-58ac-38e3-bc0a-8ead2b6aa8df@ti.com> (raw)
In-Reply-To: <7b8f3c6a-0f4b-98ed-3887-91a01ed6cdbb@oracle.com>
Hi Santosh,
On 10/03/2017 11:41 AM, Santosh Shilimkar wrote:
>
>
> On 10/3/2017 9:17 AM, Grygorii Strashko 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=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=XBn1JQGPwR8CsE7xpP3wPlG6DQU7qw8ym65xieNZ4hY&m=-JZAaXlsRBFYNqtZ-2KOemoupa4pL7ka9D3wKn6hX9o&s=c-1XuQUl3_1uYedoNhmY70xCO3fAftWB7cmFxgyC3j4&e=
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
>> ---
>> Resend with proper cc list.
>>
> This was one of the concern I was thinking when GPIO IRQ conversion
> was done. Grygorii since you did that conversion, can you please
> check since I see now that the irq code is becoming increasingly
> complex.
This patch was developed in coop with Ladislav and he intensively tested it and
this patch actually simplifies IRQ handling. Also, OMAP driver parts which
this patch touches are ancient.
--
regards,
-grygorii
next prev parent reply other threads:[~2017-10-03 16:52 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 [this message]
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
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=81906eda-58ac-38e3-bc0a-8ead2b6aa8df@ti.com \
--to=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=santosh.shilimkar@oracle.com \
--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®