From: balajitk@ti.com (Balaji T K)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: OMAP2+: GPMC set dummy irq chip
Date: Thu, 17 Mar 2011 21:30:05 +0530 [thread overview]
Message-ID: <1300377606-16616-3-git-send-email-balajitk@ti.com> (raw)
In-Reply-To: <1300377606-16616-1-git-send-email-balajitk@ti.com>
Resolve following warning messages in boot when irq chip is not set
[ 0.429229] Trying to install interrupt handler for IRQ402
[ 0.429229] Trying to install interrupt handler for IRQ403
[ 0.429229] Trying to install interrupt handler for IRQ404
[ 0.429260] Trying to install interrupt handler for IRQ405
[ 0.429260] Trying to install interrupt handler for IRQ406
[ 0.429260] Trying to install interrupt handler for IRQ407
[ 0.429290] Trying to install interrupt handler for IRQ408
Signed-off-by: Balaji T K <balajitk@ti.com>
---
arch/arm/mach-omap2/gpmc.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 6741743..d81d536 100644
--- a/arch/arm/mach-omap2/gpmc.c
+++ b/arch/arm/mach-omap2/gpmc.c
@@ -739,7 +739,8 @@ static int __init gpmc_init(void)
/* initalize the irq_chained */
irq = OMAP_GPMC_IRQ_BASE;
for (cs = 0; cs < GPMC_CS_NUM; cs++) {
- set_irq_handler(irq, handle_simple_irq);
+ set_irq_chip_and_handler(irq, &dummy_irq_chip,
+ handle_simple_irq);
set_irq_flags(irq, IRQF_VALID);
irq++;
}
--
1.7.0.4
next prev parent reply other threads:[~2011-03-17 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 16:00 [PATCH 0/3] ARM: OMAP2+: gpmc warning fixes Balaji T K
2011-03-17 16:00 ` [PATCH 1/3] ARM: OMAP2+: correct GPMC IRQ Balaji T K
2011-03-17 16:00 ` Balaji T K [this message]
2011-03-17 16:00 ` [PATCH 3/3] ARM: OMAP4: correct GPMC IRQ number Balaji T K
2011-03-18 23:43 ` [PATCH 0/3] ARM: OMAP2+: gpmc warning fixes Tony Lindgren
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=1300377606-16616-3-git-send-email-balajitk@ti.com \
--to=balajitk@ti.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).