From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v5 21/21] xen/arm: check for GICv3 platform support Date: Mon, 16 Jun 2014 16:37:29 +0100 Message-ID: <539F0F39.2010801@linaro.org> References: <1402580192-13937-1-git-send-email-vijay.kilari@gmail.com> <1402580192-13937-22-git-send-email-vijay.kilari@gmail.com> <539A2EFE.5010500@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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 Cc: Ian Campbell , Stefano Stabellini , Prasun Kapoor , Vijaya Kumar K , Tim Deegan , "xen-devel@lists.xen.org" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 06/16/2014 04:28 PM, Vijay Kilari wrote: > On Fri, Jun 13, 2014 at 4:21 AM, Julien Grall wrote: >> On 12/06/14 14:36, vijay.kilari@gmail.com wrote: >>> >>> From: Vijaya Kumar K >>> >>> ID_AA64PFR0_EL1 register provides information about GIC support. >>> Check for this register in GICv3 driver. >>> >>> Also print GICv3 support information in boot log >> >> >> We already have a GICv3 node in the device tree. Why do we need to check >> that GICv3 is effectively support by board? >> >> We rely on the user provide us a correct device tree, so I don't think this >> patch is helpful... > > GICv3 driver is compiled for arm64 alone. Assume that platform does not support > GICv3 and DT is passed with GICv3 info. In such scenario this patch helps. I think this is pointless, lots of things (worst than trying to poke a GICv3 on a GICv2 platform) can happen on Xen and Linux if the user fails to give a valid device tree. IHMO, it's safe to assume that the user will provide a device tree with valid devices... Regards, -- Julien Grall