From: Marek Vasut <marek.vasut@mailbox.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Andre Przywara <andre.przywara@arm.com>,
Caleb Connolly <caleb.connolly@linaro.org>,
Igor Opaniuk <igor.opaniuk@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Julien Masson <jmasson@baylibre.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Maxim Moskalets <maximmosk4@gmail.com>,
Michael Walle <mwalle@kernel.org>,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
Paul-Erwan Rio <paulerwan.rio@gmail.com>,
Peter Hoyes <Peter.Hoyes@arm.com>,
Raymond Mao <raymond.mao@linaro.org>,
Sam Protsenko <semen.protsenko@linaro.org>,
Simon Glass <sjg@chromium.org>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 2/3] image: Add support for starting TFA BL31 as fitImage loadables
Date: Mon, 13 Jan 2025 13:39:38 +0100 [thread overview]
Message-ID: <4dddca99-dcc2-411e-af9a-b27115e60efa@mailbox.org> (raw)
In-Reply-To: <TY3PR01MB113468B93D55B10C9D38ABFAE861F2@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On 1/13/25 1:15 PM, Biju Das wrote:
> Hi Marex,
>
> Thanks for the patch
>
>> -----Original Message-----
>> From: U-Boot <u-boot-bounces@lists.denx.de> On Behalf Of Marek Vasut
>> Sent: 12 January 2025 22:37
>> Subject: [PATCH 2/3] image: Add support for starting TFA BL31 as fitImage loadables
>>
>> Add support for starting TFA from U-Boot running in EL3 as part of fitImage boot, so the user can
>> start U-Boot in the highest privilege level on the platform, bundle TFA, Linux, DT into a single
>> fitImage and boot such a bundle as a whole.
>>
>> There are two main benefits of this approach. First is the ability to run U-Boot in EL3, where it has
>> unrestricted access to the entire system and can act as a useful debug tool, as it was always intended
>> to be used. Second is the ability to easily and safely update of any component in the fitImage, be it
>> TFA, Linux or DT.
>
> In this case, who will do switching from secure world to normal world, u-boot?
> Do you have any link to the u-boot patch from secure to normal world switching
> with kernel entry point passed to BL31?
>
> Otherwise, kernel, also will be executing in secure world mode.
See 3/3 , U-Boot runs in EL3 , before starting kernel it jumps into TFA
BL31 , TFA BL31 does its setup and switches from EL3 to EL2 , TFA BL31
returns to U-Boot armv8_switch_to_el2 which checks if this code is
running in EL2 (it is) and does the last few steps before starting
kernel, and then finally jumps to the kernel .
next prev parent reply other threads:[~2025-01-13 12:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 22:36 [PATCH 1/3] arm64: Add late jump to kernel board hook Marek Vasut
2025-01-12 22:36 ` [PATCH 2/3] image: Add support for starting TFA BL31 as fitImage loadables Marek Vasut
2025-01-13 12:15 ` Biju Das
2025-01-13 12:39 ` Marek Vasut [this message]
2025-01-13 13:31 ` Biju Das
2025-01-15 11:51 ` Quentin Schulz
2025-01-18 13:49 ` Marek Vasut
2025-01-15 1:13 ` Tom Rini
2025-01-29 17:10 ` Quentin Schulz
2025-01-29 17:38 ` Marek Vasut
2025-01-29 17:51 ` Quentin Schulz
2025-07-21 21:43 ` Marek Vasut
2025-01-12 22:36 ` [PATCH 3/3] arm64: renesas: Add TFA BL31 handoff support Marek Vasut
2025-01-29 16:02 ` Quentin Schulz
2025-01-29 16:28 ` Quentin Schulz
2025-01-29 17:03 ` Marek Vasut
2025-01-29 17:00 ` Marek Vasut
2025-01-29 17:32 ` Quentin Schulz
2025-01-15 1:13 ` [PATCH 1/3] arm64: Add late jump to kernel board hook Tom Rini
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=4dddca99-dcc2-411e-af9a-b27115e60efa@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=Peter.Hoyes@arm.com \
--cc=andre.przywara@arm.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=caleb.connolly@linaro.org \
--cc=igor.opaniuk@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=iwamatsu@nigauri.org \
--cc=jmasson@baylibre.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=maximmosk4@gmail.com \
--cc=mkorpershoek@baylibre.com \
--cc=mwalle@kernel.org \
--cc=patrick.rudolph@9elements.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=paulerwan.rio@gmail.com \
--cc=raymond.mao@linaro.org \
--cc=semen.protsenko@linaro.org \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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