From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mfd: update irq handler in max8925
Date: Wed, 27 Jan 2010 01:02:09 -0500 [thread overview]
Message-ID: <771cded01001262202s45f28206hd9740279a275898e@mail.gmail.com> (raw)
In-Reply-To: <20100126120602.GP15759@rakim.wolfsonmicro.main>
On Tue, Jan 26, 2010 at 7:06 AM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Jan 26, 2010 at 06:31:56AM -0500, Haojian Zhuang wrote:
>> On Tue, Jan 26, 2010 at 6:28 AM, Mark Brown
>
>> > and call handle_nested_irq() unconditionally, genirq should generate a
>> > warning and mask the IRQ if it's not handled which is what your code
>> > here is doing.
>
>> Actually I can't find genirq reports any warning. I only find my code
>> reports warning message.
>
> There's a threashold before the warning starts displaying, IIRC. ?In any
> case, the handling of spurious IRQs isn't really an IRQ controller
> driver issue - it's a generic issue that affects all interrupt
> controllers.
>
Thanks a lot.
Updated patch is attached in mail. Now the modification is in below.
1. remove clear_irq() & clear_tsc_irq().
2. remove warning message in max8925_irq().
Best Regards
Haojian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-mfd-update-irq-handler-in-max8925.patch
Type: text/x-patch
Size: 28146 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100127/645e8444/attachment-0001.bin>
next prev parent reply other threads:[~2010-01-27 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 11:08 [PATCH 2/4] mfd: update irq handler in max8925 Haojian Zhuang
2010-01-25 11:59 ` Mark Brown
2010-01-26 3:12 ` Haojian Zhuang
2010-01-26 3:14 ` Haojian Zhuang
2010-01-26 11:28 ` Mark Brown
2010-01-26 11:31 ` Haojian Zhuang
2010-01-26 12:06 ` Mark Brown
2010-01-27 6:02 ` Haojian Zhuang [this message]
2010-01-27 11:12 ` Mark Brown
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=771cded01001262202s45f28206hd9740279a275898e@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).