From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D9363CD8CB2 for ; Wed, 10 Jun 2026 13:53:22 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 5A7E1848A1; Wed, 10 Jun 2026 15:53:21 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=dolcini.it Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=dolcini.it header.i=@dolcini.it header.b="oewJgGxK"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id CB113848BA; Wed, 10 Jun 2026 15:53:19 +0200 (CEST) Received: from mail11.truemail.it (mail11.truemail.it [IPv6:2001:4b7e:0:8::81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 9FEB58489F for ; Wed, 10 Jun 2026 15:53:17 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=dolcini.it Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=francesco@dolcini.it Received: from gaggiata.pivistrello.it (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id D32951FE3B; Wed, 10 Jun 2026 15:53:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1781099597; bh=YcTogNJmYVjqCzV34IGcoLTmArc9faqn59nkPJakgIE=; h=Received:From:To:Subject; b=oewJgGxKaziw4qg8qCG0swuglbQL8YZgD3m99YZKjYwzuNo5xMvHt3Y9QGHwPRTGo X9+foSOi4IDvgIBjQEu6gccvqa45+FAe4gMRv3qRCUf/mfFrKHYKAE3jU5olsCs9PK 4UR5MHw6EN7Z97FET8x4dJEBVaAJkJ8NQ4fDTPFVWsciFVyOh50WrOP92FjCXfyuZd bzG1EZlLGc5vwWqQC5j8EVnGr2VdqgWnvvEfsn2VyF80QjoZl4qQaCp2e/GL6ilTHP vv060cJJiQcsiXfodZ3+Q1oWwc3mpvk4pL/mWlFOvuVh/X6jIktJb2j8KOZNA/kyqM R3XTrkldYvv5w== Received: by gaggiata.pivistrello.it (Postfix, from userid 1000) id 884997F969; Wed, 10 Jun 2026 15:53:16 +0200 (CEST) Date: Wed, 10 Jun 2026 15:53:16 +0200 From: Francesco Dolcini To: Shiva Tripathi Cc: Francesco Dolcini , Tom Rini , Andrew Davis , Ernest Van Hoecke , 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 Message-ID: References: <20260522061515.GA8642@francesco-nb> <0c76975d-1f87-4a6c-87c2-cff99584fa1e@ti.com> <20260522162048.GA114365@francesco-nb> <20260522173637.GW1858239@bill-the-cat> <20260610055141.GA13255@francesco-nb> <9b1540d5-81dc-45f2-a188-915a8b4b4c90@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9b1540d5-81dc-45f2-a188-915a8b4b4c90@ti.com> X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean On Wed, Jun 10, 2026 at 06:57:54PM +0530, Shiva Tripathi wrote: > > > On 6/10/26 11:21, Francesco Dolcini wrote: > > Hello Shiva, > > > > On Fri, May 22, 2026 at 11:36:37AM -0600, Tom Rini wrote: > >> On Fri, May 22, 2026 at 06:20:48PM +0200, Francesco Dolcini wrote: > >>> On Fri, May 22, 2026 at 07:49:27PM +0530, Shiva Tripathi wrote: > >>>> On 5/22/26 11:45, Francesco Dolcini wrote: > >>>>> On Wed, May 13, 2026 at 06:36:40PM +0530, Shiva Tripathi wrote: > >>>>> 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? > >>>> Yes, I am looking into it. The logs are showing up as OPTEE's fTPM TA is > >>>> failing to load, since the eMMC RPMB isn't provisioned. > >>> > >>> Thanks for looking into that, and I am glad you can reproduce the issue. > >>> > >>>> Even though these logs don't affect functionality, you can revert this > >>>> patch to avoid confusion. I am checking if there's a cleaner way to > >>>> handle this. > >>> > >>> I am using mainline U-Boot, if this needs to be reverted, it must be > >>> reverted here. Given the release timeline, and the fact that this is not > >>> breaking the functionality I am fine waiting a little bit to see if it > >>> is possible to fix it, we have some time before the v2026.07 release. > >> > >> And for the release I would like to make sure someone has a clear path > >> on what changes are needed, if any in the end, on mainline U-Boot by > >> rc4, which is June 8th. We have the last one on June 22nd but I'd rather > >> not have to revert then unless things are just unresolved. Thanks! > > > > Shiva: what's the plan? As of now the issue is still there. > > > I have sent a fix patch to optee_ftpm[1]. With this patch, the fTPM TA > gracefully handles RPMB unavailability without panicking, eliminating > the memory dumps. > > For now, there are two interim approaches: > 1. Revert the u-boot patch that enabled k3 fTPM configs > 2. Apply the optee-ftpm patch in meta-ti recipes > > I am waiting review from optee-ftpm maintainers. If it's accepted, we > will upgrade the optee-ftpm in meta-ti to the fixed version. Given the current status I would not revert the patch in U-Boot. Once the patch is accepted in optee the issue will naturally solve on its own, and in the short term you can have the patch in meta-ti. Francesco