GLINK edge contains subnodes representing devices related to the remote
processor. Each of such device (e.g. APR or FastRPC) must have
a "qcom,glink-channels" property. However the APR or FastRPC device can
be also part of other communication - SMD - thus their schema does not
require "qcom,glink-channels".
To make the GLINK edge bindings strict, require "qcom,glink-channels"
for its children.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>
---
.../devicetree/bindings/remoteproc/qcom,glink-edge.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,glink-edge.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,glink-edge.yaml
index 8953678da83e..25c27464ef25 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,glink-edge.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,glink-edge.yaml
@@ -19,11 +19,15 @@ properties:
apr:
$ref: /schemas/soc/qcom/qcom,apr.yaml#
+ required:
+ - qcom,glink-channels
description:
Qualcomm APR/GPR (Asynchronous/Generic Packet Router)
fastrpc:
$ref: /schemas/misc/qcom,fastrpc.yaml#
+ required:
+ - qcom,glink-channels
description:
Qualcomm FastRPC
--
2.34.1
