From: "Cousson, Benoit" <b-cousson-l0cyMroinI0@public.gmane.org>
To: tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
linux-omap <linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: [GIT PULL] ARM: OMAP2+: Interrupt controllers adaptation to DT
Date: Mon, 9 Jan 2012 14:57:17 +0100 [thread overview]
Message-ID: <4F0AF23D.9040103@ti.com> (raw)
Hi Tony,
If this is not too late, could you please pull the OMAP interrupt controllers adaptation to device tree?
This series is based on your lo/dt branch to get the DTS and board cleanup.
Thanks,
Benoit
The following changes since commit 40c0591f0a349ec074357e05c6ab1a3bc951807c:
Benoit Cousson (1):
ARM: OMAP2+: kconfig: Enable devicetree by default for OMAP2+ systems
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git for_3.3/dt_irq
Benoit Cousson (5):
arm/dts: OMAP4: Update DTS file with new GIC bindings
ARM: OMAP2/3: intc: Add irqdomain support
ARM: OMAP2/3: intc: Add DT support for TI interrupt controller
arm/dts: OMAP3: Add interrupt-controller bindings for INTC
ARM: OMAP2+: board-generic: Use of_irq_init API
.../devicetree/bindings/arm/omap/intc.txt | 27 +++++++++++
arch/arm/boot/dts/omap3.dtsi | 6 ++-
arch/arm/boot/dts/omap4.dtsi | 2 +-
arch/arm/mach-omap2/board-generic.c | 30 +++++++------
arch/arm/mach-omap2/common.h | 10 ++++
arch/arm/mach-omap2/irq.c | 48 ++++++++++++++++++--
6 files changed, 102 insertions(+), 21 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/omap/intc.txt
reply other threads:[~2012-01-09 13:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F0AF23D.9040103@ti.com \
--to=b-cousson-l0cymroini0@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).