On 10/09/2020 17:20, Heinrich Schuchardt wrote:
The reusable and the no-map property are mutually exclusive.
Clarify this in the documentation.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@xxxxxx>
Acked-by: Grant Likely <grant.likely@xxxxxxx>
---
.../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 bac4afa3b197..eb987203548f 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.28.0
