From: Rob Herring <robherring2@gmail.com>
To: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Cc: grant.likely@secretlab.ca, marc.zyngier@arm.com,
thomas.abraham@linaro.org, jamie@jamieiles.com, b-cousson@ti.com,
shawn.guo@linaro.org, Rob Herring <rob.herring@calxeda.com>
Subject: [PATCH 0/3] GIC OF bindings
Date: Fri, 30 Sep 2011 14:27:57 -0500 [thread overview]
Message-ID: <1317410880-24828-1-git-send-email-robherring2@gmail.com> (raw)
From: Rob Herring <rob.herring@calxeda.com>
Another round of GIC devicetree support.
This moves the tracking of the starting hwirq number into the irq domain
code. Doing this makes hwirq == GIC interrupt ID and simplifies the GIC
code removing irq_offset.
The full series is available here. This includes Russell's devel-stable and
for-next branches and Nico's vmalloc branch:
git://git.jdl.com/software/linux-3.0.git gic-v2
Tested on highbank and Realview 11MPCore qemu (2 GICs).
Rob
Rob Herring (3):
irq: support domains with non-zero hwirq base
ARM: gic: add irq_domain support
ARM: gic: add OF based initialization
Documentation/devicetree/bindings/arm/gic.txt | 55 ++++++++++
arch/arm/common/Kconfig | 1 +
arch/arm/common/gic.c | 142 +++++++++++++++++++------
arch/arm/include/asm/hardware/gic.h | 5 +-
include/linux/irqdomain.h | 16 +++-
kernel/irq/irqdomain.c | 12 +-
6 files changed, 189 insertions(+), 42 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/gic.txt
--
1.7.5.4
next reply other threads:[~2011-09-30 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 19:27 Rob Herring [this message]
[not found] ` <1317410880-24828-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-30 19:27 ` [PATCH 1/3] irq: support domains with non-zero hwirq base Rob Herring
2011-10-04 23:39 ` Grant Likely
2011-09-30 19:27 ` [PATCH 2/3] ARM: gic: add irq_domain support Rob Herring
2011-10-04 23:41 ` Grant Likely
2011-09-30 19:28 ` [PATCH 3/3] ARM: gic: add OF based initialization Rob Herring
2011-10-04 23:44 ` Grant Likely
2011-10-04 16:15 ` [PATCH 0/3] GIC OF bindings Rob Herring
2011-10-08 14:04 ` Thomas Abraham
-- strict thread matches above, loose matches on Subject: below --
2011-09-20 20:24 Rob Herring
2011-09-21 2:49 ` David Miller
2011-09-21 4:14 ` Grant Likely
[not found] ` <CACxGe6t7Mdr+w+aGFPM2-FEAQaYHuG8Za9dybLgMo-5-whLyNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-21 4:58 ` Mitch Bradley
2011-09-21 5:21 ` David Miller
[not found] ` <20110921.012158.2252182592946972727.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-09-21 7:11 ` Mitch Bradley
[not found] ` <20110920.224910.1996429830782124690.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-09-21 5:16 ` Segher Boessenkool
[not found] ` <1316550244-3655-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-21 9:43 ` Shawn Guo
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=1317410880-24828-1-git-send-email-robherring2@gmail.com \
--to=robherring2@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=thomas.abraham@linaro.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).