From: Marc Zyngier <marc.zyngier@arm.com>
To: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Cc: rob.herring@calxeda.com
Subject: [PATCH] ARM: DT: Add binding for GIC virtualization extentions (VGIC)
Date: Mon, 2 Apr 2012 17:30:17 +0100 [thread overview]
Message-ID: <1333384217-13441-1-git-send-email-marc.zyngier@arm.com> (raw)
The GICv2 can have virtualization extension support, consisting
of an additional set of registers and interrupts. Add the necessary
binding to the GIC DT documentation.
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
---
Documentation/devicetree/bindings/arm/gic.txt | 29 +++++++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/gic.txt b/Documentation/devicetree/bindings/arm/gic.txt
index 9b4b82a..fb1b5ab 100644
--- a/Documentation/devicetree/bindings/arm/gic.txt
+++ b/Documentation/devicetree/bindings/arm/gic.txt
@@ -57,3 +57,32 @@ Example:
<0xfff10100 0x100>;
};
+
+* GIC virtualization extensions (VGIC)
+
+For ARM cores that support the virtualization extensions, an
+additional node describes the VGIC hardware block. Only exists if the
+GIC is the primary interrupt controller.
+
+Required properties:
+- compatible : should be one of:
+ "arm,cortex-a15-vgic"
+ "arm,cortex-a7-vgic"
+ "arm,vgic"
+
+- reg : Specifies base physical address and size of the VGIC
+ registers. The first region is the GIC virtual interface control
+ register base and size. the 2nd region is the GIC virtual cpu
+ interface register base and size.
+
+- interrupts : VGIC maintainance interrupt. Must be relative to the
+ primary GIC.
+
+Example:
+
+ vgic@2c004000 {
+ compatible = "arm,cortex-a15-vgic", "arm,vgic";
+ reg = <0x2c004000 0x2000>,
+ <0x2c006000 0x2000>;
+ interrupts = <1 9 0xf04>;
+ };
--
1.7.7.1
next reply other threads:[~2012-04-02 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 16:30 Marc Zyngier [this message]
2012-04-03 9:22 ` [PATCH] ARM: DT: Add binding for GIC virtualization extentions (VGIC) David Vrabel
2012-04-03 9:53 ` Marc Zyngier
2012-04-03 15:35 ` Grant Likely
2012-04-05 12:59 ` Marc Zyngier
[not found] ` <4F7D974C.9050506-5wv7dgnIgG8@public.gmane.org>
2012-04-05 13:15 ` David Vrabel
2012-04-05 13:34 ` Rob Herring
2012-04-05 14:07 ` Marc Zyngier
[not found] ` <4F7DA71A.4020809-5wv7dgnIgG8@public.gmane.org>
2012-04-05 14:25 ` Rob Herring
2012-04-07 1:35 ` Grant Likely
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=1333384217-13441-1-git-send-email-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rob.herring@calxeda.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).