On 11/21/25 12:01 PM, Mukesh Ojha wrote: > Qualcomm remote processor may rely on static and dynamic resources for > it to be functional. 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 from SMC call along with dynamic > resources. > > Remoteproc already has method like rproc_elf_load_rsc_table() to check > firmware binary has resources or not and if it is not having then we > pass NULL and zero as input resource table and its size argument > respectively to qcom_scm_pas_get_rsc_table() and while it has resource > present then it should pass the present resources to Trustzone(TZ) so that > it could authenticate the present resources and append dynamic resource > to return in output_rt argument along with authenticated resources. > > Extend parse_fw callback to include SMC call to get resources from > Trustzone and to leverage resource table parsing and mapping and > unmapping code from the remoteproc framework. > > Signed-off-by: Mukesh Ojha <[email protected]> > ---
Reviewed-by: Konrad Dybcio <[email protected]> Konrad
