public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@amd.com>
Cc: Gabriel Dalimonte <gabriel.dalimonte@gmail.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Jonathan Humphreys <j-humphreys@ti.com>,
	Raymond Mao <raymondmaoca@gmail.com>,
	Shantur Rathore <i@shantur.com>, Simon Glass <sjg@chromium.org>,
	Tom Rini <trini@konsulko.com>,
	"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>
Subject: [PATCH v4 0/3] efi_vars: Implement SPI Flash storage for EFI
Date: Wed, 14 Jan 2026 16:15:32 +0100	[thread overview]
Message-ID: <cover.1768403729.git.michal.simek@amd.com> (raw)


This is updated series based on v3 version sent here
https://lore.kernel.org/all/20231126220836.374956-1-i@shantur.com/

that's why I am continuing on v4 instead of starting from scratch.

Tested on kv260 with saving variables to location where User MTD partition
is.
CONFIG_EFI_VARIABLE_SF_STORE=y
CONFIG_EFI_RT_VOLATILE_STORE=y
CONFIG_EFI_VARIABLE_SF_OFFSET=0x22a0000

Thanks,
Michal

Changes in v4:
- New patch based on review comments from v3
- use unify methods for reading/writing variable

Changes in v3:
- Fixed compiler warnings.

Changes in v2:
- Refactored efi_var_file to move common parts out as requested
- Changed ifdefs to use CONFIG_IS_DEFINED
- Fixed typos

Michal Simek (1):
  efi_var: Unify read/write access helper function

Shantur Rathore (2):
  efi_var_file: refactor to move buffer functions
  efi_vars: Implement SPI Flash store

 include/efi_variable.h          | 18 +++----
 lib/efi_loader/Kconfig          | 26 +++++++++-
 lib/efi_loader/Makefile         |  3 +-
 lib/efi_loader/efi_var_common.c | 44 ++++++++++++++++
 lib/efi_loader/efi_var_file.c   | 65 ++---------------------
 lib/efi_loader/efi_var_sf.c     | 91 +++++++++++++++++++++++++++++++++
 lib/efi_loader/efi_variable.c   | 16 ++++--
 7 files changed, 187 insertions(+), 76 deletions(-)
 create mode 100644 lib/efi_loader/efi_var_sf.c

-- 
2.43.0

base-commit: 4aa15db6ff8b2bbdcdb082e547967bf4a96fee52
branch: master-next-test

             reply	other threads:[~2026-01-14 15:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 15:15 Michal Simek [this message]
2026-01-14 15:15 ` [PATCH v4 1/3] efi_var_file: refactor to move buffer functions Michal Simek
2026-01-14 15:15 ` [PATCH v4 2/3] efi_var: Unify read/write access helper function Michal Simek
2026-01-14 15:15 ` [PATCH v4 3/3] efi_vars: Implement SPI Flash store Michal Simek
2026-01-15  7:55   ` Ilias Apalodimas
2026-01-15 10:01     ` Peter Robinson
2026-01-15 10:08       ` Ilias Apalodimas
2026-01-22 12:18   ` Ilias Apalodimas
2026-01-22 12:32     ` Michal Simek
2026-01-23  7:40       ` Ilias Apalodimas
2026-01-23  8:22         ` Michal Simek
2026-01-23 13:01           ` Ilias Apalodimas
2026-01-23 14:15             ` Michal Simek
2026-01-14 18:24 ` [PATCH v4 0/3] efi_vars: Implement SPI Flash storage for EFI E Shattow
2026-01-15  2:40   ` Peter Robinson

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.1768403729.git.michal.simek@amd.com \
    --to=michal.simek@amd.com \
    --cc=gabriel.dalimonte@gmail.com \
    --cc=git@amd.com \
    --cc=i@shantur.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=j-humphreys@ti.com \
    --cc=paul.liu@linaro.org \
    --cc=raymondmaoca@gmail.com \
    --cc=sjg@chromium.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