Skip to content

Commit

Permalink
s/xen,shared-memory/xen,shared-memory-v1/g
Browse files Browse the repository at this point in the history
The shared memory device tree binding went upstream as
"xen,shared-memory-v1". So, rename all occurrences of
"xen,shared-memory" to "xen,shared-memory-v1" in the docs.

Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
  • Loading branch information
Stefano Stabellini committed Dec 18, 2019
1 parent aff77b4 commit b4b7e91
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/misc/arm/dom0_shared_mem.txt
Expand Up @@ -4,15 +4,15 @@ between dom0 and a domU.
First, we have to add a reserved-memory node to the host device tree to
advertise the special memory region to dom0, so that it won't use it to
allocate memory as any other pages. For that, we can make use of the
newly introduced "xen,shared-memory" compatible string. For example:
newly introduced "xen,shared-memory-v1" compatible string. For example:

reserved-memory {
#address-cells = <0x2>;
#size-cells = <0x2>;
ranges;

xen-shmem@0 {
compatible = "xen,shared-memory";
compatible = "xen,shared-memory-v1";
reg = <0x0 0x70000000 0x0 0x1000>;
};
};
Expand Down Expand Up @@ -42,7 +42,7 @@ be for example:
ranges;

xen-shmem@0 {
compatible = "xen,shared-memory";
compatible = "xen,shared-memory-v1";
reg = <0x0 0x70000000 0x0 0x1000>;
};
};
Expand Down

0 comments on commit b4b7e91

Please sign in to comment.