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 v2 0/2] Add binding and driver for Nord SoCCP
Date: Wed, 14 Oct 2026 17:16:08 +0530 [thread overview]
Message-ID: <20261014-soccp_driver_dtbinding-v2-0-09d9c1378e9e@oss.qualcomm.com> (raw)
This series adds System on Chip Control Processor (SOCCP) remoteproc
support for the Nord platform. SOCCP is a dedicated control processor
that handles hardware fencing for display and other use cases on
Nord-based devices, sharing interrupts, SMP2P states, power domains,
and clock with Kaanapali SoCCP. However, its firmware ships without
a separate SoCCP devicetree image. It therefore takes a single
firmware-name and memory-region, and cannot use the Kaanapali
compatible as fallback.
To: Bjorn Andersson <andersson@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk+dt@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org
Cc: linux-remoteproc@vger.kernel.org
Cc: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: shengchao.guo@oss.qualcomm.com
Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
Changes in v2:
- Amend the commit for remoteproc driver support to add Nord specific usecase of SoCCP.(Shawn, Konrad)
- Add the information regarding only single firmware for SoCCP and no seperate device tree image.(Konrad)
- Collected Reviewed-by tags from Shawn and Rob
- Link to v1: https://lore.kernel.org/all/20261009-soccp_driver_dtbinding-v1-0-40862f7fc58b@oss.qualcomm.com
---
---
Anurag Pateriya (2):
dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add Nord SoCCP
remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord
.../remoteproc/qcom,kaanapali-soccp-pas.yaml | 20 ++++++++++++++++++++
drivers/remoteproc/qcom_q6v5_pas.c | 15 +++++++++++++++
2 files changed, 35 insertions(+)
---
base-commit: 0312234a60912d65819167631115e39c7e8f9621
change-id: 20261008-soccp_driver_dtbinding-ad131aa42a94
Best regards,
--
Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
next reply other threads:[~2026-10-14 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 11:46 Anurag Pateriya [this message]
2026-10-14 11:46 ` [PATCH v2 1/2] dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add " Anurag Pateriya
2026-10-14 11:46 ` [PATCH v2 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord Anurag Pateriya
2026-10-15 0:21 ` 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=20261014-soccp_driver_dtbinding-v2-0-09d9c1378e9e@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
all inboxes | Powered by JetHome®