All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] SPI fixes for v6.17-rc3
Date: Fri, 05 Sep 2025 19:39:55 +0100	[thread overview]
Message-ID: <279ce5a01bec4d9c300da6709a582e21@kernel.org> (raw)

The following changes since commit b320789d6883cc00ac78ce83bccbfe7ed58afcf0:

  Linux 6.17-rc4 (2025-08-31 15:33:07 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-fix-v6.17-rc3

for you to fetch changes up to 1991a458528588ff34e98b6365362560d208710f:

  spi: spi-qpic-snand: unregister ECC engine on probe error and device remove (2025-09-03 14:49:58 +0100)

----------------------------------------------------------------
spi: Fixes for v6.17

The largest batch of fixes here is a series of fixes for the Freescale
LPSPI driver which James Clark pulled out of their BSP while looking at
support for the NXP S32G version of the controller.  The majority of
this turned out to be bug fixes that affect existing systems with the
actual S32G support being just a small quirk that would be unremarkable
by itself, the whole series has had a good amount of testing and review
and the individual patches are all pretty straightforward by themselves.

We also have a few other driver specific fixes, including a relatively
large but simple one for the Cadence QuadSPI driver.

----------------------------------------------------------------
Conor Dooley (1):
      spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback

Gabor Juhos (1):
      spi: spi-qpic-snand: unregister ECC engine on probe error and device remove

James Clark (3):
      spi: spi-fsl-lpspi: Constify devtype datas
      spi: spi-fsl-lpspi: Treat prescale_max == 0 as no erratum
      spi: spi-fsl-lpspi: Parameterize reading num-cs from hardware

Khairul Anuar Romli (1):
      spi: cadence-quadspi: Implement refcount to handle unbind during busy

Larisa Grigore (6):
      spi: spi-fsl-lpspi: Fix transmissions when using CONT
      spi: spi-fsl-lpspi: Set correct chip-select polarity bit
      spi: spi-fsl-lpspi: Reset FIFO and disable module on transfer abort
      spi: spi-fsl-lpspi: Clear status register after disabling the module
      dt-bindings: lpspi: Document support for S32G
      spi: spi-fsl-lpspi: Add compatible for S32G

Mark Brown (1):
      spi: spi-fsl-lpspi: Generic fixes and support for

 .../devicetree/bindings/spi/spi-fsl-lpspi.yaml     |  5 +++
 drivers/spi/spi-cadence-quadspi.c                  | 33 +++++++++++++++
 drivers/spi/spi-fsl-lpspi.c                        | 47 +++++++++++++---------
 drivers/spi/spi-microchip-core-qspi.c              | 12 ------
 drivers/spi/spi-qpic-snand.c                       |  6 ++-
 5 files changed, 70 insertions(+), 33 deletions(-)

             reply	other threads:[~2025-09-05 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 18:39 Mark Brown [this message]
2025-09-05 22:34 ` [GIT PULL] SPI fixes for v6.17-rc3 pr-tracker-bot

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=279ce5a01bec4d9c300da6709a582e21@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.