From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vishwas Udupa <vishwas.udupa@oss.qualcomm.com>
Cc: andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, kbajaj@qti.qualcomm.com,
konradybcio@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, robh@kernel.org,
snb@qti.qualcomm.com, vudupa@qti.qualcomm.com
Subject: Re: [PATCH] arm64: dts: qcom: install DT overlays via dtbs_install
Date: Tue, 16 Jun 2026 05:49:32 +0200 [thread overview]
Message-ID: <ce96a826-08ce-4e63-a794-26d9600f73f4@kernel.org> (raw)
In-Reply-To: <20260615162739.787779-1-vishwas.udupa@oss.qualcomm.com>
On 15/06/2026 18:27, Vishwas Udupa wrote:
> EL2 DTBOs are used at build time to construct DTBs corresponding to
> an EL2 (hypervisor-enabled) boot configuration. These DTBs are included in
> distributions [1] as complete boot configurations (e.g. EL1 and EL2).
>
> The EL2 configuration is not enabled by default and is typically selected
> after the initial boot by updating a UEFI runtime variable from userspace.
> Once set, firmware selects the prebuilt EL2 DTB on subsequent boots.
>
> Although EL2 DTBOs are not used directly at runtime during initial boot,
> they are required to generate and package the EL2 DTBs in the image so that
> firmware can switch to EL2 when the configuration variable is enabled. Hence, el2 dtbo's
> need to be retained.
>
> 1: https://github.com/qualcomm-linux/qcom-dtb-metadata/blob/main/qcom-next-fitimage.its#L273
You cut entire context making any discussion very difficult.
Anyway, comment stays. EL2 is not an overlay. If I need to repeat
myself, then let's do like:
NAK
Best regards,
Krzysztof
prev parent reply other threads:[~2026-06-16 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 12:37 [PATCH] arm64: dts: qcom: install DT overlays via dtbs_install Vishwas Udupa
2026-06-15 5:00 ` Krzysztof Kozlowski
2026-06-15 16:27 ` Vishwas Udupa
2026-06-16 3:49 ` Krzysztof Kozlowski [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=ce96a826-08ce-4e63-a794-26d9600f73f4@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kbajaj@qti.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=snb@qti.qualcomm.com \
--cc=vishwas.udupa@oss.qualcomm.com \
--cc=vudupa@qti.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