Re: [PATCH v3 06/25] docs: Xen ARM DT bindings
From: Rob Herring <hidden>
Date: 2012-08-27 23:03:58
Also in:
linux-arm-kernel, lkml, xen-devel
On 08/16/2012 10:35 AM, Stefano Stabellini wrote:
quoted hunk ↗ jump to hunk
Add a doc to describe the Xen ARM device tree bindings Signed-off-by: Stefano Stabellini <redacted> CC: devicetree-discuss@lists.ozlabs.org CC: David Vrabel <redacted> --- Documentation/devicetree/bindings/arm/xen.txt | 22 ++++++++++++++++++++++ 1 files changed, 22 insertions(+), 0 deletions(-) create mode 100644 Documentation/devicetree/bindings/arm/xen.txtdiff --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-<version>"; + where <version> 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 Rob
+
+
+Example:
+
+hypervisor {
+ compatible = "xen,xen", "xen,xen-4.3";
+ reg = <0xb0000000 0x20000>;
+ interrupts = <1 15 0xf08>;
+};