From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: i.MX93: ele: make A0 firmware optional
Date: Fri, 31 Jan 2025 13:39:18 +0100 [thread overview]
Message-ID: <Z5zEdpqeoN_W9FqR@pengutronix.de> (raw)
In-Reply-To: <20250128154531.1172019-1-m.grzeschik@pengutronix.de>
On Tue, Jan 28, 2025 at 04:45:31PM +0100, Michael Grzeschik wrote:
> Since the A0 firmare is not located in the firmware-ele-imx-0.1.0.bin
> anymore it is better to make it optional. We add a reference to where
> to find the latest version of the firmware in case someone still
> uses it.
>
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> arch/arm/mach-imx/ele.c | 2 ++
> firmware/Kconfig | 11 +++++++++--
> firmware/Makefile | 2 +-
> 3 files changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-imx/ele.c b/arch/arm/mach-imx/ele.c
> index c209f53de4..ec0fd65216 100644
> --- a/arch/arm/mach-imx/ele.c
> +++ b/arch/arm/mach-imx/ele.c
> @@ -200,9 +200,11 @@ int imx93_ele_load_fw(void *bl33)
> rev = FIELD_GET(ELE_INFO_SOC_REV, info.soc);
>
> switch (rev) {
> +#ifdef CONFIG_FIRMWARE_IMX93_OPTEE_A0
> case 0xa0:
> get_builtin_firmware_ext(mx93a0_ahab_container_img, bl33, &firmware, &size);
> break;
> +#endif
> case 0xa1:
> get_builtin_firmware_ext(mx93a1_ahab_container_img, bl33, &firmware, &size);
> break;
> diff --git a/firmware/Kconfig b/firmware/Kconfig
> index d068e6d983..00546e8706 100644
> --- a/firmware/Kconfig
> +++ b/firmware/Kconfig
> @@ -81,10 +81,17 @@ config FIRMWARE_IMX93_OPTEE
> in CONFIG_EXTRA_FIRMWARE_DIR/imx93-bl32.bin. When this option is enabled then
> the TF-A binary will be used from CONFIG_EXTRA_FIRMWARE_DIR/imx93-bl31.bin-optee.
> Additionally OP-TEE requires a RAM firmware loaded into the ELE. This is expected
> - in CONFIG_EXTRA_FIRMWARE_DIR/mx93a0-ahab-container.img and
> - CONFIG_EXTRA_FIRMWARE_DIR/mx93a1-ahab-container.img. You can obtain it from
> + in CONFIG_EXTRA_FIRMWARE_DIR/mx93a1-ahab-container.img. You can obtain it from
> https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.0.bin
There's https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.1.bin now.
I took the chance to update the link accordingly.
>
> +config FIRMWARE_IMX93_OPTEE_A0
> + bool "install OP-TEE on i.MX93 older A0 revision boards"
> + depends on FIRMWARE_IMX93_OPTEE
> + help
> + Additionally OP-TEE requires a RAM firmware loaded into the ELE. This is expected
> + in CONFIG_EXTRA_FIRMWARE_DIR/mx93a0-ahab-container.img. You can obtain it from
> + https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-sentinel-0.11.bin
firmware-sentinel is the old package name. It has been renamed to
firmware-ele-imx and there is a version of that package that still
contains the A0 ELE firmware binary:
https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.0.bin
I updated the link accordingly.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-01-31 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 15:45 Michael Grzeschik
2025-01-31 12:36 ` Sascha Hauer
2025-01-31 12:39 ` Sascha Hauer [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=Z5zEdpqeoN_W9FqR@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.grzeschik@pengutronix.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