Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: eliza-mtp: Enable CDSP remoteproc
Date: Tue, 14 Jul 2026 13:49:55 +0000	[thread overview]
Message-ID: <20260714134955.CFFC51F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260714-dts-qcom-eliza-add-cdsp-v1-2-525e757a23b0@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `remoteproc_cdsp` node is missing the `glink-edge` subnode required for IPC.
--

--- Patch [2]: [PATCH 2/3] arm64: dts: qcom: eliza-mtp: Enable CDSP remoteproc ---
commit 5af49a73d9e2d56636adad16779d928f64bfc0a3
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>

arm64: dts: qcom: eliza-mtp: Enable CDSP remoteproc

This commit enables the CDSP remoteproc node on the Eliza MTP. It provides 
the required firmware names and sets the status to okay to bring the DSP out 
of reset.

> diff --git a/arch/arm64/boot/dts/qcom/eliza-mtp.dts b/arch/arm64/boot/dts/qcom/eliza-mtp.dts
> index a7d6f9d52ef31..7de4ee3935e63 100644
> --- a/arch/arm64/boot/dts/qcom/eliza-mtp.dts
> +++ b/arch/arm64/boot/dts/qcom/eliza-mtp.dts
> @@ -484,6 +484,13 @@ &remoteproc_adsp {
>  	status = "okay";
>  };
>  
> +&remoteproc_cdsp {
> +	firmware-name = "qcom/eliza/cdsp.mbn",
> +			"qcom/eliza/cdsp_dtb.mbn";
> +
> +	status = "okay";
> +};

[Severity: Medium]
Is this missing the glink-edge subnode required for IPC?

Looking at the base device tree definition in 
arch/arm64/boot/dts/qcom/eliza.dtsi, the remoteproc_cdsp node is defined 
without a glink-edge child node:

	remoteproc_cdsp: remoteproc@32300000 {
		compatible = "qcom,eliza-cdsp-pas";
...
		qcom,smem-states = <&smp2p_cdsp_out 0>;
		qcom,smem-state-names = "stop";

		status = "disabled";
	};

Without this subnode, qcom_glink_smem won't be instantiated for the CDSP. 
Will this leave the DSP functionally isolated since the host cannot establish 
RPMSG IPC channels (like fastrpcglink-apps-dsp) to perform compute offloading?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-dts-qcom-eliza-add-cdsp-v1-0-525e757a23b0@oss.qualcomm.com?part=2

  reply	other threads:[~2026-07-14 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 13:06 [PATCH 0/3] arm64: dts: qcom: eliza: Add CDSP support and enable it on MTP and CQS SoM Abel Vesa
2026-07-14 13:06 ` [PATCH 1/3] arm64: dts: qcom: eliza: Describe the CDSP remoteproc Abel Vesa
2026-07-14 13:06 ` [PATCH 2/3] arm64: dts: qcom: eliza-mtp: Enable " Abel Vesa
2026-07-14 13:49   ` sashiko-bot [this message]
2026-07-14 13:06 ` [PATCH 3/3] arm64: dts: qcom: eliza-cqs-som: " Abel Vesa

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=20260714134955.CFFC51F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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