public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 00/11] SF: Migrate to Linux SPI NOR framework
Date: Tue, 4 Dec 2018 13:55:48 +0100	[thread overview]
Message-ID: <20181204135548.640503ce@bbrezillon> (raw)
In-Reply-To: <20181204122659.14720-1-vigneshr@ti.com>

On Tue, 4 Dec 2018 17:56:48 +0530
Vignesh R <vigneshr@ti.com> wrote:

> U-Boot SPI NOR support (sf layer) is quite outdated as it does not
> support 4 byte addressing opcodes, SFDP table parsing and different types of
> quad mode enable sequences. Many newer flashes no longer support BANK
> registers used by sf layer to a access >16MB space.
> Also, many SPI controllers have special MMIO interfaces which provide
> accelerated read/write access but require knowledge of flash parameters
> to make use of it. Recent spi-mem layer provides a way to support such
> flashes but sf layer isn't using that.
> This patch series syncs SPI NOR framework from Linux v4.19. It also adds
> spi-mem support on top.
> So, we gain 4byte addressing support and SFDP support. This makes
> migrating to U-Boot MTD framework easier.

Glad to see that happen sooner than I had expected. Looks like the
patch series is in a good shape already, and I'm happy to see the
u-boot spi-nor layer being based on the Linux one.

Good job, and thanks again for working on that!

Boris

  parent reply	other threads:[~2018-12-04 12:55 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 12:26 [U-Boot] [RFC PATCH v2 00/11] SF: Migrate to Linux SPI NOR framework Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 01/11] spi: spi-mem: Allow use of spi_mem_exec_op for all SPI modes Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 02/11] spi-mem: Claim SPI bus before spi mem access Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 03/11] spi: Add non DM version of SPI_MEM Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 04/11] sh: bitops: add hweight*() macros Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 05/11] mtd: spi: Port SPI NOR framework from Linux Vignesh R
2018-12-05 20:13   ` Simon Goldschmidt
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 06/11] mtd spi: Switch to new SPI NOR framework Vignesh R
2018-12-05  7:04   ` Simon Goldschmidt
2018-12-05 11:12     ` Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 07/11] mtd: spi: Remove unused files Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 08/11] mtd: spi: Add lightweight SPI flash stack for SPL Vignesh R
2018-12-05  7:01   ` Simon Goldschmidt
2018-12-05 11:09     ` Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 09/11] sf_mtd: Simply mtd operations Vignesh R
2018-12-04 12:49   ` Boris Brezillon
2018-12-05  8:00     ` Vignesh R
2018-12-05  8:27       ` Miquel Raynal
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 10/11] taurus_defconfig: Enable simple malloc in SPL Vignesh R
2018-12-04 12:26 ` [U-Boot] [RFC PATCH v2 11/11] axm_defconfig: " Vignesh R
2018-12-04 12:55 ` Boris Brezillon [this message]
2018-12-04 20:11   ` [U-Boot] [RFC PATCH v2 00/11] SF: Migrate to Linux SPI NOR framework Simon Goldschmidt
2018-12-05  6:51     ` Vignesh R
2018-12-05  6:55       ` Simon Goldschmidt
2018-12-05 20:45         ` Simon Goldschmidt
2018-12-06 13:46           ` Vignesh R
2018-12-06 13:54             ` Simon Goldschmidt
2018-12-06 16:36               ` Simon Goldschmidt
2018-12-06 17:39                 ` Vignesh R
2018-12-06 19:17                   ` Simon Goldschmidt
2018-12-07  5:58                     ` Vignesh R
2018-12-07 18:43                       ` Simon Goldschmidt
2018-12-06 17:14 ` Jagan Teki
2018-12-06 18:18   ` Tom Rini
2018-12-06 18:25   ` Vignesh R
2018-12-06 19:22     ` Simon Goldschmidt
2018-12-07  9:51     ` Boris Brezillon
2018-12-09  8:54       ` Vignesh R
2018-12-10 13:02     ` Jagan Teki
2018-12-10 13:15       ` Boris Brezillon
2018-12-10 14:33         ` Tom Rini
2018-12-10 17:38       ` Vignesh R
2018-12-10 18:04         ` Miquel Raynal

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=20181204135548.640503ce@bbrezillon \
    --to=boris.brezillon@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox