All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Shiva Tripathi <s-tripathi1@ti.com>, Andrew Davis <afd@ti.com>,
	Francesco Dolcini <francesco@dolcini.it>
Cc: Ernest Van Hoecke <ernestvanhoecke@gmail.com>,
	trini@konsulko.com, vigneshr@ti.com, bb@ti.com,
	u-boot@lists.denx.de, u-kumar1@ti.com, praneeth@ti.com,
	kamlesh@ti.com, vishalm@ti.com, k-malarvizhi@ti.com,
	anshuld@ti.com
Subject: Re: [PATCH v2] arm: k3: Kconfig: Enable fTPM and RPMB support
Date: Fri, 22 May 2026 08:15:15 +0200	[thread overview]
Message-ID: <20260522061515.GA8642@francesco-nb> (raw)
In-Reply-To: <20260513142336.GA123538@francesco-nb> <b42fe4a0-a0f3-4773-be29-ac881c750799@ti.com> <677d1d7c-8276-44f2-b563-d2b0d0a263ea@ti.com>


Hello Shiva, Andrew

On Wed, May 13, 2026 at 06:36:40PM +0530, Shiva Tripathi wrote:
> It's not expected for all K3-platforms to build OP-TEE with RPMB
> support, some platforms lack eMMC entirely. fTPM is an optional
> configuration for users who need measured boot, disk encryption, or
> similar TPM related use-cases.
> 
> The Yocto SDK we release for K3 platforms includes the fTPM TA embedded
> in the OP-TEE, not sure if the same is true in your case.
> 
> RPMB provisioning is needed for full functionality, but even without it
> you shouldn't see these errors. Maybe the fTPM TA is missing from your
> OP-TEE build, or something similar is causing loader error.

Any comment on this? We are just integrating current meta-ti master with
latest master U-Boot, as I wrote a few days ago. There is nothing
special going on on our side, and your recent changes are introducing
this unexpected behavior.


On Wed, May 13, 2026 at 08:49:31AM -0500, Andrew Davis wrote:
> This makes me think we are at the stage in boot where EFI variables
> are trying to be persisted to some media, and when trying to use
> the fTPM for this it fails (as would be expected without RPMB).
> So this should be harmless, but why there is such a large error
> printout we need to investigate and try to make it less verbose.

Any chance TI can help on this?


Francesco


  parent reply	other threads:[~2026-05-22  6:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 11:24 [PATCH v2] arm: k3: Kconfig: Enable fTPM and RPMB support Shiva Tripathi
2026-02-25 14:48 ` Andrew Davis
2026-03-10 20:45 ` Tom Rini
2026-03-17 11:34   ` Shiva Tripathi
2026-03-17 14:07     ` Tom Rini
2026-03-18 11:01       ` Shiva Tripathi
2026-05-12 16:44 ` Ernest Van Hoecke
2026-05-13 13:06   ` Shiva Tripathi
2026-05-13 13:49     ` Andrew Davis
2026-05-13 14:23       ` Francesco Dolcini
2026-05-22  6:15     ` Francesco Dolcini [this message]
2026-05-22 14:19       ` Shiva Tripathi
2026-05-22 16:20         ` Francesco Dolcini
2026-05-22 17:36           ` Tom Rini
2026-06-10  5:51             ` Francesco Dolcini
2026-06-10 13:27               ` Shiva Tripathi
2026-06-10 13:53                 ` Francesco Dolcini
2026-06-10 19:00                   ` 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=20260522061515.GA8642@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=afd@ti.com \
    --cc=anshuld@ti.com \
    --cc=bb@ti.com \
    --cc=ernestvanhoecke@gmail.com \
    --cc=k-malarvizhi@ti.com \
    --cc=kamlesh@ti.com \
    --cc=praneeth@ti.com \
    --cc=s-tripathi1@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vishalm@ti.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.