From: "Andrew F. Davis" <afd@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>,
Russell King <linux@armlinux.org.uk>, Suman Anna <s-anna@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, "Andrew F . Davis" <afd@ti.com>
Subject: [PATCH v2 2/3] ARM: dts: keystone-k2g: Add keystone IRQ controller node
Date: Tue, 9 Aug 2016 09:33:05 -0500 [thread overview]
Message-ID: <20160809143306.25028-3-afd@ti.com> (raw)
In-Reply-To: <20160809143306.25028-1-afd@ti.com>
Add the Keystone IRQ controller IP node on K2G SoC. This allows the
ARM CorePac core to receive interrupts from remote processor devices
(eg: DSP) on the SoC.
The IP is identical in functionality to that of the equivalent
nodes on existing K2 SoCs. The only difference is the ARM INTC
interrupt id/event number.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
---
arch/arm/boot/dts/keystone-k2g.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/keystone-k2g.dtsi b/arch/arm/boot/dts/keystone-k2g.dtsi
index fe17dc4..eccda9c 100644
--- a/arch/arm/boot/dts/keystone-k2g.dtsi
+++ b/arch/arm/boot/dts/keystone-k2g.dtsi
@@ -98,5 +98,13 @@
clock-frequency = <200000000>;
status = "disabled";
};
+
+ kirq0: keystone_irq@026202a0 {
+ compatible = "ti,keystone-irq";
+ interrupts = <GIC_SPI 1 IRQ_TYPE_EDGE_RISING>;
+ interrupt-controller;
+ #interrupt-cells = <1>;
+ ti,syscon-dev = <&devctrl 0x2a0>;
+ };
};
};
--
2.9.2
next prev parent reply other threads:[~2016-08-09 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 14:33 [PATCH v2 0/3] Add DSP control nodes for K2G Andrew F. Davis
2016-08-09 14:33 ` [PATCH v2 1/3] ARM: dts: keystone-k2g: Add device state controller node Andrew F. Davis
2016-08-09 14:33 ` Andrew F. Davis [this message]
2016-08-09 14:33 ` [PATCH v2 3/3] ARM: dts: keystone-k2g: Add DSP GPIO " Andrew F. Davis
2016-08-09 15:41 ` [PATCH v2 0/3] Add DSP control nodes for K2G Santosh Shilimkar
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=20160809143306.25028-3-afd@ti.com \
--to=afd@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=s-anna@ti.com \
--cc=ssantosh@kernel.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