Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Shawn Guo" <shengchao.guo@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] remoteproc: qcom: pas: Add Nord ADSP and CDSP support
Date: Fri, 24 Jul 2026 11:10:25 +0000	[thread overview]
Message-ID: <20260724111026.6D7751F04290@smtp.kernel.org> (raw)
In-Reply-To: <20260724103848.233804-4-shengchao.guo@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect `crash_reason_smem` value for `nord_cdsp3_resource`.
--

--- Patch [3]: [PATCH v2 3/3] remoteproc: qcom: pas: Add Nord ADSP and CDSP support ---
commit e1a98d51f6d64eea0602e8e964394bba2b37262b
Author: Shawn Guo <shengchao.guo@oss.qualcomm.com>

remoteproc: qcom: pas: Add Nord ADSP and CDSP support

This commit adds support for the ADSP and four CDSPs found on the Qualcomm 
Nord SoC. It configures the ADSP for early boot and sets up the necessary 
resource structures for all five DSPs.

> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index 25599d7282083..6f3850a3fa9e8 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c

[ ... ]

> +static const struct qcom_pas_data nord_cdsp3_resource = {
> +	.crash_reason_smem = 666,

[Severity: Medium]
Is this SMEM item ID correct?

The sequence for the other CDSPs increases by 32:
nord_cdsp0_resource: 601
nord_cdsp1_resource: 633
nord_cdsp2_resource: 665

If that pattern holds, should this be 697 instead of 666?

Querying the wrong SMEM item ID will result in a failure to retrieve the 
crash reason when the CDSP3 remote processor crashes.

> +	.firmware_name = "cdsp3.mdt",
> +	.dtb_firmware_name = "cdsp3_dtb.mbn",
> +	.pas_id = 58,

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260724103848.233804-1-shengchao.guo@oss.qualcomm.com?part=3

      reply	other threads:[~2026-07-24 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 10:38 [PATCH v2 0/3] Add ADSP and CDSP support for Nord SoC Shawn Guo
2026-07-24 10:38 ` [PATCH v2 1/3] dt-bindings: soc: qcom,aoss-qmp: Document Nord AOSS side channel Shawn Guo
2026-07-24 10:38 ` [PATCH v2 2/3] dt-bindings: remoteproc: qcom,nord-pas: Document Nord PAS Shawn Guo
2026-07-24 10:48   ` sashiko-bot
2026-07-24 12:19   ` Shawn Guo
2026-07-24 10:38 ` [PATCH v2 3/3] remoteproc: qcom: pas: Add Nord ADSP and CDSP support Shawn Guo
2026-07-24 11:10   ` sashiko-bot [this message]

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=20260724111026.6D7751F04290@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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