From: Sricharan R <r.sricharan@ti.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, linus.walleij@linaro.org,
linux@arm.linux.org.uk, tony@atomide.com, rnayak@ti.com,
marc.zyngier@arm.com, grant.likely@linaro.org,
mark.rutland@arm.com, tglx@linutronix.de, galak@codeaurora.org,
santosh.shilimkar@ti.com, nm@ti.com, bcousson@baylibre.com,
robherring2@gmail.com
Cc: Sricharan R <r.sricharan@ti.com>
Subject: [PATCH V5 3/3] arm: dts: dra7: Add routable-irqs property for gic node
Date: Tue, 6 May 2014 19:26:19 +0530 [thread overview]
Message-ID: <1399384579-25620-4-git-send-email-r.sricharan@ti.com> (raw)
In-Reply-To: <1399384579-25620-1-git-send-email-r.sricharan@ti.com>
There is a IRQ crossbar device in the soc, which maps the
irq requests from the peripherals to the mpu interrupt
controller's inputs. The gic provides the support for such
IPs in the form of routable-irqs. So adding the property
here to gic node.
Cc: Benoit Cousson <bcousson@baylibre.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Signed-off-by: Sricharan R <r.sricharan@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
---
[V5] Rebased and corrected routable irqs from 160 to 192
arch/arm/boot/dts/dra7.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index 52e4bd0..cec826f 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++ b/arch/arm/boot/dts/dra7.dtsi
@@ -72,6 +72,7 @@
compatible = "arm,cortex-a15-gic";
interrupt-controller;
#interrupt-cells = <3>;
+ arm,routable-irqs = <192>;
reg = <0x48211000 0x1000>,
<0x48212000 0x1000>,
<0x48214000 0x2000>,
--
1.7.9.5
next prev parent reply other threads:[~2014-05-06 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 13:56 [PATCH V5 0/3] arm: dts: dra7: Updates for adding crossbar device Sricharan R
2014-05-06 13:56 ` [PATCH V5 1/3] arm: dts: dra7: Add crossbar device binding Sricharan R
2014-05-06 19:40 ` Felipe Balbi
2014-05-06 19:46 ` Nishanth Menon
2014-05-06 19:58 ` Darren Etheridge
2014-05-06 20:07 ` Darren Etheridge
2014-05-06 13:56 ` [PATCH V5 2/3] arm: dts: dra7: Replace peripheral interrupt numbers with crossbar inputs Sricharan R
[not found] ` <1399384579-25620-3-git-send-email-r.sricharan-l0cyMroinI0@public.gmane.org>
2014-05-06 14:41 ` Tony Lindgren
2014-05-06 13:56 ` Sricharan R [this message]
2014-05-06 21:45 ` [PATCH V5 0/3] arm: dts: dra7: Updates for adding crossbar device Darren Etheridge
2014-05-07 4:40 ` Sricharan R
2014-05-08 8:13 ` Archit Taneja
2014-05-07 12:06 ` Roger Quadros
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=1399384579-25620-4-git-send-email-r.sricharan@ti.com \
--to=r.sricharan@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rnayak@ti.com \
--cc=robherring2@gmail.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).