mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] arch: arm: imx: esdctl: limit ram to 1GB on imx93 in case OPTEE is enabled
Date: Tue, 24 Jun 2025 12:30:50 +0200	[thread overview]
Message-ID: <20250624103050.apwnypp2qjmf7kc6@pengutronix.de> (raw)
In-Reply-To: <20250623220009.3898126-1-m.grzeschik@pengutronix.de>

Hi Michael,

thanks for the patch.

On 25-06-24, Michael Grzeschik wrote:
> In MX93 the ELE (Edge Lock Enclave) is limited to communicate with
> messages addressed under 1.5GB. The ELE can not reach the memory between
> (0xE0000000-0xFFFFFFFF).
> 
> So we limit the usable memory in case OPTEE is used.

Out of curiosity. This limits the memory for barebox but what about
Linux? You don't want to limit memory for Linux because ELE is not
capable of using memory above 0xe0000000.

> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> 
> ---
> v1 -> v2: moved the limitation to be active in imx93_barebox_entry only
> ---
>  arch/arm/mach-imx/esdctl.c | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-imx/esdctl.c b/arch/arm/mach-imx/esdctl.c
> index 4b67b52ca45..c79d7c29245 100644
> --- a/arch/arm/mach-imx/esdctl.c
> +++ b/arch/arm/mach-imx/esdctl.c
> @@ -1046,9 +1046,20 @@ void __noreturn imx7d_barebox_entry(void *boarddata)
>  
>  void __noreturn imx93_barebox_entry(void *boarddata)
>  {
> +	resource_size_t mem = 0;
> +
>  	imx93_init_scratch_space(false);
>  	optee_set_membase(imx_scratch_get_optee_hdr());
>  
> -	barebox_arm_entry(MX9_DDR_CSD1_BASE_ADDR,
> -			  imx9_ddrc_sdram_size(), boarddata);
> +	mem = imx9_ddrc_sdram_size();
> +	/* In MX93 the ELE is limited to comunicate with messages
> +	 * under 1.5GB address space. This limits the overal memory
> +	 * to be 1GB in case OPTEE is used.
> +	 */

What is the role of OP-TEE here? Is the ELE communication done by
barebox or op-tee or both?

Regards,
  Marco

> +	if (IS_ENABLED(CONFIG_PBL_OPTEE)) {
> +	        if (mem > 0x40000000)
> +	                mem = 0x40000000;
> +	}
> +
> +	barebox_arm_entry(MX9_DDR_CSD1_BASE_ADDR, mem, boarddata);
>  }
> -- 
> 2.39.5
> 
> 
> 



  parent reply	other threads:[~2025-06-24 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 22:00 Michael Grzeschik
2025-06-24 10:26 ` Sascha Hauer
2025-06-24 10:30 ` Marco Felsch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-01  7:20 Michael Grzeschik

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=20250624103050.apwnypp2qjmf7kc6@pengutronix.de \
    --to=m.felsch@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