From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v2 13/15] xen/arm: Add support for GIC v3 Date: Thu, 10 Apr 2014 10:25:29 +0100 Message-ID: <1397121929.9862.59.camel@kazak.uk.xensource.com> References: <1396612593-443-1-git-send-email-vijay.kilari@gmail.com> <1396612593-443-14-git-send-email-vijay.kilari@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1396612593-443-14-git-send-email-vijay.kilari@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: vijay.kilari@gmail.com Cc: stefano.stabellini@eu.citrix.com, Prasun.Kapoor@caviumnetworks.com, vijaya.kumar@caviumnetworks.com, julien.grall@linaro.org, xen-devel@lists.xen.org, stefano.stabellini@citrix.com List-Id: xen-devel@lists.xenproject.org On Fri, 2014-04-04 at 17:26 +0530, vijay.kilari@gmail.com wrote: > +#define GICD_CTLR (0x000) > +#define GICD_TYPER (0x004) > +#define GICD_IIDR (0x008) > +#define GICD_STATUSR (0x010) A lot of these are identical to the GIV v2 definitions. Is a separate set of #defines *really* necessary? I'd be happy with: #define GICD_CTLR (0x000) #define GICD_TYPER (0x004) #define GICD_IIDR (0x008) #define GICD_STATUSR (0x010) /* GICv3 only */ #define GICD_BLARGLE (0x...) /* GICv2 only */ etc. Or if you really feel that separate defines are needed then at the least they should incorporate v2 and v3 into their names. Ian.