public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: u-boot@lists.denx.de, 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>
Subject: Re: [PATCH 2/3] image: Add support for starting TFA BL31 as fitImage loadables
Date: Tue, 14 Jan 2025 19:13:42 -0600	[thread overview]
Message-ID: <20250115011342.GS3476@bill-the-cat> (raw)
In-Reply-To: <20250112223755.179959-2-marek.vasut+renesas@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]

On Sun, Jan 12, 2025 at 11:36:58PM +0100, Marek Vasut wrote:

> 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.
> 
> The boot process is similar to regular Linux with DT fitImage boot
> process, except the TFA has to be bundled into the fitImage. For the
> bundling instructions, see below. The TFA is started as a 'loadables'
> with custom U_BOOT_FIT_LOADABLE_HANDLER and armv8_switch_to_el2_prep()
> handling implemented in board code, and performing the handoff and
> boot in case the TFA was loaded.
> 
> The loadables handler is optional and meant to set up any sort of
> handoff structures used by the TFA BL31 or perform any other setup
> that is needed by the blob. The custom armv8_switch_to_el2_prep()
> has to implement the jump to TFA BL31 with return to U-Boot just
> before booting the Linux kernel.
> 
> Example fitImage image and configuration section:
> 
> /dts-v1/;
> 
> / {
>     description = "Linux kernel with FDT blob and TFA BL31";
> 
>     images {
>         kernel-1 { ... };
>         fdt-1 { ... };
>         atf-1 {                  /* This is the TFA BL31 image */
>             description = "TFA BL31";
>             data = /incbin/("../build/plat/release/bl31.bin");
>             type = "tfa-bl31";
>             arch = "arm64";
>             os = "arm-trusted-firmware";
>             compression = "none";
>             load = <0x46400000>;
>             entry = <0x46400000>;
>         };
>     };
> 
>     configurations {
>         default = "conf-1";
>         conf-1 {
>             description = "Boot Linux";
>             kernel = "kernel-1";
>             fdt = "fdt-1";
>             loadables = "atf-1"; /* This is the TFA BL31 loadable */
>         };
>     };
> };
> 
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2025-01-15  1:14 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
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 [this message]
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=20250115011342.GS3476@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=Peter.Hoyes@arm.com \
    --cc=andre.przywara@arm.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=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