From: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
shengchao.guo@oss.qualcomm.com,
Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
Subject: [PATCH 1/2] dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add Nord SoCCP
Date: Fri, 09 Oct 2026 13:05:39 +0530 [thread overview]
Message-ID: <20261009-soccp_driver_dtbinding-v1-1-40862f7fc58b@oss.qualcomm.com> (raw)
In-Reply-To: <20261009-soccp_driver_dtbinding-v1-0-40862f7fc58b@oss.qualcomm.com>
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 <anurag.pateriya@oss.qualcomm.com>
---
.../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
next prev parent reply other threads:[~2026-10-09 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 7:35 [PATCH 0/2] Add binding and driver for Nord SoCCP Anurag Pateriya
2026-10-09 7:35 ` Anurag Pateriya [this message]
2026-10-09 7:52 ` [PATCH 1/2] dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add " Shawn Guo
2026-10-09 14:08 ` Rob Herring (Arm)
2026-10-09 7:35 ` [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord Anurag Pateriya
2026-10-09 7:53 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261009-soccp_driver_dtbinding-v1-1-40862f7fc58b@oss.qualcomm.com \
--to=anurag.pateriya@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=shengchao.guo@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox