This series fixes some runtime PM related issues in the cadence-quadspi
driver.

Included is also a couple of related cleanups.

Johan


Johan Hovold (6):
  spi: cadence-quadspi: fix runtime pm disable imbalance on probe
    failure
  spi: cadence-quadspi: fix clock imbalance on probe failure
  spi: cadence-quadspi: fix unclocked access on unbind
  spi: cadence-quadspi: fix runtime pm and clock imbalance on unbind
  spi: cadence-quadspi: clean up disable runtime pm quirk
  spi: cadence-quadspi: drop redundant match data lookup

 drivers/spi/spi-cadence-quadspi.c | 66 +++++++++++++------------------
 1 file changed, 27 insertions(+), 39 deletions(-)

-- 
2.52.0

On Tue, 21 Apr 2026 14:53:48 +0200, Johan Hovold wrote:
> spi: cadence-quadspi: runtime PM fixes
> 
> This series fixes some runtime PM related issues in the cadence-quadspi
> driver.
> 
> Included is also a couple of related cleanups.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.2

Thanks!

[1/6] spi: cadence-quadspi: fix runtime pm disable imbalance on probe failure
      https://git.kernel.org/broonie/spi/c/5ff4d5d1af0c
[2/6] spi: cadence-quadspi: fix clock imbalance on probe failure
      https://git.kernel.org/broonie/spi/c/cba53fe20c18
[3/6] spi: cadence-quadspi: fix unclocked access on unbind
      https://git.kernel.org/broonie/spi/c/233db2cb14db
[4/6] spi: cadence-quadspi: fix runtime pm and clock imbalance on unbind
      https://git.kernel.org/broonie/spi/c/5e8bb0cc72f1
[5/6] spi: cadence-quadspi: clean up disable runtime pm quirk
      https://git.kernel.org/broonie/spi/c/edbaae583ead
[6/6] spi: cadence-quadspi: drop redundant match data lookup
      https://git.kernel.org/broonie/spi/c/37c9dfa385db

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark