All of lore.kernel.org
 help / color / mirror / Atom feed
From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: DT: Add binding for GIC virtualization extentions (VGIC)
Date: Thu, 5 Apr 2012 14:15:57 +0100	[thread overview]
Message-ID: <4F7D9B0D.7020009@citrix.com> (raw)
In-Reply-To: <4F7D974C.9050506@arm.com>

On 05/04/12 13:59, Marc Zyngier wrote:
> 
> How about this?
> 
> 	gic: interrupt-controller at 2c001000 {
> 		compatible = "arm,cortex-a15-gic";
> 		#interrupt-cells = <3>;
> 		#address-cells = <1>;
> 		#size-cells = <1>;
> 		interrupt-controller;
> 		reg = <0x2c001000 0x1000>,
> 		      <0x2c002000 0x100>;
> 
> 		vgic at 2c004000 {
> 			compatible = "arm,cortex-a15-vgic", "arm,vgic";
> 			reg = <0x2c004000 0x2000>,
> 			      <0x2c006000 0x2000>;
> 			interrupts = <1 9 0xf04>;
> 		};
> 	};
> 
> It cleanly separate the extension from the core GIC, and still make it
> part of the GIC node.

This looks sensible to me.

David

WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
To: Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org"
	<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] ARM: DT: Add binding for GIC virtualization extentions (VGIC)
Date: Thu, 5 Apr 2012 14:15:57 +0100	[thread overview]
Message-ID: <4F7D9B0D.7020009@citrix.com> (raw)
In-Reply-To: <4F7D974C.9050506-5wv7dgnIgG8@public.gmane.org>

On 05/04/12 13:59, Marc Zyngier wrote:
> 
> How about this?
> 
> 	gic: interrupt-controller@2c001000 {
> 		compatible = "arm,cortex-a15-gic";
> 		#interrupt-cells = <3>;
> 		#address-cells = <1>;
> 		#size-cells = <1>;
> 		interrupt-controller;
> 		reg = <0x2c001000 0x1000>,
> 		      <0x2c002000 0x100>;
> 
> 		vgic@2c004000 {
> 			compatible = "arm,cortex-a15-vgic", "arm,vgic";
> 			reg = <0x2c004000 0x2000>,
> 			      <0x2c006000 0x2000>;
> 			interrupts = <1 9 0xf04>;
> 		};
> 	};
> 
> It cleanly separate the extension from the core GIC, and still make it
> part of the GIC node.

This looks sensible to me.

David

  reply	other threads:[~2012-04-05 13:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 16:30 [PATCH] ARM: DT: Add binding for GIC virtualization extentions (VGIC) Marc Zyngier
2012-04-02 16:30 ` Marc Zyngier
2012-04-03  9:22 ` David Vrabel
2012-04-03  9:22   ` David Vrabel
2012-04-03  9:53   ` Marc Zyngier
2012-04-03  9:53     ` Marc Zyngier
2012-04-03 15:35     ` Grant Likely
2012-04-03 15:35       ` Grant Likely
2012-04-05 12:59       ` Marc Zyngier
2012-04-05 12:59         ` Marc Zyngier
2012-04-05 13:15         ` David Vrabel [this message]
2012-04-05 13:15           ` David Vrabel
2012-04-05 13:34         ` Rob Herring
2012-04-05 13:34           ` Rob Herring
2012-04-05 14:07           ` Marc Zyngier
2012-04-05 14:07             ` Marc Zyngier
2012-04-05 14:25             ` Rob Herring
2012-04-05 14:25               ` Rob Herring
2012-04-07  1:35         ` Grant Likely
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=4F7D9B0D.7020009@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.