[PATCH 0/2] Add binding and driver for Nord SoCCP

[PATCH 0/2] Add binding and driver for Nord SoCCP

[Anurag Pateriya]

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.

Signed-off-by: Anurag Pateriya <anurag.pateriya@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>

[PATCH 1/2] dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add Nord SoCCP

[Anurag Pateriya]

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

Re: [PATCH 1/2] dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add Nord SoCCP

[Shawn Guo]

On Fri, Oct 09, 2026 at 01:05:39PM +0530, Anurag Pateriya wrote:
> 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>

Reviewed-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>

Re: [PATCH 1/2] dt-bindings: remoteproc: qcom,kaanapali-soccp-pas: Add Nord SoCCP

[Rob Herring (Arm)]

On Fri, 09 Oct 2026 13:05:39 +0530, Anurag Pateriya wrote:
> 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(+)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>

[PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Anurag Pateriya]

The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
USB Type-C, battery charging and various other functions on Qualcomm SoCs.
It provides a solution for control-plane processing, reducing per-subsystem
microcontroller reinvention. Add support for SoCCP PAS loader on Nord
platform

Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
---
 drivers/remoteproc/qcom_q6v5_pas.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
index a005546c265d..6fa958044218 100644
--- a/drivers/remoteproc/qcom_q6v5_pas.c
+++ b/drivers/remoteproc/qcom_q6v5_pas.c
@@ -1545,6 +1545,20 @@ static const struct qcom_pas_data nord_cdsp3_resource = {
 	.smem_host_id = 197,
 };
 
