From: Michal Simek <michal.simek@amd.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, git@amd.com, ilias.apalodimas@linaro.org,
sjg@chromium.org, Casey Connolly <casey.connolly@linaro.org>,
Kory Maincent <kory.maincent@bootlin.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Padmarao Begari <padmarao.begari@amd.com>,
Sughosh Ganu <sughosh.ganu@arm.com>,
Weijie Gao <weijie.gao@mediatek.com>, Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v2 0/3] fwu: Call EFI stack initialization after preboot
Date: Tue, 31 Mar 2026 17:03:07 +0200 [thread overview]
Message-ID: <5769c248-5d76-4a45-80a7-2deda8a640b4@amd.com> (raw)
In-Reply-To: <13015773-7580-40DB-A865-3B490FDD183A@gmx.de>
On 3/31/26 17:00, Heinrich Schuchardt wrote:
> Am 31. März 2026 16:28:06 MESZ schrieb Tom Rini <trini@konsulko.com>:
>> On Wed, Mar 18, 2026 at 02:25:08PM +0100, Michal Simek wrote:
>>
>>> Hi,
>>>
>>> the whole series is trying to address issues we have on platforms where usb
>>> and ufs init are not done before efi initialization. This is happenin on
>>> platforms where A/B update is enabled. FWU code is called early and do EFI
>>> initialization before usb and ufs started that's why they are not visible.
>>>
>>> We are workarounding it by starting usb/ufs from board file but this should
>>> be more generic approach.
>
> If a block device is created after EFI initialization an event handler creates an EFI handle.
But capsules are not automatically taken.
> Do have an example for QEMU to reproduce the issue.
Nope. Only on our HW.
> I am on vacation till April 11th. But maybe Ilias could look at it.
Enjoy.
M
prev parent reply other threads:[~2026-03-31 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 13:25 [PATCH v2 0/3] fwu: Call EFI stack initialization after preboot Michal Simek
2026-03-18 13:25 ` [PATCH v2 1/3] event: Check return value from event_notify_null() Michal Simek
2026-03-19 22:09 ` Simon Glass
2026-03-18 13:25 ` [PATCH v2 2/3] event: Introduce EVT_POST_PREBOOT event Michal Simek
2026-03-19 22:09 ` Simon Glass
2026-03-18 13:25 ` [PATCH v2 3/3] fwu: Move boottime checks to EVT_POST_PREBOOT Michal Simek
2026-03-19 23:56 ` [PATCH v2 0/3] fwu: Call EFI stack initialization after preboot Casey Connolly
2026-03-20 8:31 ` Michal Simek
2026-03-31 14:28 ` Tom Rini
2026-03-31 14:46 ` Michal Simek
2026-03-31 15:00 ` Heinrich Schuchardt
2026-03-31 15:03 ` Michal Simek [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=5769c248-5d76-4a45-80a7-2deda8a640b4@amd.com \
--to=michal.simek@amd.com \
--cc=casey.connolly@linaro.org \
--cc=git@amd.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kory.maincent@bootlin.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=me@ziyao.cc \
--cc=padmarao.begari@amd.com \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@arm.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=weijie.gao@mediatek.com \
--cc=xypron.glpk@gmx.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