public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu@linaro.org>
To: u-boot@lists.denx.de
Cc: Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Alexander Graf <agraf@csgraf.de>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Simon Glass <sjg@chromium.org>, Bin Meng <bmeng.cn@gmail.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Jose Marinho <jose.marinho@arm.com>,
	Grant Likely <grant.likely@arm.com>,
	Tom Rini <trini@konsulko.com>,
	Etienne Carriere <etienne.carriere@linaro.org>,
	Sughosh Ganu <sughosh.ganu@linaro.org>,
	Paul Liu <paul.liu@linaro.org>
Subject: [PATCH 0/2] EFI: Reset system after capsule-on-disk
Date: Mon, 31 Jan 2022 18:18:39 +0900	[thread overview]
Message-ID: <164362071931.312714.14793570668139727572.stgit@localhost> (raw)

Hi,

According to Takahiro's suggestion and discussion, I made a patchset to
update the EFI capsule-on-disk, so that it does not use UpdateCapsule()
EFI API and reset after completing the capsule-on-disk.

The reset after completing the capsule-on-disk is stated in the UEFI
specification 2.9, section 8.5.5 "Delivery of Capsules via file on Mass
Storage device" as below,

    In all cases that a capsule is identified for processing the system is
    restarted after capsule processing is completed.

Note that this feature is enabled by CONFIG_EFI_RESET_AFTER_CAPSULE_ON_DISK.
If you want to keep the current firmware runs after capsule-on-disk (e.g.
for debugging), you can configure it disabled.

Thank you,

---

Masami Hiramatsu (2):
      efi_loader: Avoid using efi_update_capsule() from update capsule on disk
      efi_loader: Reset system after CapsuleUpdate on disk


 lib/efi_loader/Kconfig       |   10 ++++++++++
 lib/efi_loader/efi_capsule.c |   18 +++++++++++++++++-
 2 files changed, 27 insertions(+), 1 deletion(-)

--
Masami Hiramatsu <masami.hiramatsu@linaro.org>

             reply	other threads:[~2022-01-31  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  9:18 Masami Hiramatsu [this message]
2022-01-31  9:18 ` [PATCH 1/2] efi_loader: Avoid using efi_update_capsule() from update capsule on disk Masami Hiramatsu
2022-01-31 19:26   ` Heinrich Schuchardt
2022-02-01  2:21     ` Masami Hiramatsu
2022-01-31  9:19 ` [PATCH 2/2] efi_loader: Reset system after CapsuleUpdate " Masami Hiramatsu
2022-01-31 11:19   ` Grant Likely
2022-01-31 12:17     ` Heinrich Schuchardt
2022-02-01  2:26       ` Masami Hiramatsu
2022-02-01  3:16         ` AKASHI Takahiro
2022-01-31 12:38     ` Masami Hiramatsu

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=164362071931.312714.14793570668139727572.stgit@localhost \
    --to=masami.hiramatsu@linaro.org \
    --cc=agraf@csgraf.de \
    --cc=bmeng.cn@gmail.com \
    --cc=etienne.carriere@linaro.org \
    --cc=grant.likely@arm.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jose.marinho@arm.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=paul.liu@linaro.org \
    --cc=sjg@chromium.org \
    --cc=sughosh.ganu@linaro.org \
    --cc=takahiro.akashi@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox