* [PATCH RFC v2 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support
@ 2026-10-18 7:16 Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Anurag Pateriya @ 2026-10-18 7:16 UTC (permalink / raw)
To: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel, Shawn Guo,
Anurag Pateriya, Abel Vesa
This series adds device tree support for SoCCP
(System on Chip Control Processor) on Nord platform.
SoCCP is used for hw fencing for display and other
use cases on Nord.
It has the same interrupts, SMP2P states, power domains
and clock as Kaanapali SoCCP, but its firmware ships without a separate
SoCCP devicetree image. It therefore takes a single firmware-name and
memory-region.
Prerequisite series:
[PATCH v5 0/7] arm64: dts: qcom: nord: Add remoteproc and PMIC support
https://lore.kernel.org/all/20261014063953.549379-1-shengchao.guo@oss.qualcomm.com/
[PATCH v2 0/2] Add binding and driver for Nord SoCCP
https://lore.kernel.org/all/20261014-soccp_driver_dtbinding-v2-0-09d9c1378e9e@oss.qualcomm.com/
Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
---
Changes in v2:
- Drop the BWMON nodes from the Nord SoC as they are outside the scope of this series. (Konrad, Abel)
- Enable SoCCP by default on Nord and drop the board-level status overrides. (Konrad)
- Amend the RRD and Ride-Embedded board commits to describe the addition of SoCCP support rather than its enablement.
- Fix missing whitespace before the opening brace in the RRD SoCCP node. (Konrad)
- Got Reviewed-By tags from Abel.
- Link to v1: https://lore.kernel.org/r/20261016-nord-soccp-dt-v1-0-ee13aef55d8b@oss.qualcomm.com
---
Anurag Pateriya (3):
arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
arm64: dts: qcom: nord: Add SoCCP on RRD board
arm64: dts: qcom: nord: Add SoCCP on Ride-Embedded board
arch/arm64/boot/dts/qcom/nord-embedded.dtsi | 9 ++++
arch/arm64/boot/dts/qcom/nord-ride-embedded.dts | 4 ++
arch/arm64/boot/dts/qcom/nord-rrd.dts | 4 ++
arch/arm64/boot/dts/qcom/nord.dtsi | 57 +++++++++++++++++++++++++
4 files changed, 74 insertions(+)
---
base-commit: 601369ae08a35f1698a96bbcff02f3665a0cf675
change-id: 20261015-nord-soccp-dt-bbc2d288c560
Best regards,
--
Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
2026-10-18 7:16 [PATCH RFC v2 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya
@ 2026-10-18 7:16 ` Anurag Pateriya
2026-10-19 6:34 ` Shawn Guo
2026-10-18 7:16 ` [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 3/3] arm64: dts: qcom: nord: Add SoCCP on Ride-Embedded board Anurag Pateriya
2 siblings, 1 reply; 8+ messages in thread
From: Anurag Pateriya @ 2026-10-18 7:16 UTC (permalink / raw)
To: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel, Shawn Guo, Anurag Pateriya
Add the SoCCP (System on Chip Control Processor) remoteproc node and
its SMP2P configuration at the SoC level in nord.dtsi, and wire up
the clock and power-domain dependencies shared by all Nord embedded
variants in nord-embedded.dtsi.
Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/nord-embedded.dtsi | 9 +++++
arch/arm64/boot/dts/qcom/nord.dtsi | 57 +++++++++++++++++++++++++++++
2 files changed, 66 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
index 6dc4c871f41e..e21b9ba480f5 100644
--- a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
+++ b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
@@ -430,6 +430,15 @@ &remoteproc_cdsp3 {
"nsp";
};
+&remoteproc_soccp {
+ clocks = <&rpmhcc RPMH_CXO_CLK>;
+ clock-names = "xo";
+ power-domains = <&rpmhpd RPMHPD_CX>,
+ <&rpmhpd RPMHPD_MX>;
+ power-domain-names = "cx",
+ "mx";
+};
+
&spi0 {
clocks = <&segcc SE_GCC_QUPV3_WRAP0_S0_CLK>;
clock-names = "se";
diff --git a/arch/arm64/boot/dts/qcom/nord.dtsi b/arch/arm64/boot/dts/qcom/nord.dtsi
index dfbbaf94a7ae..827531fc1276 100644
--- a/arch/arm64/boot/dts/qcom/nord.dtsi
+++ b/arch/arm64/boot/dts/qcom/nord.dtsi
@@ -1029,6 +1029,28 @@ smp2p_cdsp3_in: slave-kernel {
};
};
+ smp2p-soccp {
+ compatible = "qcom,smp2p";
+ interrupts-extended = <&ipcc0 IPCC_MPROC_SOCCP
+ IPCC_MPROC_SIGNAL_SMP2P
+ IRQ_TYPE_EDGE_RISING>;
+ mboxes = <&ipcc0 IPCC_MPROC_SOCCP IPCC_MPROC_SIGNAL_SMP2P>;
+ qcom,smem = <617>, <616>;
+ qcom,local-pid = <0>;
+ qcom,remote-pid = <19>;
+
+ smp2p_soccp_out: master-kernel {
+ qcom,entry-name = "master-kernel";
+ #qcom,smem-state-cells = <1>;
+ };
+
+ smp2p_soccp_in: slave-kernel {
+ qcom,entry-name = "slave-kernel";
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ };
+ };
+
soc: soc@0 {
compatible = "simple-bus";
#address-cells = <2>;
@@ -1587,6 +1609,41 @@ uart13: serial@a98000 {
};
};
+ remoteproc_soccp: remoteproc@d00000 {
+ compatible = "qcom,nord-soccp-pas";
+ reg = <0x0 0x00d00000 0x0 0x200000>;
+
+ interrupts-extended = <&intc GIC_SPI 167 IRQ_TYPE_EDGE_RISING>,
+ <&smp2p_soccp_in 0 IRQ_TYPE_EDGE_RISING>,
+ <&smp2p_soccp_in 1 IRQ_TYPE_EDGE_RISING>,
+ <&smp2p_soccp_in 2 IRQ_TYPE_EDGE_RISING>,
+ <&smp2p_soccp_in 3 IRQ_TYPE_EDGE_RISING>,
+ <&smp2p_soccp_in 9 IRQ_TYPE_EDGE_RISING>;
+ interrupt-names = "wdog",
+ "fatal",
+ "ready",
+ "handover",
+ "stop-ack",
+ "pong";
+
+ memory-region = <&soccp_mem>;
+
+ qcom,smem-states = <&smp2p_soccp_out 0>,
+ <&smp2p_soccp_out 8>;
+ qcom,smem-state-names = "stop",
+ "ping";
+
+ glink-edge {
+ interrupts-extended = <&ipcc0 IPCC_MPROC_SOCCP
+ IPCC_MPROC_SIGNAL_GLINK_QMP
+ IRQ_TYPE_EDGE_RISING>;
+ mboxes = <&ipcc0 IPCC_MPROC_SOCCP
+ IPCC_MPROC_SIGNAL_GLINK_QMP>;
+ qcom,remote-pid = <19>;
+ label = "soccp";
+ };
+ };
+
rng: rng@10c3000 {
compatible = "qcom,nord-trng",
"qcom,trng";
--
2.43.0
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board
2026-10-18 7:16 [PATCH RFC v2 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
@ 2026-10-18 7:16 ` Anurag Pateriya
2026-10-18 12:49 ` Shawn Guo
2026-10-18 7:16 ` [PATCH RFC v2 3/3] arm64: dts: qcom: nord: Add SoCCP on Ride-Embedded board Anurag Pateriya
2 siblings, 1 reply; 8+ messages in thread
From: Anurag Pateriya @ 2026-10-18 7:16 UTC (permalink / raw)
To: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel, Shawn Guo, Anurag Pateriya
Add the SoCCP remoteproc node with its firmware path on the Nord
RRD board.
Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/nord-rrd.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/nord-rrd.dts b/arch/arm64/boot/dts/qcom/nord-rrd.dts
index 47978df0af92..89f8d36ed812 100644
--- a/arch/arm64/boot/dts/qcom/nord-rrd.dts
+++ b/arch/arm64/boot/dts/qcom/nord-rrd.dts
@@ -434,6 +434,10 @@ &spi16 {
status = "okay";
};
+&remoteproc_soccp {
+ firmware-name = "qcom/nord/soccp.mbn";
+};
+
&uart4 {
status = "okay";
};
--
2.43.0
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH RFC v2 3/3] arm64: dts: qcom: nord: Add SoCCP on Ride-Embedded board
2026-10-18 7:16 [PATCH RFC v2 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board Anurag Pateriya
@ 2026-10-18 7:16 ` Anurag Pateriya
2 siblings, 0 replies; 8+ messages in thread
From: Anurag Pateriya @ 2026-10-18 7:16 UTC (permalink / raw)
To: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-arm-msm, devicetree, linux-kernel, Shawn Guo,
Anurag Pateriya, Abel Vesa
Add the SoCCP remoteproc node with its firmware path on the Nord
Ride Embedded board.
Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/nord-ride-embedded.dts | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/nord-ride-embedded.dts b/arch/arm64/boot/dts/qcom/nord-ride-embedded.dts
index 49635695f832..1aa3ed4c1e45 100644
--- a/arch/arm64/boot/dts/qcom/nord-ride-embedded.dts
+++ b/arch/arm64/boot/dts/qcom/nord-ride-embedded.dts
@@ -419,6 +419,10 @@ &remoteproc_cdsp3 {
status = "okay";
};
+&remoteproc_soccp {
+ firmware-name = "qcom/nord/soccp.mbn";
+};
+
&uart15 {
status = "okay";
};
--
2.43.0
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board
2026-10-18 7:16 ` [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board Anurag Pateriya
@ 2026-10-18 12:49 ` Shawn Guo
2026-10-21 6:36 ` Anurag Pateriya
0 siblings, 1 reply; 8+ messages in thread
From: Shawn Guo @ 2026-10-18 12:49 UTC (permalink / raw)
To: Anurag Pateriya
Cc: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-msm, devicetree,
linux-kernel
On Sun, Oct 18, 2026 at 12:46:47PM +0530, Anurag Pateriya wrote:
> Add the SoCCP remoteproc node with its firmware path on the Nord
> RRD board.
>
> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/nord-rrd.dts | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/nord-rrd.dts b/arch/arm64/boot/dts/qcom/nord-rrd.dts
> index 47978df0af92..89f8d36ed812 100644
> --- a/arch/arm64/boot/dts/qcom/nord-rrd.dts
> +++ b/arch/arm64/boot/dts/qcom/nord-rrd.dts
> @@ -434,6 +434,10 @@ &spi16 {
> status = "okay";
> };
>
> +&remoteproc_soccp {
In alphabetical order, I think it should go right after remoteproc_cdsp3
rather than spi16.
Shawn
> + firmware-name = "qcom/nord/soccp.mbn";
> +};
> +
> &uart4 {
> status = "okay";
> };
>
> --
> 2.43.0
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
2026-10-18 7:16 ` [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
@ 2026-10-19 6:34 ` Shawn Guo
2026-10-21 6:35 ` Anurag Pateriya
0 siblings, 1 reply; 8+ messages in thread
From: Shawn Guo @ 2026-10-19 6:34 UTC (permalink / raw)
To: Anurag Pateriya
Cc: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-msm, devicetree,
linux-kernel
On Sun, Oct 18, 2026 at 12:46:46PM +0530, Anurag Pateriya wrote:
> Add the SoCCP (System on Chip Control Processor) remoteproc node and
> its SMP2P configuration at the SoC level in nord.dtsi, and wire up
> the clock and power-domain dependencies shared by all Nord embedded
> variants in nord-embedded.dtsi.
>
> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/nord-embedded.dtsi | 9 +++++
> arch/arm64/boot/dts/qcom/nord.dtsi | 57 +++++++++++++++++++++++++++++
> 2 files changed, 66 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
> index 6dc4c871f41e..e21b9ba480f5 100644
> --- a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
> +++ b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
> @@ -430,6 +430,15 @@ &remoteproc_cdsp3 {
> "nsp";
> };
>
> +&remoteproc_soccp {
> + clocks = <&rpmhcc RPMH_CXO_CLK>;
> + clock-names = "xo";
> + power-domains = <&rpmhpd RPMHPD_CX>,
> + <&rpmhpd RPMHPD_MX>;
> + power-domain-names = "cx",
> + "mx";
> +};
> +
> &spi0 {
> clocks = <&segcc SE_GCC_QUPV3_WRAP0_S0_CLK>;
> clock-names = "se";
> diff --git a/arch/arm64/boot/dts/qcom/nord.dtsi b/arch/arm64/boot/dts/qcom/nord.dtsi
> index dfbbaf94a7ae..827531fc1276 100644
> --- a/arch/arm64/boot/dts/qcom/nord.dtsi
> +++ b/arch/arm64/boot/dts/qcom/nord.dtsi
> @@ -1029,6 +1029,28 @@ smp2p_cdsp3_in: slave-kernel {
> };
> };
>
> + smp2p-soccp {
> + compatible = "qcom,smp2p";
> + interrupts-extended = <&ipcc0 IPCC_MPROC_SOCCP
> + IPCC_MPROC_SIGNAL_SMP2P
> + IRQ_TYPE_EDGE_RISING>;
> + mboxes = <&ipcc0 IPCC_MPROC_SOCCP IPCC_MPROC_SIGNAL_SMP2P>;
> + qcom,smem = <617>, <616>;
> + qcom,local-pid = <0>;
> + qcom,remote-pid = <19>;
> +
> + smp2p_soccp_out: master-kernel {
> + qcom,entry-name = "master-kernel";
> + #qcom,smem-state-cells = <1>;
> + };
> +
> + smp2p_soccp_in: slave-kernel {
> + qcom,entry-name = "slave-kernel";
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + };
> + };
> +
> soc: soc@0 {
> compatible = "simple-bus";
> #address-cells = <2>;
> @@ -1587,6 +1609,41 @@ uart13: serial@a98000 {
> };
> };
>
> + remoteproc_soccp: remoteproc@d00000 {
> + compatible = "qcom,nord-soccp-pas";
It causes CHECK_DTBS complaints for nord-ride.dtb, so we may want to move
the compatible to nord-embedded.dtsi.
Shawn
> + reg = <0x0 0x00d00000 0x0 0x200000>;
> +
> + interrupts-extended = <&intc GIC_SPI 167 IRQ_TYPE_EDGE_RISING>,
> + <&smp2p_soccp_in 0 IRQ_TYPE_EDGE_RISING>,
> + <&smp2p_soccp_in 1 IRQ_TYPE_EDGE_RISING>,
> + <&smp2p_soccp_in 2 IRQ_TYPE_EDGE_RISING>,
> + <&smp2p_soccp_in 3 IRQ_TYPE_EDGE_RISING>,
> + <&smp2p_soccp_in 9 IRQ_TYPE_EDGE_RISING>;
> + interrupt-names = "wdog",
> + "fatal",
> + "ready",
> + "handover",
> + "stop-ack",
> + "pong";
> +
> + memory-region = <&soccp_mem>;
> +
> + qcom,smem-states = <&smp2p_soccp_out 0>,
> + <&smp2p_soccp_out 8>;
> + qcom,smem-state-names = "stop",
> + "ping";
> +
> + glink-edge {
> + interrupts-extended = <&ipcc0 IPCC_MPROC_SOCCP
> + IPCC_MPROC_SIGNAL_GLINK_QMP
> + IRQ_TYPE_EDGE_RISING>;
> + mboxes = <&ipcc0 IPCC_MPROC_SOCCP
> + IPCC_MPROC_SIGNAL_GLINK_QMP>;
> + qcom,remote-pid = <19>;
> + label = "soccp";
> + };
> + };
> +
> rng: rng@10c3000 {
> compatible = "qcom,nord-trng",
> "qcom,trng";
>
> --
> 2.43.0
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
2026-10-19 6:34 ` Shawn Guo
@ 2026-10-21 6:35 ` Anurag Pateriya
0 siblings, 0 replies; 8+ messages in thread
From: Anurag Pateriya @ 2026-10-21 6:35 UTC (permalink / raw)
To: Shawn Guo
Cc: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-msm, devicetree,
linux-kernel
On 10/19/2026 12:04 PM, Shawn Guo wrote:
> On Sun, Oct 18, 2026 at 12:46:46PM +0530, Anurag Pateriya wrote:
>> Add the SoCCP (System on Chip Control Processor) remoteproc node and
>> its SMP2P configuration at the SoC level in nord.dtsi, and wire up
>> the clock and power-domain dependencies shared by all Nord embedded
>> variants in nord-embedded.dtsi.
>>
>> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/nord-embedded.dtsi | 9 +++++
>> arch/arm64/boot/dts/qcom/nord.dtsi | 57 +++++++++++++++++++++++++++++
>> 2 files changed, 66 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
>> index 6dc4c871f41e..e21b9ba480f5 100644
>> --- a/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/nord-embedded.dtsi
>> @@ -430,6 +430,15 @@ &remoteproc_cdsp3 {
>> "nsp";
>> };
>>
>> +&remoteproc_soccp {
>> + clocks = <&rpmhcc RPMH_CXO_CLK>;
>> + clock-names = "xo";
>> + power-domains = <&rpmhpd RPMHPD_CX>,
>> + <&rpmhpd RPMHPD_MX>;
>> + power-domain-names = "cx",
>> + "mx";
>> +};
>> +
>> &spi0 {
>> clocks = <&segcc SE_GCC_QUPV3_WRAP0_S0_CLK>;
>> clock-names = "se";
>> diff --git a/arch/arm64/boot/dts/qcom/nord.dtsi b/arch/arm64/boot/dts/qcom/nord.dtsi
>> index dfbbaf94a7ae..827531fc1276 100644
>> --- a/arch/arm64/boot/dts/qcom/nord.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/nord.dtsi
>> @@ -1029,6 +1029,28 @@ smp2p_cdsp3_in: slave-kernel {
>> };
>> };
>>
>> + smp2p-soccp {
>> + compatible = "qcom,smp2p";
>> + interrupts-extended = <&ipcc0 IPCC_MPROC_SOCCP
>> + IPCC_MPROC_SIGNAL_SMP2P
>> + IRQ_TYPE_EDGE_RISING>;
>> + mboxes = <&ipcc0 IPCC_MPROC_SOCCP IPCC_MPROC_SIGNAL_SMP2P>;
>> + qcom,smem = <617>, <616>;
>> + qcom,local-pid = <0>;
>> + qcom,remote-pid = <19>;
>> +
>> + smp2p_soccp_out: master-kernel {
>> + qcom,entry-name = "master-kernel";
>> + #qcom,smem-state-cells = <1>;
>> + };
>> +
>> + smp2p_soccp_in: slave-kernel {
>> + qcom,entry-name = "slave-kernel";
>> + interrupt-controller;
>> + #interrupt-cells = <2>;
>> + };
>> + };
>> +
>> soc: soc@0 {
>> compatible = "simple-bus";
>> #address-cells = <2>;
>> @@ -1587,6 +1609,41 @@ uart13: serial@a98000 {
>> };
>> };
>>
>> + remoteproc_soccp: remoteproc@d00000 {
>> + compatible = "qcom,nord-soccp-pas";
>
> It causes CHECK_DTBS complaints for nord-ride.dtb, so we may want to move
> the compatible to nord-embedded.dtsi.
>
> Shawn
Yes. I will add this compatible to nord-embedded.dtsi in next version.
Anurag
>
>> + reg = <0x0 0x00d00000 0x0 0x200000>;
>> +
>> + interrupts-extended = <&intc GIC_SPI 167 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 0 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 1 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 2 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 3 IRQ_TYPE_EDGE_RISING>,
>> + <&smp2p_soccp_in 9 IRQ_TYPE_EDGE_RISING>;
>> + interrupt-names = "wdog",
>> + "fatal",
>> + "ready",
>> + "handover",
>> + "stop-ack",
>> + "pong";
>> +
>> + memory-region = <&soccp_mem>;
>> +
>> + qcom,smem-states = <&smp2p_soccp_out 0>,
>> + <&smp2p_soccp_out 8>;
>> + qcom,smem-state-names = "stop",
>> + "ping";
>> +
>> + glink-edge {
>> + interrupts-extended = <&ipcc0 IPCC_MPROC_SOCCP
>> + IPCC_MPROC_SIGNAL_GLINK_QMP
>> + IRQ_TYPE_EDGE_RISING>;
>> + mboxes = <&ipcc0 IPCC_MPROC_SOCCP
>> + IPCC_MPROC_SIGNAL_GLINK_QMP>;
>> + qcom,remote-pid = <19>;
>> + label = "soccp";
>> + };
>> + };
>> +
>> rng: rng@10c3000 {
>> compatible = "qcom,nord-trng",
>> "qcom,trng";
>>
>> --
>> 2.43.0
>>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board
2026-10-18 12:49 ` Shawn Guo
@ 2026-10-21 6:36 ` Anurag Pateriya
0 siblings, 0 replies; 8+ messages in thread
From: Anurag Pateriya @ 2026-10-21 6:36 UTC (permalink / raw)
To: Shawn Guo
Cc: Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-msm, devicetree,
linux-kernel
On 10/18/2026 6:19 PM, Shawn Guo wrote:
> On Sun, Oct 18, 2026 at 12:46:47PM +0530, Anurag Pateriya wrote:
>> Add the SoCCP remoteproc node with its firmware path on the Nord
>> RRD board.
>>
>> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/nord-rrd.dts | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/nord-rrd.dts b/arch/arm64/boot/dts/qcom/nord-rrd.dts
>> index 47978df0af92..89f8d36ed812 100644
>> --- a/arch/arm64/boot/dts/qcom/nord-rrd.dts
>> +++ b/arch/arm64/boot/dts/qcom/nord-rrd.dts
>> @@ -434,6 +434,10 @@ &spi16 {
>> status = "okay";
>> };
>>
>> +&remoteproc_soccp {
>
> In alphabetical order, I think it should go right after remoteproc_cdsp3
> rather than spi16.
>
> Shawn
Yes. Will fix it in next version.
Anurag
>
>> + firmware-name = "qcom/nord/soccp.mbn";
>> +};
>> +
>> &uart4 {
>> status = "okay";
>> };
>>
>> --
>> 2.43.0
>>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-10-21 6:36 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-18 7:16 [PATCH RFC v2 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya
2026-10-19 6:34 ` Shawn Guo
2026-10-21 6:35 ` Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 2/3] arm64: dts: qcom: nord: Add SoCCP on RRD board Anurag Pateriya
2026-10-18 12:49 ` Shawn Guo
2026-10-21 6:36 ` Anurag Pateriya
2026-10-18 7:16 ` [PATCH RFC v2 3/3] arm64: dts: qcom: nord: Add SoCCP on Ride-Embedded board Anurag Pateriya
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®