The BAM-DMUX node lives as a direct child of the modem PAS remoteproc node, but qcom,shikra-pas.yaml has unevaluatedProperties: false and does not list bam-dmux, so any DT adding this subnode fails schema validation.
Add an optional bam-dmux property referencing qcom,bam-dmux.yaml, mirroring qcom,msm8916-mss-pil.yaml. Co-developed-by: Deepak Kumar Singh <[email protected]> Signed-off-by: Deepak Kumar Singh <[email protected]> Signed-off-by: Vishnu Santhosh <[email protected]> --- Changes in v2: - Restrict bam-dmux to the qcom,shikra-mpss-pas compatible. - Link to v1: https://lore.kernel.org/r/20260727-shikra-pas-bam-dmux-binding-v1-1-c0159c7c3...@oss.qualcomm.com --- .../devicetree/bindings/remoteproc/qcom,shikra-pas.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml index 253b14eb2b598f0ca91854c8ff4d0b785090e621..eeb87aa5fae7ad9022fc800075c2f9e906b16ae6 100644 --- a/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml +++ b/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml @@ -44,6 +44,11 @@ properties: - description: Firmware name of the Hexagon core - description: Firmware name of the Hexagon Devicetree + bam-dmux: + $ref: /schemas/net/qcom,bam-dmux.yaml# + description: + Qualcomm BAM Data Multiplexer (provides network interface to the modem) + glink-edge: $ref: /schemas/remoteproc/qcom,glink-edge.yaml# description: @@ -117,6 +122,16 @@ allOf: power-domains: false power-domain-names: false + - if: + properties: + compatible: + enum: + - qcom,shikra-cdsp-pas + - qcom,shikra-lpaicp-pas + then: + properties: + bam-dmux: false + unevaluatedProperties: false examples: --- base-commit: f5098b6bae761e346ebcd9da7f95622c04733cff change-id: 20260727-shikra-pas-bam-dmux-binding-28a6bf97857c Best regards, -- Vishnu Santhosh <[email protected]>
