All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Li <ye.li@oss.nxp.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Richard Weinberger <richard@sigma-star.at>,
	u-boot@lists.denx.de, alice.guo@nxp.com, peng.fan@nxp.com,
	upstream+uboot@sigma-star.at, ye.li@nxp.com
Subject: Re: TZASC misconfiguration on i.mx8m
Date: Fri, 12 Jun 2026 17:59:02 +0800	[thread overview]
Message-ID: <7b4ffed3-3321-43ba-932b-e59a8793e95f@oss.nxp.com> (raw)
In-Reply-To: <CAOMZO5AOMGgf-iHL-504ZTLjG4-_LhrPAMQbG48tuqfrEVamwQ@mail.gmail.com>

Hi Fabio,

On 6/11/2026 10:53 PM, Fabio Estevam wrote:
> Hi Ye Li,
> 
> On Sun, Jun 7, 2026 at 10:53 PM Ye Li <ye.li@oss.nxp.com> wrote:
> 
>> We have discussed this with iMX optee owner. The fix should be done in
>> OPTEE not u-boot.
>> 1. OPTEE uses secure memory, so it needs to re-confiure trustzone to
>> meet secure requirement not depending on SPL setting.
>> 2. SPL also supports Non-optee case.
> 
> Does NXP plan to fix this?
> 
> Thanks

Sahil has sent patch to optee community. We are still discussing it. In 
any case, this SPL patch can't be simply reverted, it will cause 
regression to SW running in normal world.

Best regards,
Ye Li


      reply	other threads:[~2026-06-12  9:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 17:24 TZASC misconfiguration on i.mx8m Richard Weinberger
2026-06-05 14:52 ` Richard Weinberger
2026-06-08  1:42   ` Ye Li
2026-06-08  3:07     ` Richard Weinberger
2026-06-09  1:44       ` Ye Li
2026-06-09  6:53         ` Richard Weinberger
2026-06-09  9:56           ` Ye Li
2026-06-09  9:58             ` Richard Weinberger
2026-06-09 10:12               ` Ye Li
2026-06-09 10:15                 ` Richard Weinberger
2026-06-10  7:21                   ` [EXT] " Sahil Malhotra
2026-06-11 14:53     ` Fabio Estevam
2026-06-12  9:59       ` Ye Li [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=7b4ffed3-3321-43ba-932b-e59a8793e95f@oss.nxp.com \
    --to=ye.li@oss.nxp.com \
    --cc=alice.guo@nxp.com \
    --cc=festevam@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=richard@sigma-star.at \
    --cc=u-boot@lists.denx.de \
    --cc=upstream+uboot@sigma-star.at \
    --cc=ye.li@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.