From: Xin Liu <xin.liu@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, tingwei.zhang@oss.qualcomm.com,
jie.gan@oss.qualcomm.com
Subject: Re: [PATCH] arm64: dts: qcom: hamoa: Add remoteproc in EL2 device trees
Date: Mon, 2 Feb 2026 09:51:54 +0800 [thread overview]
Message-ID: <e5d87fb5-ac7b-4442-9f5d-75ecf6bae657@oss.qualcomm.com> (raw)
In-Reply-To: <5qplhwnkiwhsfr5rxzjqk4v6rtvpqkvsg7qxvrpkqd3b7vjvob@jffvv4fvvd3d>
On 1/31/2026 3:56 PM, Dmitry Baryshkov wrote:
> On Thu, Jan 29, 2026 at 11:31:13PM -0800, Xin Liu wrote:
>> All the existing variants Talos boards are using Gunyah hypervisor
> Why are you mentioning Talos here?
Thank you for your reminder. My fault, will update next version.
XIN
>
>> 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@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/x1-el2.dtso | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
prev parent reply other threads:[~2026-02-02 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 7:31 Xin Liu
2026-01-30 9:24 ` Konrad Dybcio
2026-02-02 1:46 ` Xin Liu
2026-01-30 9:37 ` Xilin Wu
2026-02-02 2:19 ` Xin Liu
2026-01-31 7:56 ` Dmitry Baryshkov
2026-02-02 1:51 ` Xin Liu [this message]
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=e5d87fb5-ac7b-4442-9f5d-75ecf6bae657@oss.qualcomm.com \
--to=xin.liu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jie.gan@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@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®