From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760881Ab2ILRIK (ORCPT ); Wed, 12 Sep 2012 13:08:10 -0400 Received: from smtp.ctxuk.citrix.com ([62.200.22.115]:35999 "EHLO SMTP.EU.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760603Ab2ILRIA (ORCPT ); Wed, 12 Sep 2012 13:08:00 -0400 X-IronPort-AV: E=Sophos;i="4.80,410,1344211200"; d="scan'208";a="14502526" Date: Wed, 12 Sep 2012 18:07:16 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Rob Herring CC: Stefano Stabellini , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xensource.com" , "linaro-dev@lists.linaro.org" , Ian Campbell , "arnd@arndb.de" , "konrad.wilk@oracle.com" , "catalin.marinas@arm.com" , "devicetree-discuss@lists.ozlabs.org" , "Tim (Xen.org)" , David Vrabel , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH v3 06/25] docs: Xen ARM DT bindings In-Reply-To: <503BFCD8.5090804@gmail.com> Message-ID: References: <1345131377-14713-6-git-send-email-stefano.stabellini@eu.citrix.com> <503BFCD8.5090804@gmail.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 28 Aug 2012, Rob Herring wrote: > On 08/16/2012 10:35 AM, Stefano Stabellini wrote: > > Add a doc to describe the Xen ARM device tree bindings > > > > Signed-off-by: Stefano Stabellini > > CC: devicetree-discuss@lists.ozlabs.org > > CC: David Vrabel > > --- > > Documentation/devicetree/bindings/arm/xen.txt | 22 ++++++++++++++++++++++ > > 1 files changed, 22 insertions(+), 0 deletions(-) > > create mode 100644 Documentation/devicetree/bindings/arm/xen.txt > > > > diff --git a/Documentation/devicetree/bindings/arm/xen.txt b/Documentation/devicetree/bindings/arm/xen.txt > > new file mode 100644 > > index 0000000..ec6d884 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/arm/xen.txt > > @@ -0,0 +1,22 @@ > > +* Xen hypervisor device tree bindings > > + > > +Xen ARM virtual platforms shall have the following properties: > > + > > +- compatible: > > + compatible = "xen,xen", "xen,xen-"; > > + where is the version of the Xen ABI of the platform. > > + > > +- reg: specifies the base physical address and size of a region in > > + memory where the grant table should be mapped to, using an > > + HYPERVISOR_memory_op hypercall. > > + > > +- interrupts: the interrupt used by Xen to inject event notifications. > > You should look at ePAPR 1.1 which defines hypervisor related bindings. > While it is a PPC doc, we should reuse or extend what makes sense. > > See section 7.5: > > https://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.1.pdf Thanks for the link, I wasn't aware of ePAPR. The hypervisor node defined by ePAPR is not very different from what I am proposing. Should I try to be compatible with the hypervisor specification above (as in compatible = "epapr,hypervisor-1.1")? Or should I just use it as a reference for my own specification? Personally I would rather avoid full compatibility with ePAPR.