u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Mayuresh Chitale <mchitale@ventanamicro.com>
Cc: Bin Meng <bmeng.cn@gmail.com>,
	u-boot@lists.denx.de,  Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>
Subject: Re: [PATCH v3 1/5] spl: Add Kconfig options for NVME
Date: Thu, 4 May 2023 18:41:05 -0600	[thread overview]
Message-ID: <CAPnjgZ3_G0WP+niROFH7Ne8apQ=Q=Aysc0SaN_T2r3_wFFqfKg@mail.gmail.com> (raw)
In-Reply-To: <20230504095327.2791676-2-mchitale@ventanamicro.com>

On Thu, 4 May 2023 at 03:53, Mayuresh Chitale <mchitale@ventanamicro.com> wrote:
>
> Add kconfig options to enable NVME and PCI NVMe support in SPL
>
> Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
> ---
>  common/spl/Kconfig | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
>
> diff --git a/common/spl/Kconfig b/common/spl/Kconfig
> index 2c042ad306..515e8f2c66 100644
> --- a/common/spl/Kconfig
> +++ b/common/spl/Kconfig
> @@ -1263,6 +1263,27 @@ config SPL_SATA_RAW_U_BOOT_SECTOR
>           Sector on the SATA disk to load U-Boot from, when the SATA disk is being
>           used in raw mode. Units: SATA disk sectors (1 sector = 512 bytes).
>

Reviewed-by: Simon Glass <sjg@chromium.org>


> +config SPL_NVME
> +       bool "NVM Express device support"
> +       depends on BLK
> +       select HAVE_BLOCK_DEVICE
> +       select SPL_BLK_FS
> +       help
> +         This option enables support for NVM Express devices.
> +         It supports basic functions of NVMe (read/write).
> +
> +config SPL_NVME_PCI
> +       bool "NVM Express PCI device support for SPL"
> +       depends on SPL_PCI && SPL_NVME
> +       help
> +         This option enables support for NVM Express PCI devices.
> +         This allows use of NVMe devices for loading u-boot.
> +
> +config SPL_NVME_BOOT_DEVICE
> +       hex "NVMe boot device number"
> +       depends on SPL_NVME
> +       default 0x0
> +
>  config SPL_SERIAL
>         bool "Support serial"
>         select SPL_PRINTF
> --
> 2.34.1
>

  reply	other threads:[~2023-05-05  0:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  9:53 [PATCH v3 0/5] SPL NVMe support Mayuresh Chitale
2023-05-04  9:53 ` [PATCH v3 1/5] spl: Add Kconfig options for NVME Mayuresh Chitale
2023-05-05  0:41   ` Simon Glass [this message]
2023-05-04  9:53 ` [PATCH v3 2/5] spl: blk: Support loading images from fs Mayuresh Chitale
2023-05-05  0:41   ` Simon Glass
2023-06-03  8:19     ` Mayuresh Chitale
2023-05-04  9:53 ` [PATCH v3 3/5] nvme: pci: Enable for SPL Mayuresh Chitale
2023-05-05  0:41   ` Simon Glass
2023-06-03  8:19     ` Mayuresh Chitale
2023-05-04  9:53 ` [PATCH v3 4/5] spl: Support loading a FIT from ext FS Mayuresh Chitale
2023-05-05  0:40   ` Simon Glass
2023-06-03  8:21     ` Mayuresh Chitale
2023-05-17 14:41   ` Tom Rini
2023-05-17 14:58     ` Heinrich Schuchardt
2023-06-03  8:22     ` Mayuresh Chitale
2023-05-04  9:53 ` [PATCH v3 5/5] common: spl: Add spl NVMe boot support Mayuresh Chitale
2023-05-05  0:40   ` 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='CAPnjgZ3_G0WP+niROFH7Ne8apQ=Q=Aysc0SaN_T2r3_wFFqfKg@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=bmeng.cn@gmail.com \
    --cc=mchitale@ventanamicro.com \
    --cc=rick@andestech.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;
as well as URLs for NNTP newsgroup(s).