* [PATCH RFC 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support
@ 2026-10-16 5:39 Anurag Pateriya
2026-10-16 5:39 ` [PATCH RFC 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-16 5:39 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
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>
---
Anurag Pateriya (3):
arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord
arm64: dts: qcom: nord: Enable SoCCP on RRD board
arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board
arch/arm64/boot/dts/qcom/nord-embedded.dtsi | 9 ++
arch/arm64/boot/dts/qcom/nord-ride-embedded.dts | 6 ++
arch/arm64/boot/dts/qcom/nord-rrd.dts | 6 ++
arch/arm64/boot/dts/qcom/nord.dtsi | 126 ++++++++++++++++++++++++
4 files changed, 147 insertions(+)
---
base-commit: bf2089c6d55a812b133ba2dabe59413746c2328d
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 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord 2026-10-16 5:39 [PATCH RFC 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya @ 2026-10-16 5:39 ` Anurag Pateriya 2026-10-16 8:52 ` Konrad Dybcio 2026-10-16 9:05 ` Abel Vesa 2026-10-16 5:39 ` [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board Anurag Pateriya 2026-10-16 5:39 ` [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board Anurag Pateriya 2 siblings, 2 replies; 8+ messages in thread From: Anurag Pateriya @ 2026-10-16 5:39 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 | 126 ++++++++++++++++++++++++++++ 2 files changed, 135 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..53c594281f6b 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,110 @@ 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"; + + status = "disabled"; + + 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"; + }; + }; + + bwmon_cluster2: pmu@1014400 { + reg = <0x0 0x01014400 0x0 0x600>; + interrupts = <GIC_SPI 739 IRQ_TYPE_LEVEL_HIGH>; + operating-points-v2 = <&bwmon_cluster_opp_table>; + }; + + bwmon_cluster1: pmu@1015400 { + reg = <0x0 0x01015400 0x0 0x600>; + interrupts = <GIC_SPI 812 IRQ_TYPE_LEVEL_HIGH>; + operating-points-v2 = <&bwmon_cluster_opp_table>; + }; + + bwmon_cluster0: pmu@1016400 { + reg = <0x0 0x01016400 0x0 0x600>; + interrupts = <GIC_SPI 813 IRQ_TYPE_LEVEL_HIGH>; + + operating-points-v2 = <&bwmon_cluster_opp_table>; + + bwmon_cluster_opp_table: opp-table { + compatible = "operating-points-v2"; + + opp-0 { + opp-peak-kBps = <800000>; + }; + + opp-1 { + opp-peak-kBps = <2188800>; + }; + + opp-2 { + opp-peak-kBps = <5414400>; + }; + + opp-3 { + opp-peak-kBps = <6220800>; + }; + + opp-4 { + opp-peak-kBps = <6835200>; + }; + + opp-5 { + opp-peak-kBps = <7603200>; + }; + + opp-6 { + opp-peak-kBps = <8371200>; + }; + + opp-7 { + opp-peak-kBps = <9657600>; + }; + + opp-8 { + opp-peak-kBps = <10944000>; + }; + + opp-9 { + opp-peak-kBps = <12748800>; + }; + + opp-10 { + opp-peak-kBps = <14745600>; + }; + }; + }; + rng: rng@10c3000 { compatible = "qcom,nord-trng", "qcom,trng"; -- 2.43.0 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord 2026-10-16 5:39 ` [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya @ 2026-10-16 8:52 ` Konrad Dybcio 2026-10-16 9:05 ` Abel Vesa 1 sibling, 0 replies; 8+ messages in thread From: Konrad Dybcio @ 2026-10-16 8:52 UTC (permalink / raw) To: Anurag Pateriya, Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring, Krzysztof Kozlowski, Conor Dooley Cc: linux-arm-msm, devicetree, linux-kernel, Shawn Guo On 10/16/26 7:39 AM, 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. [...] > + 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"; > + > + status = "disabled"; The SoCCP should be always enabled, especially given it's left on by the bootloader. [...] > + bwmon_cluster2: pmu@1014400 { > + reg = <0x0 0x01014400 0x0 0x600>; > + interrupts = <GIC_SPI 739 IRQ_TYPE_LEVEL_HIGH>; > + operating-points-v2 = <&bwmon_cluster_opp_table>; > + }; This is somehow present yet not mentioned at all by the commit message Konrad ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord 2026-10-16 5:39 ` [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya 2026-10-16 8:52 ` Konrad Dybcio @ 2026-10-16 9:05 ` Abel Vesa 1 sibling, 0 replies; 8+ messages in thread From: Abel Vesa @ 2026-10-16 9:05 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, Shawn Guo On 26-10-16 11:09:54, 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 | 126 ++++++++++++++++++++++++++++ > 2 files changed, 135 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..53c594281f6b 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,110 @@ 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"; > + > + status = "disabled"; > + > + 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"; > + }; > + }; > + > + bwmon_cluster2: pmu@1014400 { > + reg = <0x0 0x01014400 0x0 0x600>; > + interrupts = <GIC_SPI 739 IRQ_TYPE_LEVEL_HIGH>; > + operating-points-v2 = <&bwmon_cluster_opp_table>; > + }; This isn't supposed to be part of this patch, right? Same for the ones below. > + > + bwmon_cluster1: pmu@1015400 { > + reg = <0x0 0x01015400 0x0 0x600>; > + interrupts = <GIC_SPI 812 IRQ_TYPE_LEVEL_HIGH>; > + operating-points-v2 = <&bwmon_cluster_opp_table>; > + }; > + > + bwmon_cluster0: pmu@1016400 { > + reg = <0x0 0x01016400 0x0 0x600>; > + interrupts = <GIC_SPI 813 IRQ_TYPE_LEVEL_HIGH>; > + > + operating-points-v2 = <&bwmon_cluster_opp_table>; > + > + bwmon_cluster_opp_table: opp-table { > + compatible = "operating-points-v2"; > + > + opp-0 { > + opp-peak-kBps = <800000>; > + }; > + > + opp-1 { > + opp-peak-kBps = <2188800>; > + }; > + > + opp-2 { > + opp-peak-kBps = <5414400>; > + }; > + > + opp-3 { > + opp-peak-kBps = <6220800>; > + }; > + > + opp-4 { > + opp-peak-kBps = <6835200>; > + }; > + > + opp-5 { > + opp-peak-kBps = <7603200>; > + }; > + > + opp-6 { > + opp-peak-kBps = <8371200>; > + }; > + > + opp-7 { > + opp-peak-kBps = <9657600>; > + }; > + > + opp-8 { > + opp-peak-kBps = <10944000>; > + }; > + > + opp-9 { > + opp-peak-kBps = <12748800>; > + }; > + > + opp-10 { > + opp-peak-kBps = <14745600>; > + }; > + }; > + }; > + > rng: rng@10c3000 { > compatible = "qcom,nord-trng", > "qcom,trng"; > > -- > 2.43.0 > ^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board 2026-10-16 5:39 [PATCH RFC 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya 2026-10-16 5:39 ` [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya @ 2026-10-16 5:39 ` Anurag Pateriya 2026-10-16 8:52 ` Konrad Dybcio 2026-10-16 5:39 ` [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board Anurag Pateriya 2 siblings, 1 reply; 8+ messages in thread From: Anurag Pateriya @ 2026-10-16 5:39 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 Enable 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 | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/nord-rrd.dts b/arch/arm64/boot/dts/qcom/nord-rrd.dts index 47978df0af92..9db94c3b0c91 100644 --- a/arch/arm64/boot/dts/qcom/nord-rrd.dts +++ b/arch/arm64/boot/dts/qcom/nord-rrd.dts @@ -434,6 +434,12 @@ &spi16 { status = "okay"; }; +&remoteproc_soccp{ + firmware-name = "qcom/nord/soccp.mbn"; + + status = "okay"; +}; + &uart4 { status = "okay"; }; -- 2.43.0 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board 2026-10-16 5:39 ` [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board Anurag Pateriya @ 2026-10-16 8:52 ` Konrad Dybcio 0 siblings, 0 replies; 8+ messages in thread From: Konrad Dybcio @ 2026-10-16 8:52 UTC (permalink / raw) To: Anurag Pateriya, Bjorn Andersson, Konrad Dybcio, Abel Vesa, Rob Herring, Krzysztof Kozlowski, Conor Dooley Cc: linux-arm-msm, devicetree, linux-kernel, Shawn Guo On 10/16/26 7:39 AM, Anurag Pateriya wrote: > Enable 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 | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/arch/arm64/boot/dts/qcom/nord-rrd.dts b/arch/arm64/boot/dts/qcom/nord-rrd.dts > index 47978df0af92..9db94c3b0c91 100644 > --- a/arch/arm64/boot/dts/qcom/nord-rrd.dts > +++ b/arch/arm64/boot/dts/qcom/nord-rrd.dts > @@ -434,6 +434,12 @@ &spi16 { > status = "okay"; > }; > > +&remoteproc_soccp{ Missing space before opening bracket Konrad > + firmware-name = "qcom/nord/soccp.mbn"; > + > + status = "okay"; > +}; > + > &uart4 { > status = "okay"; > }; > ^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board 2026-10-16 5:39 [PATCH RFC 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya 2026-10-16 5:39 ` [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya 2026-10-16 5:39 ` [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board Anurag Pateriya @ 2026-10-16 5:39 ` Anurag Pateriya 2026-10-16 9:03 ` Abel Vesa 2 siblings, 1 reply; 8+ messages in thread From: Anurag Pateriya @ 2026-10-16 5:39 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 Enable the SoCCP remoteproc node with its firmware path on the Nord Ride Embedded board. Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com> --- arch/arm64/boot/dts/qcom/nord-ride-embedded.dts | 6 ++++++ 1 file changed, 6 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..1206609a5030 100644 --- a/arch/arm64/boot/dts/qcom/nord-ride-embedded.dts +++ b/arch/arm64/boot/dts/qcom/nord-ride-embedded.dts @@ -419,6 +419,12 @@ &remoteproc_cdsp3 { status = "okay"; }; +&remoteproc_soccp { + firmware-name = "qcom/nord/soccp.mbn"; + + status = "okay"; +}; + &uart15 { status = "okay"; }; -- 2.43.0 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board 2026-10-16 5:39 ` [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board Anurag Pateriya @ 2026-10-16 9:03 ` Abel Vesa 0 siblings, 0 replies; 8+ messages in thread From: Abel Vesa @ 2026-10-16 9:03 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, Shawn Guo On 26-10-16 11:09:56, Anurag Pateriya wrote: > Enable the SoCCP remoteproc node with its firmware path on the Nord > Ride Embedded board. > > Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com> Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com> ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-10-16 9:05 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2026-10-16 5:39 [PATCH RFC 0/3] arm64: dts: qcom: nord: Enable SoCCP remoteproc support Anurag Pateriya 2026-10-16 5:39 ` [PATCH RFC 1/3] arm64: dts: qcom: nord: Add SoCCP remoteproc DT support for Nord Anurag Pateriya 2026-10-16 8:52 ` Konrad Dybcio 2026-10-16 9:05 ` Abel Vesa 2026-10-16 5:39 ` [PATCH RFC 2/3] arm64: dts: qcom: nord: Enable SoCCP on RRD board Anurag Pateriya 2026-10-16 8:52 ` Konrad Dybcio 2026-10-16 5:39 ` [PATCH RFC 3/3] arm64: dts: qcom: nord: Enable SoCCP on Ride-Embedded board Anurag Pateriya 2026-10-16 9:03 ` Abel Vesa
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®