From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v4 6/6] firmware: qcom: scm: introduce keep_mdt_buf flag in PAS context
Date: Tue, 30 Jun 2026 12:39:12 +0200 [thread overview]
Message-ID: <1c5c6399-e4cb-4d33-8fb7-fdfde0b33e19@oss.qualcomm.com> (raw)
In-Reply-To: <20260430191253.4052025-7-mukesh.ojha@oss.qualcomm.com>
On 4/30/26 9:12 PM, Mukesh Ojha wrote:
> The PAS image initialization path always retains the metadata buffer
> when a valid qcom_scm_pas_context is provided, even if the caller does
> not require it. This implicit behavior leads to unclear buffer ownership
> and forces new users of qcom_mdt_pas_load() to manually release
> metadata, which is error‑ prone and incorrect.
>
> Add a keep_mdt_buf flag to struct qcom_scm_pas_context to make metadata
> retention explicit. Metadata buffers are now freed by default and are
> only preserved when this flag is set. qcom_q6v5_pas enables this during
> probe for contexts that require retained metadata for subsequent PAS
> operations, while existing callers continue to work unchanged.
>
> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> ---
[...]
> ret = __qcom_scm_pas_init_image(pas_id, mdata_phys, &res);
> - if (ret < 0 || !ctx) {
> +
> + /*
> + * Some clients still pass the PAS context as NULL. Until all clients
> + * switch to qcom_mdt_pas_load() and provide a valid PAS context, check
> + * for NULL before dereferencing it.
> + *
> + * When a valid context is provided, metadata handling differs across
> + * clients. For example, modem clients pass metadata to TrustZone that
> + * must not be freed until the authentication and reset SMCs are
> + * invoked, as the buffers remain locked until then.
> + *
> + * Other clients free their metadata immediately after the PAS_INIT
> + * SMC call. Therefore, keep_mdt_buf should be set to true for modem
> + * clients and false for others.
You say this...
[...]
> --- a/drivers/remoteproc/qcom_q6v5_pas.c
> +++ b/drivers/remoteproc/qcom_q6v5_pas.c
> @@ -669,6 +669,7 @@ static int qcom_pas_alloc_memory_region(struct qcom_pas *pas)
> return PTR_ERR(pas->pas_ctx);
>
> pas->pas_ctx->use_tzmem = rproc->has_iommu;
> + pas->pas_ctx->keep_mdt_buf = true;
> if (!pas->dtb_pas_id)
> return 0;
>
> @@ -688,6 +689,7 @@ static int qcom_pas_alloc_memory_region(struct qcom_pas *pas)
> return PTR_ERR(pas->dtb_pas_ctx);
>
> pas->dtb_pas_ctx->use_tzmem = rproc->has_iommu;
> + pas->dtb_pas_ctx->keep_mdt_buf = true;
And you set it globally for all PAS rprocs
Konrad
next prev parent reply other threads:[~2026-06-30 10:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 19:12 [PATCH v4 0/6] remoteproc: qcom: pas: Misc fixes Mukesh Ojha
2026-04-30 19:12 ` [PATCH v4 1/6] remoteproc: qcom: fix sparse warnings for __iomem annotated mem_region Mukesh Ojha
2026-06-18 13:53 ` Konrad Dybcio
2026-06-22 15:50 ` Mukesh Ojha
2026-07-06 17:31 ` Mukesh Ojha
2026-04-30 19:12 ` [PATCH v4 2/6] remoteproc: qcom: pas: Guard dtb metadata release with dtb_pas_id check Mukesh Ojha
2026-07-06 18:00 ` Dmitry Baryshkov
2026-04-30 19:12 ` [PATCH v4 3/6] remoteproc: qcom: pas: Fix the PAS context creation placement Mukesh Ojha
2026-07-06 18:02 ` Dmitry Baryshkov
2026-04-30 19:12 ` [PATCH v4 4/6] remoteproc: qcom: pas: Map/unmap subsystem region before auth_and_reset Mukesh Ojha
2026-06-24 11:45 ` Konrad Dybcio
2026-07-06 18:07 ` Dmitry Baryshkov
2026-04-30 19:12 ` [PATCH v4 5/6] remoteproc: qcom: pas: Drop unused dtb_mem_region field Mukesh Ojha
2026-06-24 11:47 ` Konrad Dybcio
2026-07-06 18:10 ` Dmitry Baryshkov
2026-04-30 19:12 ` [PATCH v4 6/6] firmware: qcom: scm: introduce keep_mdt_buf flag in PAS context Mukesh Ojha
2026-06-30 10:39 ` Konrad Dybcio [this message]
2026-06-30 11:14 ` Mukesh Ojha
2026-07-06 18:13 ` Dmitry Baryshkov
2026-07-07 7:38 ` Mukesh Ojha
2026-06-08 16:18 ` [PATCH v4 0/6] remoteproc: qcom: pas: Misc fixes Mukesh Ojha
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=1c5c6399-e4cb-4d33-8fb7-fdfde0b33e19@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mukesh.ojha@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
all inboxes | Powered by JetHome®