From: Sricharan R <r.sricharan@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: tony@atomide.com, santosh.shilimkar@ti.com, nm@ti.com,
rnayak@ti.com, linux@arm.linux.org.uk, r.sricharan@ti.com,
tglx@linutronix.de, jason@lakedaemon.net, joe@perches.com
Subject: [PATCH V4 0/2] arm: dts: dra7: add crossbar dt support
Date: Thu, 26 Jun 2014 12:55:29 +0530 [thread overview]
Message-ID: <1403767532-19290-1-git-send-email-r.sricharan@ti.com> (raw)
This series introduces DT support for crossbar device and
changes dra7 peripherals to use crossbar number instead of irq.
This depends on below driver fixes and cleanup series.
http://marc.info/?l=linux-omap&m=140376708127157&w=2
[V2] Rebased on 3.15 mainline.
[V3] Added ti,irqs-skip property and ti,irqs-safe-map property to
crossbar dt node.
[V4] Introduced macros MAX_SOURCES and DIRECT_IRQ
R Sricharan (2):
arm: dts: dra7: add routable-irqs property for gic node
arm: dts: dra7: add crossbar device binding
arch/arm/boot/dts/dra7.dtsi | 139 +++++++++++++++++++++++++------------------
1 file changed, 81 insertions(+), 58 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-06-26 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 7:25 Sricharan R [this message]
2014-06-26 7:25 ` [PATCH V4 1/2] arm: dts: dra7: add routable-irqs property for gic node Sricharan R
2014-06-26 7:25 ` [PATCH V4 2/2] arm: dts: dra7: add crossbar device binding Sricharan R
[not found] ` <1403767532-19290-3-git-send-email-r.sricharan-l0cyMroinI0@public.gmane.org>
2014-06-26 7:44 ` Tony Lindgren
2014-06-26 8:32 ` Sricharan R
2014-06-26 10:26 ` Tony Lindgren
2014-07-09 15:44 ` Tony Lindgren
2014-07-10 5:58 ` Lokesh Vutla
2014-07-10 6:19 ` 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=1403767532-19290-1-git-send-email-r.sricharan@ti.com \
--to=r.sricharan@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nm@ti.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/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).