From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 11/14] firmware: qcom_scm: Add qcom_scm_pas_get_rsc_table() to get resource table
Date: Thu, 18 Dec 2025 14:34:27 +0100 [thread overview]
Message-ID: <646c0f6a-9d84-490b-a55c-7ff92e2b26f5@oss.qualcomm.com> (raw)
In-Reply-To: <20251217-kvm_rproc_v9-v9-11-ab7ac03e0ff1@oss.qualcomm.com>
On 12/17/25 5:34 PM, Mukesh Ojha wrote:
> Qualcomm remote processor may rely on Static and Dynamic resources for
> it to be functional. Static resources are fixed like for example,
> memory-mapped addresses required by the subsystem and dynamic
> resources, such as shared memory in DDR etc., are determined at
> runtime during the boot process.
>
> For most of the Qualcomm SoCs, when run with Gunyah or older QHEE
> hypervisor, all the resources whether it is static or dynamic, is
> managed by the hypervisor. Dynamic resources if it is present for a
> remote processor will always be coming from secure world via SMC call
> while static resources may be present in remote processor firmware
> binary or it may be coming qcom_scm_pas_get_rsc_table() SMC call along
> with dynamic resources.
>
> Some of the remote processor drivers, such as video, GPU, IPA, etc., do
> not check whether resources are present in their remote processor
> firmware binary. In such cases, the caller of this function should set
> input_rt and input_rt_size as NULL and zero respectively. Remoteproc
> framework has method to check whether firmware binary contain resources
> or not and they should be pass resource table pointer to input_rt and
> resource table size to input_rt_size and this will be forwarded to
> TrustZone for authentication. TrustZone will then append the dynamic
> resources and return the complete resource table in output_rt
>
> More about documentation on resource table format can be found in
> include/linux/remoteproc.h
>
> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> ---
[...]
> + memcpy(input_rt_tzm, input_rt, input_rt_size);
> +
> + do {
> + output_rt_tzm = qcom_tzmem_alloc(__scm->mempool, size, GFP_KERNEL);
> + if (!output_rt_tzm) {
> + ret = -ENOMEM;
> + goto free_input_rt;
> + }
> +
> + ret = __qcom_scm_pas_get_rsc_table(ctx->pas_id, input_rt_tzm,
> + input_rt_size, output_rt_tzm,
> + &size);
> + if (ret)
> + qcom_tzmem_free(output_rt_tzm);
> +
> + } while (ret == -EOVERFLOW);
This still looks shaky (do-while is convenient for calling this twice, but perhaps
the allocation could be moved to __qcom_scm_pas_get_rsc_table() since it's static
anyway, and then we can just do:
ret = __qcom_scm_pas_get_rsc_table(...)
if (ret == -EOVERFLOW) {
/* Try again with the size requested by the TZ */
ret = __qcom_scm_pas_get_rsc_table(...)
}
Other than that, it looks good (although there's still a lot of boilerplate
that we can't really get rid of with C)
Konrad
next prev parent reply other threads:[~2025-12-18 13:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 16:34 [PATCH v9 00/14] Peripheral Image Loader support for Qualcomm SoCs running Linux host at EL2 Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 01/14] dt-bindings: remoteproc: qcom,pas: Add iommus property Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 02/14] firmware: qcom_scm: Remove redundant piece of code Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 03/14] firmware: qcom_scm: Rename peripheral as pas_id Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 04/14] firmware: qcom_scm: Introduce PAS context allocator helper function Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 05/14] remoteproc: pas: Replace metadata context with PAS context structure Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 06/14] soc: qcom: mdtloader: Add PAS context aware qcom_mdt_pas_load() function Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 07/14] soc: qcom: mdtloader: Remove qcom_mdt_pas_init() from exported symbols Mukesh Ojha
2025-12-20 14:45 ` kernel test robot
2025-12-17 16:34 ` [PATCH v9 08/14] firmware: qcom_scm: Add a prep version of auth_and_reset function Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 09/14] firmware: qcom_scm: Refactor qcom_scm_pas_init_image() Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 10/14] firmware: qcom_scm: Add SHM bridge handling for PAS when running without QHEE Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 11/14] firmware: qcom_scm: Add qcom_scm_pas_get_rsc_table() to get resource table Mukesh Ojha
2025-12-18 13:34 ` Konrad Dybcio [this message]
2025-12-18 16:28 ` Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 12/14] remoteproc: pas: Extend parse_fw callback to fetch resources via SMC call Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 13/14] remoteproc: qcom: pas: Enable Secure PAS support with IOMMU managed by Linux Mukesh Ojha
2025-12-17 16:34 ` [PATCH v9 14/14] arm64: dts: qcom: Add EL2 overlay for Lemans 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=646c0f6a-9d84-490b-a55c-7ff92e2b26f5@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=robh@kernel.org \
/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®