From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@amd.com>, <xypron.glpk@gmx.de>,
<ilias.apalodimas@linaro.org>, <sjg@chromium.org>
Cc: Casey Connolly <casey.connolly@linaro.org>,
Jerome Forissier <jerome.forissier@arm.com>,
Kory Maincent <kory.maincent@bootlin.com>,
"Leo Yu-Chi Liang" <ycliang@andestech.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Padmarao Begari <padmarao.begari@amd.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Sughosh Ganu <sughosh.ganu@arm.com>,
Tom Rini <trini@konsulko.com>, Yao Zi <me@ziyao.cc>
Subject: [PATCH v4 0/3] fwu: Call EFI stack initialization after preboot
Date: Thu, 2 Apr 2026 17:36:57 +0200 [thread overview]
Message-ID: <cover.1775144215.git.michal.simek@amd.com> (raw)
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 happening 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.
Thanks,
Michal
Changes in v4:
- update dm tests
Changes in v3:
- add missing type_name extension
Changes in v2:
- new patch in series
- check return value
Michal Simek (3):
event: Check return value from event_notify_null()
event: Introduce EVT_POST_PREBOOT event
fwu: Move boottime checks to EVT_POST_PREBOOT
common/board_r.c | 6 +++++-
common/event.c | 3 +++
common/main.c | 4 ++++
include/event.h | 9 +++++++++
lib/fwu_updates/fwu.c | 2 +-
test/dm/fwu_mdata.c | 4 ++--
6 files changed, 24 insertions(+), 4 deletions(-)
--
2.43.0
base-commit: 0cdcef58834c0ad223952987d9bde449badeea31
branch: debian-sent3
next reply other threads:[~2026-04-02 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 15:36 Michal Simek [this message]
2026-04-02 15:36 ` [PATCH v4 1/3] event: Check return value from event_notify_null() Michal Simek
2026-04-02 15:36 ` [PATCH v4 2/3] event: Introduce EVT_POST_PREBOOT event Michal Simek
2026-04-02 15:37 ` [PATCH v4 3/3] fwu: Move boottime checks to EVT_POST_PREBOOT Michal Simek
2026-04-02 16:14 ` [v4,3/3] " Simon Glass
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=cover.1775144215.git.michal.simek@amd.com \
--to=michal.simek@amd.com \
--cc=casey.connolly@linaro.org \
--cc=git@amd.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@arm.com \
--cc=kory.maincent@bootlin.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=me@ziyao.cc \
--cc=padmarao.begari@amd.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@arm.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ycliang@andestech.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