Some SoCs mandate that the RMTFS is also assigned to the NAV VM, while
others really don't want that. Since it has to be conditional, add a
bool property to toggle this behavior.
Signed-off-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxx>
---
v1 -> v2:
- Rewrite the newly added description
.../devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml b/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
index 2998f1c8f0db..4026788a4e40 100644
--- a/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
+++ b/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
@@ -31,6 +31,12 @@ properties:
description: >
vmid of the remote processor, to set up memory protection
+ qcom,assign-to-nav:
+ type: boolean
+ description:
+ Whether to also assign the region to a third (NAV) VM, as opposed to
+ the usual 2.
+
required:
- qcom,client-id
--
2.39.0
