Document the 'no-exclusive' parameter used for the 'shared-dma-pool'
compatible reserved-memory type.
Signed-off-by: Neil Armstrong <narmstr...@baylibre.com>
---
Documentation/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 3da0ebd..897aada 100644
--- a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
+++ b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
@@ -63,6 +63,9 @@ reusable (optional) - empty property
able to reclaim it back. Typically that means that the operating
system can use that region to store volatile or cached data that
can be otherwise regenerated or migrated elsewhere.
+no-exclusive (optional) - empty property
+ - Indicates the operating system can fall back to the default allocation
+ mechanism if no more enough memory is available from this pool.
Linux implementation note:
- If a "linux,cma-default" property is present, then Linux will use the
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
