From: Christian Marangi <ansuelsmth@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: Joe Hershberger <joe.hershberger@ni.com>, u-boot@lists.denx.de
Subject: Re: [PATCH] env: Introduce support for SPI NAND flash
Date: Wed, 2 Apr 2025 17:10:31 +0200 [thread overview]
Message-ID: <67ed536a.050a0220.3bc19f.b184@mx.google.com> (raw)
In-Reply-To: <20250402150542.GV5495@bill-the-cat>
On Wed, Apr 02, 2025 at 09:05:42AM -0600, Tom Rini wrote:
> On Wed, Apr 02, 2025 at 12:57:57AM +0200, Christian Marangi wrote:
>
> > Introduce support for SPI NAND flash. Currently we only support SPI
> > flash based on the lagacy sf cmd that assume SPI flash are always NOR.
> > This is not the case as to SPI controller also NAND can be attached. Add
> > support for it by adding an env driver that base entirely on the MTD
> > api.
> >
> > Introduce a new kconfig ENV_IS_IN_SPI_NAND_FLASH and
> > CONFIG_SYS_SNAND_ENV_DEV to define the name of the SPI nand as exposed
> > by mtd list.
> >
> > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> > ---
> > env/Kconfig | 41 ++++-
> > env/Makefile | 1 +
> > env/env.c | 3 +
> > env/snand.c | 338 +++++++++++++++++++++++++++++++++++++++++
> > include/env_internal.h | 1 +
> > 5 files changed, 380 insertions(+), 4 deletions(-)
> > create mode 100644 env/snand.c
>
> Since this uses the generic mtd API, it can also support SPI NOR, and
> "regular" NAND too yes? If so, I'd like to see this named more
> generically (and my feedback about naming things from the UFS one
> applies here too), and then perhaps a follow-up converting some other
> platforms to use this? Thanks.
>
I assume yes. So maybe we can change this to env/mtd.c? Any hint for a
better name?
Can you link the feedback from UFS, I can't find it.
--
Ansuel
next prev parent reply other threads:[~2025-04-02 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 22:57 [PATCH] env: Introduce support for SPI NAND flash Christian Marangi
2025-04-02 15:05 ` Tom Rini
2025-04-02 15:10 ` Christian Marangi [this message]
2025-04-02 15:13 ` Tom Rini
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=67ed536a.050a0220.3bc19f.b184@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=joe.hershberger@ni.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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.