+static const struct qcom_pas_data nord_soccp_resource = {
+	.crash_reason_smem = 656,
+	.firmware_name = "soccp.mbn",
+	.pas_id = 51,
+	.proxy_pd_names = (char*[]){
+		"cx",
+		"mx",
+		NULL
+	},
+	.ssr_name = "soccp",
+	.sysmon_name = "soccp",
+	.auto_boot = true,
+};
+
 static const struct qcom_pas_data sm8450_mpss_resource = {
 	.crash_reason_smem = 421,
 	.firmware_name = "modem.mdt",
@@ -1844,6 +1858,7 @@ static const struct of_device_id qcom_pas_of_match[] = {
 	{ .compatible = "qcom,nord-cdsp1-pas", .data = &nord_cdsp1_resource },
 	{ .compatible = "qcom,nord-cdsp2-pas", .data = &nord_cdsp2_resource },
 	{ .compatible = "qcom,nord-cdsp3-pas", .data = &nord_cdsp3_resource },
+	{ .compatible = "qcom,nord-soccp-pas", .data = &nord_soccp_resource },
 	{ .compatible = "qcom,qcs404-adsp-pas", .data = &adsp_resource_init },
 	{ .compatible = "qcom,qcs404-cdsp-pas", .data = &cdsp_resource_init },
 	{ .compatible = "qcom,qcs404-wcss-pas", .data = &wcss_resource_init },

-- 
2.43.0

Re: [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Shawn Guo]

On Fri, Oct 09, 2026 at 01:05:40PM +0530, Anurag Pateriya wrote:
> The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
> USB Type-C, battery charging and various other functions on Qualcomm SoCs.

Are you sure about this? It doesn't seem to match what cover letter
tells.

Shawn

> It provides a solution for control-plane processing, reducing per-subsystem
> microcontroller reinvention. Add support for SoCCP PAS loader on Nord
> platform
> 
> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
> ---
>  drivers/remoteproc/qcom_q6v5_pas.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index a005546c265d..6fa958044218 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
> @@ -1545,6 +1545,20 @@ static const struct qcom_pas_data nord_cdsp3_resource = {
>  	.smem_host_id = 197,
>  };
>  
> +static const struct qcom_pas_data nord_soccp_resource = {
> +	.crash_reason_smem = 656,
> +	.firmware_name = "soccp.mbn",
> +	.pas_id = 51,
> +	.proxy_pd_names = (char*[]){
> +		"cx",
> +		"mx",
> +		NULL
> +	},
> +	.ssr_name = "soccp",
> +	.sysmon_name = "soccp",
> +	.auto_boot = true,
> +};
> +
>  static const struct qcom_pas_data sm8450_mpss_resource = {
>  	.crash_reason_smem = 421,
>  	.firmware_name = "modem.mdt",
> @@ -1844,6 +1858,7 @@ static const struct of_device_id qcom_pas_of_match[] = {
>  	{ .compatible = "qcom,nord-cdsp1-pas", .data = &nord_cdsp1_resource },
>  	{ .compatible = "qcom,nord-cdsp2-pas", .data = &nord_cdsp2_resource },
>  	{ .compatible = "qcom,nord-cdsp3-pas", .data = &nord_cdsp3_resource },
> +	{ .compatible = "qcom,nord-soccp-pas", .data = &nord_soccp_resource },
>  	{ .compatible = "qcom,qcs404-adsp-pas", .data = &adsp_resource_init },
>  	{ .compatible = "qcom,qcs404-cdsp-pas", .data = &cdsp_resource_init },
>  	{ .compatible = "qcom,qcs404-wcss-pas", .data = &wcss_resource_init },
> 
> -- 
> 2.43.0
> 

Re: [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Anurag Pateriya]

On 10/9/2026 1:23 PM, Shawn Guo wrote:
> On Fri, Oct 09, 2026 at 01:05:40PM +0530, Anurag Pateriya wrote:
>> The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
>> USB Type-C, battery charging and various other functions on Qualcomm SoCs.
> 
> Are you sure about this? It doesn't seem to match what cover letter
> tells.
> 
> Shawn

Sure. will fix this in next version.

Thanks,
Anurag

> 
>> It provides a solution for control-plane processing, reducing per-subsystem
>> microcontroller reinvention. Add support for SoCCP PAS loader on Nord
>> platform
>>
>> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
>> ---
>>   drivers/remoteproc/qcom_q6v5_pas.c | 15 +++++++++++++++
>>   1 file changed, 15 insertions(+)
>>
>> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
>> index a005546c265d..6fa958044218 100644
>> --- a/drivers/remoteproc/qcom_q6v5_pas.c
>> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
>> @@ -1545,6 +1545,20 @@ static const struct qcom_pas_data nord_cdsp3_resource = {
>>   	.smem_host_id = 197,
>>   };
>>   
>> +static const struct qcom_pas_data nord_soccp_resource = {
>> +	.crash_reason_smem = 656,
>> +	.firmware_name = "soccp.mbn",
>> +	.pas_id = 51,
>> +	.proxy_pd_names = (char*[]){
>> +		"cx",
>> +		"mx",
>> +		NULL
>> +	},
>> +	.ssr_name = "soccp",
>> +	.sysmon_name = "soccp",
>> +	.auto_boot = true,
>> +};
>> +
>>   static const struct qcom_pas_data sm8450_mpss_resource = {
>>   	.crash_reason_smem = 421,
>>   	.firmware_name = "modem.mdt",
>> @@ -1844,6 +1858,7 @@ static const struct of_device_id qcom_pas_of_match[] = {
>>   	{ .compatible = "qcom,nord-cdsp1-pas", .data = &nord_cdsp1_resource },
>>   	{ .compatible = "qcom,nord-cdsp2-pas", .data = &nord_cdsp2_resource },
>>   	{ .compatible = "qcom,nord-cdsp3-pas", .data = &nord_cdsp3_resource },
>> +	{ .compatible = "qcom,nord-soccp-pas", .data = &nord_soccp_resource },
>>   	{ .compatible = "qcom,qcs404-adsp-pas", .data = &adsp_resource_init },
>>   	{ .compatible = "qcom,qcs404-cdsp-pas", .data = &cdsp_resource_init },
>>   	{ .compatible = "qcom,qcs404-wcss-pas", .data = &wcss_resource_init },
>>
>> -- 
>> 2.43.0
>>

Re: [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Konrad Dybcio]

On 10/9/26 9:35 AM, Anurag Pateriya wrote:
> The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
> USB Type-C, battery charging and various other functions on Qualcomm SoCs.

But that's not what it does on this SoC.

> It provides a solution for control-plane processing, reducing per-subsystem
> microcontroller reinvention. Add support for SoCCP PAS loader on Nord
> platform
> 
> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
> ---
>  drivers/remoteproc/qcom_q6v5_pas.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index a005546c265d..6fa958044218 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
> @@ -1545,6 +1545,20 @@ static const struct qcom_pas_data nord_cdsp3_resource = {
>  	.smem_host_id = 197,
>  };
>  
> +static const struct qcom_pas_data nord_soccp_resource = {
> +	.crash_reason_smem = 656,
> +	.firmware_name = "soccp.mbn",
> +	.pas_id = 51,
> +	.proxy_pd_names = (char*[]){
> +		"cx",
> +		"mx",
> +		NULL
> +	},
> +	.ssr_name = "soccp",
> +	.sysmon_name = "soccp",
> +	.auto_boot = true,

No DTB?

Konrad

Re: [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Anurag Pateriya]

On 10/13/2026 2:27 PM, Konrad Dybcio wrote:
> On 10/9/26 9:35 AM, Anurag Pateriya wrote:
>> The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
>> USB Type-C, battery charging and various other functions on Qualcomm SoCs.
> 
> But that's not what it does on this SoC.
> 

Yes. I will update this in next version.

>> It provides a solution for control-plane processing, reducing per-subsystem
>> microcontroller reinvention. Add support for SoCCP PAS loader on Nord
>> platform
>>
>> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
>> ---
>>   drivers/remoteproc/qcom_q6v5_pas.c | 15 +++++++++++++++
>>   1 file changed, 15 insertions(+)
>>
>> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
>> index a005546c265d..6fa958044218 100644
>> --- a/drivers/remoteproc/qcom_q6v5_pas.c
>> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
>> @@ -1545,6 +1545,20 @@ static const struct qcom_pas_data nord_cdsp3_resource = {
>>   	.smem_host_id = 197,
>>   };
>>   
>> +static const struct qcom_pas_data nord_soccp_resource = {
>> +	.crash_reason_smem = 656,
>> +	.firmware_name = "soccp.mbn",
>> +	.pas_id = 51,
>> +	.proxy_pd_names = (char*[]){
>> +		"cx",
>> +		"mx",
>> +		NULL
>> +	},
>> +	.ssr_name = "soccp",
>> +	.sysmon_name = "soccp",
>> +	.auto_boot = true,
> 
> No DTB?
> 
> Konrad

The base patch isn't merged yet for nord-ride-embedded.dts.
we need to enable for both rrd and ride-embedded boards.
I was planning to send them together once nord-ride-embedded.dts is merged.

Thanks,
Anurag

Re: [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Konrad Dybcio]

On 10/13/26 11:58 AM, Anurag Pateriya wrote:
> On 10/13/2026 2:27 PM, Konrad Dybcio wrote:
>> On 10/9/26 9:35 AM, Anurag Pateriya wrote:
>>> The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
>>> USB Type-C, battery charging and various other functions on Qualcomm SoCs.

[...]

>>>   +static const struct qcom_pas_data nord_soccp_resource = {
>>> +    .crash_reason_smem = 656,
>>> +    .firmware_name = "soccp.mbn",
>>> +    .pas_id = 51,
>>> +    .proxy_pd_names = (char*[]){
>>> +        "cx",
>>> +        "mx",
>>> +        NULL
>>> +    },
>>> +    .ssr_name = "soccp",
>>> +    .sysmon_name = "soccp",
>>> +    .auto_boot = true,
>>
>> No DTB?
>>
>> Konrad
> 
> The base patch isn't merged yet for nord-ride-embedded.dts.
> we need to enable for both rrd and ride-embedded boards.
> I was planning to send them together once nord-ride-embedded.dts is merged.

This is not my question. Remoteprocs on recent SoCs come with split
firmware - MBN for the main part and a separate DTB binary containing
configuration data.

Konrad

Re: [PATCH 2/2] remoteproc: qcom_q6v5_pas: Add remoteproc support for SOCCP on Nord

[Anurag Pateriya]

On 10/13/2026 3:33 PM, Konrad Dybcio wrote:
> On 10/13/26 11:58 AM, Anurag Pateriya wrote:
>> On 10/13/2026 2:27 PM, Konrad Dybcio wrote:
>>> On 10/9/26 9:35 AM, Anurag Pateriya wrote:
>>>> The SoC Control Processor (SoCCP) is small RISC-V MCU that controls
>>>> USB Type-C, battery charging and various other functions on Qualcomm SoCs.
> 
> [...]
> 
>>>>    +static const struct qcom_pas_data nord_soccp_resource = {
>>>> +    .crash_reason_smem = 656,
>>>> +    .firmware_name = "soccp.mbn",
>>>> +    .pas_id = 51,
>>>> +    .proxy_pd_names = (char*[]){
>>>> +        "cx",
>>>> +        "mx",
>>>> +        NULL
>>>> +    },
>>>> +    .ssr_name = "soccp",
>>>> +    .sysmon_name = "soccp",
>>>> +    .auto_boot = true,
>>>
>>> No DTB?
>>>
>>> Konrad
>>
>> The base patch isn't merged yet for nord-ride-embedded.dts.
>> we need to enable for both rrd and ride-embedded boards.
>> I was planning to send them together once nord-ride-embedded.dts is merged.
> 
> This is not my question. Remoteprocs on recent SoCs come with split
> firmware - MBN for the main part and a separate DTB binary containing
> configuration data.
> 
> Konrad

Ok , I got your question now.

For Nord, SoCCP DTB file ships firmware without a separate SoCCP 
device-tree image. 	


Thanks,
Anurag