From: Grant Likely <grant.likely@secretlab.ca>
To: devicetree-discuss@lists.ozlabs.org, tglx@linutronix.de,
linux@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] Simple irq_domain implementation
Date: Tue, 26 Jul 2011 03:36:36 -0600 [thread overview]
Message-ID: <20110726093141.12508.48108.stgit@ponder> (raw)
In the interest of getting this infrastructure merged, I've reworked the
basic irq_domain patch to implement only what is required for ARM device
tree board support. That means it doesn't affect any architectures other
than ARM, and I'll send follow-on patches targeted at v3.2 to migrate
MIPS, Microblaze, x86 embedded and PowerPC over to it.
Thomas, can you please take a look? I've got devicetree board support
queued up and ready to be merged but for this infrastructure.
g.
---
Grant Likely (2):
irq: add irq_domain translation infrastructure
dt/irq: add irq_domain_generate_simple() helper
arch/arm/Kconfig | 1
arch/arm/include/asm/prom.h | 5 -
arch/arm/kernel/devtree.c | 14 ---
include/linux/irq.h | 6 +
include/linux/irqdomain.h | 93 ++++++++++++++++++++++
include/linux/of_irq.h | 4 +
kernel/irq/Kconfig | 4 +
kernel/irq/Makefile | 1
kernel/irq/irqdomain.c | 180 +++++++++++++++++++++++++++++++++++++++++++
9 files changed, 289 insertions(+), 19 deletions(-)
create mode 100644 include/linux/irqdomain.h
create mode 100644 kernel/irq/irqdomain.c
--
Signature
next reply other threads:[~2011-07-26 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 9:36 Grant Likely [this message]
2011-07-26 9:36 ` [PATCH v3 1/2] irq: add irq_domain translation infrastructure Grant Likely
2011-07-26 9:40 ` Grant Likely
2011-07-26 9:36 ` [PATCH v3 2/2] dt/irq: add irq_domain_generate_simple() helper Grant Likely
2011-07-28 9:31 ` [PATCH v3 0/2] Simple irq_domain implementation Thomas Gleixner
2011-07-28 22:20 ` 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=20110726093141.12508.48108.stgit@ponder \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tglx@linutronix.de \
/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).