From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Mark Asselstine <mark.asselstine@windriver•com>
Cc: Russell King - ARM Linux <linux@arm•linux.org.uk>,
openezx-devel@lists•openezx.org, sameo@linux•intel.com,
haojian.zhuang@marvell•com,
Grant Likely <grant.likely@secretlab•ca>,
linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] ARM:mfd: fix ezx-pcap build failure
Date: Fri, 27 Apr 2012 19:02:35 +0100 [thread overview]
Message-ID: <20120427180235.GA19778@sirena.org.uk> (raw)
In-Reply-To: <2732324.Os5djSkuuZ@yow-masselst-d1>
On Fri, Apr 27, 2012 at 11:28:28AM -0400, Mark Asselstine wrote:
> On April 26, 2012 22:52:58 Russell King - ARM Linux wrote:
> > What is the effect when the supplied IRQ does not have a mapping to a
> > GPIO - or it _does_ by way of a badly coded irq_to_gpio() function
> > but that GPIO is not the correct one.
> > There is no prevention against endlessly looping, so it could cause a
> > system lockup.
> Unfortunately the commit [b1148fd4 mfd: fix pcap irq bottom handler
> ] which modified things to loop as long as the interrupt is asserted didn't
> supply much information regarding the behavior they were trying to achieve/fix
> nor what would be the consequence of bailing earlier.
The usual reason for this pattern is to simulate level triggered IRQs on
an edge triggered interrupt controller.
next prev parent reply other threads:[~2012-04-27 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 15:02 [PATCH] ARM:mfd: fix ezx-pcap build failure Mark Asselstine
2012-04-26 21:52 ` Russell King - ARM Linux
2012-04-26 22:04 ` Mark Brown
2012-04-27 15:28 ` Mark Asselstine
2012-04-27 18:02 ` Mark Brown [this message]
2012-04-30 17:26 ` Mark Asselstine
2012-04-27 16:09 ` Grant Likely
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=20120427180235.GA19778@sirena.org.uk \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=haojian.zhuang@marvell$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=mark.asselstine@windriver$(echo .)com \
--cc=openezx-devel@lists$(echo .)openezx.org \
--cc=sameo@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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