The SoCCP (SoC Control Processor) on Nord handles hardware fencing for display and other use cases. It shares interrupts, SMP2P states, power domains, and clock with Kaanapali SoCCP, except that it ships firmware without a separate devicetree image, so it cannot use the Kaanapali compatible as fallback.
Add qcom,nord-soccp-pas as a standalone compatible with a single firmware-name/memory-region pair, while existing SoCs keep requiring two. Signed-off-by: Anurag Pateriya <[email protected]> --- .../remoteproc/qcom,kaanapali-soccp-pas.yaml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml index e6c78d621d17..c1911124e073 100644 --- a/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml +++ b/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml @@ -26,6 +26,7 @@ properties: - enum: - qcom,glymur-soccp-pas - qcom,kaanapali-soccp-pas + - qcom,nord-soccp-pas reg: maxItems: 1 @@ -49,11 +50,13 @@ properties: - const: mx firmware-name: + minItems: 1 items: - description: Firmware name of the SoC Control Processor - description: Firmware name of the SoCCP Devicetree memory-region: + minItems: 1 items: - description: Memory region for main Firmware authentication - description: Memory region for Devicetree Firmware authentication @@ -93,6 +96,23 @@ required: allOf: - $ref: /schemas/remoteproc/qcom,pas-common.yaml# + - if: + properties: + compatible: + contains: + const: qcom,nord-soccp-pas + then: + properties: + firmware-name: + maxItems: 1 + memory-region: + maxItems: 1 + else: + properties: + firmware-name: + minItems: 2 + memory-region: + minItems: 2 unevaluatedProperties: false -- 2.43.0
