From: "Remy Bohmer" <linux@bohmer.net>
To: "Kevin Hilman" <khilman@mvista.com>
Cc: "Daniel Walker" <dwalker@mvista.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Steven Rostedt" <rostedt@goodmis.org>,
"ARM Linux Mailing List"
<linux-arm-kernel@lists.arm.linux.org.uk>,
RT <linux-rt-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever
Date: Wed, 28 Nov 2007 15:43:49 +0100 [thread overview]
Message-ID: <3efb10970711280643q50a91aeeoee2a28455e80cb8e@mail.gmail.com> (raw)
In-Reply-To: <87bq9fqpoi.fsf@vence.hilman.org>
Hello Kevin,
Just copied your mail to the list, maybe your solution is also worth looking at.
Remy
> I had a similar issue when using the chained GPIO interrupts on OMAP
> under PREEMPT_RT.
>
> I believe the chained handler itself is supposed to be doing the
> ack/unmask instead of the simple_handler.
>
> However, currently there is no way for the chained handler to know
> when the threaded handler has acutally run. So the way I fixed this
> was to have the simple handler call the chip->end hook so that the
> chained handler could do the ack/unmask after the threaded handler has
> actually run.
>
> I've been using this against the -rt patch since 2.6.21, and submitted
> and RFC a while back, but got no comments.
>
> This patch is against 2.6.24-rc2-rt1.
>
> Signed-off-by: Kevin Hilman <khilman@mvista.com>
>
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index b35d209..2f9e09e 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -661,6 +661,8 @@ static void thread_simple_irq(irq_desc_t *desc)
> note_interrupt(irq, desc, action_ret);
> }
> desc->status &= ~IRQ_INPROGRESS;
> + if (desc->chip->end)
> + desc->chip->end(irq);
> }
>
> /*
>
>
>
>
prev parent reply other threads:[~2007-11-28 14:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 13:31 Remy Bohmer
2007-11-26 13:45 ` Remy Bohmer
2007-11-27 15:11 ` Steven Rostedt
2007-11-27 15:25 ` Daniel Walker
2007-11-27 15:53 ` Daniel Walker
2007-11-28 14:38 ` Remy Bohmer
2007-11-28 15:36 ` Daniel Walker
2007-11-28 17:25 ` Russell King - ARM Linux
2007-11-28 19:04 ` Steven Rostedt
2007-11-28 20:05 ` Russell King - ARM Linux
2007-11-28 20:16 ` Steven Rostedt
2007-11-28 20:44 ` Daniel Walker
2007-11-28 21:13 ` Steven Rostedt
2007-11-28 23:03 ` Russell King - ARM Linux
2007-11-28 23:19 ` Daniel Walker
2007-11-29 9:04 ` Russell King - ARM Linux
2007-11-29 10:14 ` Remy Bohmer
2007-11-29 10:25 ` Russell King - ARM Linux
2007-11-29 11:27 ` Remy Bohmer
2007-11-29 13:36 ` Russell King - ARM Linux
2007-11-29 13:57 ` Steven Rostedt
2007-11-29 14:18 ` Remy Bohmer
2007-11-29 14:29 ` Russell King - ARM Linux
2007-11-29 15:33 ` Remy Bohmer
2007-11-29 16:20 ` Remy Bohmer
2007-11-29 16:30 ` Steven Rostedt
2007-11-30 21:44 ` Thomas Gleixner
2007-12-12 19:40 ` [PATCH RT] Revert Softdisable for simple irqs Steven Rostedt
2007-12-12 19:46 ` Russell King
2007-12-12 20:05 ` Remy Bohmer
2007-12-12 20:27 ` Steven Rostedt
2007-12-12 21:38 ` Remy Bohmer
[not found] ` <87bq9fqpoi.fsf@vence.hilman.org>
2007-11-28 14:43 ` Remy Bohmer [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=3efb10970711280643q50a91aeeoee2a28455e80cb8e@mail.gmail.com \
--to=linux@bohmer.net \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®