From 07770a5f78938a9b6e4a9756d4c744c4e1c7b54f Mon Sep 17 00:00:00 2001 From: Heinrich Schuchardt Date: Thu, 10 Sep 2020 18:20:20 +0200 Subject: [PATCH] of: properties of reserved-memory nodes The reusable and the no-map property are mutually exclusive. Clarify this in the documentation. Acked-by: Grant Likely Signed-off-by: Heinrich Schuchardt Link: https://lore.kernel.org/r/20200910162020.3927-1-xypron.glpk@gmx.de Signed-off-by: Rob Herring --- .../devicetree/bindings/reserved-memory/reserved-memory.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt index 4dd20de6977f3..e8d3096d922c3 100644 --- a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt +++ b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt @@ -64,6 +64,9 @@ reusable (optional) - empty property system can use that region to store volatile or cached data that can be otherwise regenerated or migrated elsewhere. +A node must not carry both the no-map and the reusable property as these are +logically contradictory. + Linux implementation note: - If a "linux,cma-default" property is present, then Linux will use the region for the default pool of the contiguous memory allocator. -- 2.39.5