Re: [PATCH] arm64: dts: qcom: hamoa: Add remoteproc in EL2 device trees
From: Xin Liu
Date: Sun Feb 01 2026 - 21:19:42 EST
On 1/30/2026 5:37 PM, Xilin Wu wrote:
On 1/30/2026 3:31 PM, Xin Liu wrote:Hi,Xilin
All the existing variants Talos boards are using Gunyah hypervisor
which means that, so far, Linux-based OS could only boot in EL1 on
those devices. However, it is possible for us to boot Linux at EL2
on these devices [1].
When running under Gunyah, the remote processor firmware IOMMU streams
are controlled by Gunyah. However, without Gunyah, the IOMMU is managed
by the consumer of this DeviceTree. Therefore, describe the firmware
streams for each remote processor.
Add remoteproc to the EL2 device trees to generate the corresponding
-el2.dtb files.
[1]
https://docs.qualcomm.com/bundle/publicresource/topics/80-70020-4/boot-developer-touchpoints.html#uefi
Signed-off-by: Xin Liu <xin.liu@xxxxxxxxxxxxxxxx>
---
arch/arm64/boot/dts/qcom/x1-el2.dtso | 8 ++++++++
1 file changed, 8 insertions(+)
Hi Xin,
Will this work on Snapdragon X laptops running the older Windows firmware? I believe that Peripheral Image Loader support in EL2 requires a newer version of the TrustZone firmware.
I noticed that the TrustZone firmware used in hamoa_iot-ubuntu [1] has a different version string compared to the WP firmware found in laptops:
iot-ubuntu: TZ.XF.5.0
WP: TZ.XF.5.28.1
[1] https://softwarecenter.qualcomm.com/nexus/generic/software/chip/ubuntu_qualcomm_iot-spf-1-0/ubuntu-qualcomm-iot-spf-1-0_test_device_public/r1.0.r1_00004.0/hamoa_iot-ubun-1-0-r1/common/build/bin
Now firmware can not work, still need TZ team to modify some things. It is the only modification from kernel side, so I update it.
Uploading this modification will also facilitate debugging by TZ team.
Thanks,
Xin