From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: Kevin Hickey <khickey@rmicorp.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [PATCH] Alchemy: fix edge irq handling
Date: Wed, 21 Jan 2009 07:48:56 +0100 [thread overview]
Message-ID: <20090121064856.GA27020@roarinelk.homelinux.net> (raw)
In-Reply-To: <1232498838.3678.17.camel@kh-d820>
Hi Kevin,
> Have you actually seen this happen (outside of inducing it manually)? I
> have some concern that by doing this we may either miss interrupts on
> devices that send a lot (by design) or miss a design bug in a system
> because we are masking out some interrupts. I know that system
> stability is important, but I don't like hiding problems.
Yes, in a customer project. A simple pushbutton which connects a pulled-up
gpio pin to ground. Push it, instant hang (handler called over and over
again) when it is not debounced. With a single edge and a much lower
edge-frequency it obviously works fine (see timer).
(And, handle_edge_irq() _does_ call mask_ack() after all).
Best regards,
Manuel Lauss
> =Kevin
>
> On Tue, 2009-01-20 at 11:03 +0100, Manuel Lauss wrote:
> > Introduce separate mack_ack callbacks which really do shut up the
> > edge-triggered irqs when called. Without this change, high-frequency
> > edge interrupts can result in an endless irq storm, hanging the system.
> >
> > This can be easily triggered for example by setting an irq to falling
> > edge type and manually connecting the associated pin to ground.
> >
next prev parent reply other threads:[~2009-01-21 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 10:03 [PATCH] Alchemy: fix edge irq handling Manuel Lauss
2009-01-21 0:47 ` Kevin Hickey
2009-01-21 6:48 ` Manuel Lauss [this message]
2009-01-27 2:18 ` Kevin Hickey
2009-01-27 6:20 ` Manuel Lauss
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=20090121064856.GA27020@roarinelk.homelinux.net \
--to=mano@roarinelk.homelinux.net \
--cc=khickey@rmicorp.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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