From: Mayuresh Chitale <mchitale@ventanamicro.com>
To: Bin Meng <bmeng.cn@gmail.com>, Simon Glass <sjg@chromium.org>
Cc: Mayuresh Chitale <mchitale@ventanamicro.com>,
u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>
Subject: [PATCH v2 0/4] SPL NVme support
Date: Tue, 2 May 2023 21:48:58 +0530 [thread overview]
Message-ID: <20230502161902.1339861-1-mchitale@ventanamicro.com> (raw)
This patchset adds support to load images of the SPL's next booting stage from a NVMe device.
Changes in v2:
- Rebase on v2023.07-rc1
- Use uclass ID for blk APIs
- Add support to load FIT images from ext filesystem
Mayuresh Chitale (4):
spl: Add Kconfig options for NVME
nvme: pci: Enable for SPL
spl: Support loading a FIT from ext FS
common: spl: Add spl NVMe boot support
arch/riscv/include/asm/spl.h | 1 +
common/spl/Kconfig | 30 +++++++++++++++++++++
common/spl/Makefile | 1 +
common/spl/spl_ext.c | 33 +++++++++++++++++++++++
common/spl/spl_nvme.c | 52 ++++++++++++++++++++++++++++++++++++
drivers/Makefile | 1 +
drivers/nvme/Makefile | 2 +-
drivers/pci/Kconfig | 7 +++++
drivers/pci/pci-uclass.c | 3 ++-
9 files changed, 128 insertions(+), 2 deletions(-)
create mode 100644 common/spl/spl_nvme.c
--
2.34.1
next reply other threads:[~2023-05-02 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 16:18 Mayuresh Chitale [this message]
2023-05-02 16:18 ` [PATCH v2 1/4] spl: Add Kconfig options for NVME Mayuresh Chitale
2023-05-02 16:19 ` [PATCH v2 2/4] nvme: pci: Enable for SPL Mayuresh Chitale
2023-05-03 1:28 ` Simon Glass
2023-05-04 8:27 ` Mayuresh Chitale
2023-05-02 16:19 ` [PATCH v2 3/4] spl: Support loading a FIT from ext FS Mayuresh Chitale
2023-05-02 16:19 ` [PATCH v2 4/4] common: spl: Add spl NVMe boot support Mayuresh Chitale
2023-05-03 1:28 ` Simon Glass
2023-05-04 8:28 ` Mayuresh Chitale
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=20230502161902.1339861-1-mchitale@ventanamicro.com \
--to=mchitale@ventanamicro.com \
--cc=bmeng.cn@gmail.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).