All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@amd.com>, <xypron.glpk@gmx.de>,
	<ilias.apalodimas@linaro.org>
Cc: Casey Connolly <casey.connolly@linaro.org>,
	Kory Maincent <kory.maincent@bootlin.com>,
	Padmarao Begari <padmarao.begari@amd.com>,
	"Simon Glass" <sjg@chromium.org>,
	Sughosh Ganu <sughosh.ganu@arm.com>,
	Tom Rini <trini@konsulko.com>
Subject: [PATCH 0/2] fwu: Call EFI stack initialization after preboot
Date: Tue, 10 Mar 2026 15:59:26 +0100	[thread overview]
Message-ID: <cover.1773154765.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 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.

Thanks,
Michal


Michal Simek (2):
  event: Introduce EVT_POST_PREBOOT event
  fwu: Move boottime checks to EVT_POST_PREBOOT

 common/main.c         | 3 +++
 include/event.h       | 9 +++++++++
 lib/fwu_updates/fwu.c | 2 +-
 3 files changed, 13 insertions(+), 1 deletion(-)

-- 
2.43.0

base-commit: e5387628c1d64caf7bcabb5d99d2987bd5bff617
branch: debian-sent3

             reply	other threads:[~2026-03-10 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 14:59 Michal Simek [this message]
2026-03-10 14:59 ` [PATCH 1/2] event: Introduce EVT_POST_PREBOOT event Michal Simek
2026-03-17 12:29   ` Simon Glass
2026-03-17 12:43     ` Michal Simek
2026-03-10 14:59 ` [PATCH 2/2] fwu: Move boottime checks to EVT_POST_PREBOOT Michal Simek

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.1773154765.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=kory.maincent@bootlin.com \
    --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=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 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.