From: sashiko-bot@kernel.org
To: "Ananthu C V" <ananthu.cv@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/3] remoteproc: qcom: pas: add needs_tzmem flag to force shmbridge creation
Date: Fri, 03 Jul 2026 12:42:10 +0000 [thread overview]
Message-ID: <20260703124211.367391F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260703-glymur-soccp-v4-1-b706c4c9b3e2@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The `kaanapali_soccp_resource` lacks the newly introduced `.needs_tzmem = true` flag, causing SHM bridge setup failures or SMMU faults for the Kaanapali SoCCP remoteproc.
--
commit 1e9c4b8af0b2474dac8304d92f260e1af8817ef5
Author: Ananthu C V <ananthu.cv@oss.qualcomm.com>
remoteproc: qcom: pas: add needs_tzmem flag to force shmbridge creation
This commit adds a needs_tzmem flag to ensure tzmem and SHM bridge setup is
performed independently of the iommu property. This is intended to prevent
SMMU faults for remoteprocs that are already running, like SoCCP.
> diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c
> index 60a4337d9e516..cd7273fbcf981 100644
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
[ ... ]
> @@ -1657,8 +1658,27 @@ static const struct qcom_pas_data kaanapali_soccp_resource = {
> .early_boot = true,
> };
[Severity: High]
Should kaanapali_soccp_resource also set .needs_tzmem = true?
The commit message explicitly states that for remoteprocs that are already
running like SoCCP, the OS must use needs_tzmem to configure tzmem
independently of the iommus property to avoid SMMU faults.
Since kaanapali_soccp_resource is also a SoCCP remoteproc, will omitting
this flag here cause SMMU faults or fail to perform the required SHM bridge
setup when probing the qcom,kaanapali-soccp-pas device?
> +static const struct qcom_pas_data glymur_soccp_resource = {
> + .crash_reason_smem = 656,
> + .firmware_name = "soccp.mbn",
> + .dtb_firmware_name = "soccp_dtb.mbn",
> + .pas_id = 51,
> + .dtb_pas_id = 0x41,
> + .proxy_pd_names = (char*[]){
> + "cx",
> + "mx",
> + NULL
> + },
> + .ssr_name = "soccp",
> + .sysmon_name = "soccp",
> + .auto_boot = true,
> + .early_boot = true,
> + .needs_tzmem = true,
> +};
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260703-glymur-soccp-v4-0-b706c4c9b3e2@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-03 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 12:31 [PATCH v4 0/3] Add remoteproc PAS loader for SoCCP on Glymur DT Ananthu C V
2026-07-03 12:31 ` [PATCH v4 1/3] remoteproc: qcom: pas: add needs_tzmem flag to force shmbridge creation Ananthu C V
2026-07-03 12:42 ` sashiko-bot [this message]
2026-07-03 12:44 ` Krzysztof Kozlowski
2026-07-03 14:35 ` Ananthu C V
2026-07-03 14:47 ` Krzysztof Kozlowski
2026-07-03 12:31 ` [PATCH v4 2/3] arm64: dts: qcom: fix SoCCP memory mappings for Glymur Ananthu C V
2026-07-03 12:37 ` sashiko-bot
2026-07-03 14:39 ` Ananthu C V
2026-07-03 12:31 ` [PATCH v4 3/3] arm64: dts: qcom: add SoCCP DT node " Ananthu C V
2026-07-03 12:41 ` sashiko-bot
2026-07-03 14:42 ` Ananthu C V
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=20260703124211.367391F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ananthu.cv@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