Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Frieder Schrempf <frieder.schrempf@kontron.de>,
	Michael Walle <michael@walle.cc>,
	Pratyush Yadav <pratyush@kernel.org>,
	linux-mtd@lists.infradead.org,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: [GIT PULL] spi-nand/spi-mem changes for 7.2
Date: Tue, 05 May 2026 17:17:42 +0200	[thread overview]
Message-ID: <87jythopgp.fsf@bootlin.com> (raw)

Hello Mark,

Here is an immutable tag for you to pull into your spi tree with all the
spi-mem changes we agreed upon. I also merged it into nand/next.

Thanks,
Miquèl

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/mtd/spi-mem-cont-read-for-7.2

for you to fetch changes up to 38fbe4b3f66e5b8e2f2ab8e7ca3d912e1e935fe2:

  spi: spi-mem: Add a no_cs_assertion capability (2026-05-04 15:07:37 +0200)

----------------------------------------------------------------
Aside from preparation changes in the SPI NAND core, the changes carried
here focus on the shared spi-mem layer which is enhanced in order to
bring two new features:

- The possibility to fill a primary and a secondary operation template
  in the direct mapping structure in order to support continuous reads
  in SPI NAND, which may require two different read operations.

- SPI controllers may indicate possible CS instabilities over long
  transfers by setting a boolean. This capability is related to the
  previous one, the need for it has arised while testing SPI NAND
  continuous reads with the Cadence QSPI controller which cannot, under
  certain conditions, keep the CS asserted for the length of
  an eraseblock-large transfer.

----------------------------------------------------------------
Miquel Raynal (6):
      mtd: spinand: Drop a too strong limitation
      mtd: spinand: Expose spinand_op_is_odtr()
      mtd: spinand: Drop ECC dirmaps
      spi: spi-mem: Transform the read operation template
      spi: spi-mem: Create a secondary read operation
      spi: spi-mem: Add a no_cs_assertion capability

 drivers/mtd/nand/spi/core.c   | 76 +++++++++++++++++--------------------------
 drivers/mtd/spi-nor/core.c    | 22 +++++++------
 drivers/spi/spi-airoha-snfi.c |  6 ++--
 drivers/spi/spi-aspeed-smc.c  |  4 +--
 drivers/spi/spi-intel.c       |  6 ++--
 drivers/spi/spi-mem.c         | 32 ++++++++++++++----
 drivers/spi/spi-mxic.c        | 18 +++++-----
 drivers/spi/spi-npcm-fiu.c    | 16 ++++-----
 drivers/spi/spi-rpc-if.c      |  8 ++---
 drivers/spi/spi-stm32-ospi.c  |  6 ++--
 drivers/spi/spi-stm32-qspi.c  |  6 ++--
 drivers/spi/spi-wpcm-fiu.c    |  2 +-
 include/linux/mtd/spinand.h   |  4 +--
 include/linux/spi/spi-mem.h   | 12 ++++++-
 14 files changed, 115 insertions(+), 103 deletions(-)

                 reply	other threads:[~2026-05-05 15:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87jythopgp.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=frieder.schrempf@kontron.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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