From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] IRQ-related changes
Date: Tue, 4 Jan 2011 11:39:24 +0200 [thread overview]
Message-ID: <1294133966-20279-1-git-send-email-balbi@ti.com> (raw)
Hi,
The following two patches are enabling SPARSE_IRQ
numbering scheme on OMAP. I lightly tested on a pandaboard
and seems to be working fine so far:
# cat /proc/interrupts
CPU0 CPU1
39: 1 0 GIC TWL6030-PIH
44: 1758 0 GIC DMA
69: 7615 0 GIC gp timer
88: 195 0 GIC i2c_omap
89: 0 0 GIC i2c_omap
93: 0 0 GIC i2c_omap
94: 0 0 GIC i2c_omap
102: 0 0 GIC serial idle
104: 0 0 GIC serial idle
105: 0 0 GIC serial idle
106: 743 0 GIC serial idle, OMAP UART2
115: 2356 0 GIC mmc0
160: 0 0 GPIO mmc0
376: 0 0 twl6030 twl4030_pwrbutton
379: 0 0 twl6030 rtc0
IPI: 1111 9537
LOC: 0 0
Err: 0
The first patch just removes the direct access to irq_desc
array and converts it to irq_to_desc(). Second patch simply
selects HAVE_GENERIC_HARDIRQS and HAVE_SPARSE_IRQ. I boot
tested with and without enabling:
-> General setup
-> IRQ subsystem
-> SPARSE_IRQ
and both kernels boot fine.
Felipe Balbi (2):
arm: omap: gpio: don't access irq_desc array directly
arm: omap: select HAVE_SPARSE_IRQ
arch/arm/Kconfig | 2 ++
arch/arm/plat-omap/gpio.c | 10 +++++++---
2 files changed, 9 insertions(+), 3 deletions(-)
--
1.7.3.4.598.g85356
next reply other threads:[~2011-01-04 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 9:39 Felipe Balbi [this message]
2011-01-04 9:39 ` [PATCH 1/2] arm: omap: gpio: don't access irq_desc array directly Felipe Balbi
2011-01-04 9:39 ` [PATCH 2/2] arm: omap: select HAVE_SPARSE_IRQ Felipe Balbi
2011-01-04 9:54 ` Russell King - ARM Linux
2011-01-04 9:55 ` Russell King - ARM Linux
2011-01-04 10:34 ` Felipe Balbi
2011-01-04 11:42 ` Russell King - ARM Linux
2011-01-04 11:52 ` Felipe Balbi
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=1294133966-20279-1-git-send-email-balbi@ti.com \
--to=balbi@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).