[Xen-devel] [RFC PATCH v5 04/10] docs: Xen ARM DT bindings: document pcpus property

[Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>]

Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>
---
 Documentation/devicetree/bindings/arm/xen.txt | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/arm/xen.txt 
b/Documentation/devicetree/bindings/arm/xen.txt
index 0f7b9c2..1d7aea3 100644
--- a/Documentation/devicetree/bindings/arm/xen.txt
+++ b/Documentation/devicetree/bindings/arm/xen.txt
@@ -15,11 +15,29 @@ the following properties:
 - interrupts: the interrupt used by Xen to inject event notifications.
   A GIC node is also required.
 
+- pcpus: this property is optional. It contains an information about physical
+  CPUs. This information is used by xen-cpufreq driver. The structure of
+  nodes which are inside of this property is the same as in the /cpus/ node.
 
-Example (assuming #address-cells = <2> and #size-cells = <2>):
+Xen also copies all properties from cpus/ node to the hypervisor/pcpus/ node
+in the device tree which is created for the hwdom in case if HAS_HWDOM_CPUFREQ
+config is defined.
+
+Example (assuming #address-cells = <2> and #size-cells = <2>) whith pcpus
+property:
 
 hypervisor {
        compatible = "xen,xen-4.3", "xen,xen";
        reg = <0 0xb0000000 0 0x20000>;
        interrupts = <1 15 0xf08>;
+       pcpus {
+               cpu@0 {
+                       device_type = "cpu";
+                       reg = <0>;
+               };
+               cpu@1 {
+                       device_type = "cpu";
+                       reg = <1>;
+               };
+       };
 };
-- 
1.9.1


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel