U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: sahil.malhotra@nxp.com, Ye Li <ye.li@oss.nxp.com>
Cc: U-Boot Mailing List <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: Tue, 09 Jun 2026 12:15:34 +0200	[thread overview]
Message-ID: <3324321.byNdk4fJJx@nailgun> (raw)
In-Reply-To: <25db2dd8-e381-4b4f-a90e-7a76a7b31c59@oss.nxp.com>

On Dienstag, 9. Juni 2026 12:12 Ye Li wrote:
> >> Why can't this optee patch apply to optee upstream? It is optee using
> >> secure memory, then it should be optee's responsibility to configure
> >> trustzone correctly. Optee can't depends on default value of trustzone,
> >> since trustzone is not enabled by optee.
> > 
> > Sorry for the harsh words, but that's *your* job at NXP to sort out.
> > You seem to ignore upstream.
> > 
> I'm not working in optee. As I mentioned early, NXP has decided to fix 
> it in optee. That's what you find the patch in NXP downstream tree. I 
> think Sahil will try to upstream it later.

Ok! :)
Maybe Sahil can shed light on the issue.
I find it kinda odd that NXP is only focusing on their tree despite the
upstream solution.

Thanks,
//richard

-- 
​​​​​sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT UID/VAT Nr:
ATU 66964118 | FN: 374287y



  reply	other threads:[~2026-06-09 10:15 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 [this message]
2026-06-10  7:21                   ` [EXT] " Sahil Malhotra
2026-06-11 14:53     ` Fabio Estevam
2026-06-12  9:59       ` Ye Li

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=3324321.byNdk4fJJx@nailgun \
    --to=richard@sigma-star.at \
    --cc=alice.guo@nxp.com \
    --cc=peng.fan@nxp.com \
    --cc=sahil.malhotra@nxp.com \
    --cc=u-boot@lists.denx.de \
    --cc=upstream+uboot@sigma-star.at \
    --cc=ye.li@nxp.com \
    --cc=ye.li@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox