The 'phandle-array' type is a bit ambiguous. It can be either just an
array of phandles or an array of phandles plus args. "qcom,rpm-msg-ram" is
the former and needs to constrain each entry to a single phandle value.
Signed-off-by: Rob Herring <[email protected]>
---
.../devicetree/bindings/soc/qcom/qcom,rpm-master-stats.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,rpm-master-stats.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,rpm-master-stats.yaml
index 031800985b5e..9410404f87f1 100644
--- a/Documentation/devicetree/bindings/soc/qcom/qcom,rpm-master-stats.yaml
+++ b/Documentation/devicetree/bindings/soc/qcom/qcom,rpm-master-stats.yaml
@@ -35,6 +35,8 @@ properties:
description: Phandle to an RPM MSG RAM slice containing the master stats
minItems: 1
maxItems: 5
+ items:
+ maxItems: 1
qcom,master-names:
$ref: /schemas/types.yaml#/definitions/string-array
--
2.43.0
On 24/01/2024 20:07, Rob Herring wrote:
> The 'phandle-array' type is a bit ambiguous. It can be either just an
> array of phandles or an array of phandles plus args. "qcom,rpm-msg-ram" is
> the former and needs to constrain each entry to a single phandle value.
>
> Signed-off-by: Rob Herring <[email protected]>
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Best regards,
Krzysztof
On Wed, 24 Jan 2024 13:07:44 -0600, Rob Herring wrote:
> The 'phandle-array' type is a bit ambiguous. It can be either just an
> array of phandles or an array of phandles plus args. "qcom,rpm-msg-ram" is
> the former and needs to constrain each entry to a single phandle value.
>
>
Applied, thanks!
[1/1] dt-bindings: soc/qcom: Add size constraints on "qcom,rpm-msg-ram"
commit: 8796fa0f9a08359bb87e859d6010350a9d7da38f
Best regards,
--
Bjorn Andersson <[email protected]>