In preparation for fixing the SPI controller API so that it no longer
drops a reference when deregistering (non-managed) controllers (cf.
[1]), this series converts drivers using non-managed registration to use
managed allocation.

Included is also a related cleanup of a ti-qspi error path.

This second set will be followed by a third set of 12 patches for
drivers using managed registration.

That leaves us with 18 drivers using non-managed allocation, which is
few enough to be able to fix the API in tree-wide change.

Johan


[1] https://lore.kernel.org/lkml/20260325145319.1132072-1-johan@kernel.org/


Johan Hovold (20):
  spi: pic32: switch to managed controller allocation
  spi: pic32-sqi: switch to managed controller allocation
  spi: pl022: switch to managed controller allocation
  spi: qup: switch to managed controller allocation
  spi: rspi: switch to managed controller allocation
  spi: sh-hspi: switch to managed controller allocation
  spi: sh-msiof: switch to managed controller allocation
  spi: sifive: switch to managed controller allocation
  spi: slave-mt27xx: switch to managed controller allocation
  spi: sprd: switch to managed controller allocation
  spi: st-ssc4: switch to managed controller allocation
  spi: sun4i: switch to managed controller allocation
  spi: sun6i: switch to managed controller allocation
  spi: syncuacer: switch to managed controller allocation
  spi: tegra114: switch to managed controller allocation
  spi: tegra20-sflash: switch to managed controller allocation
  spi: ti-qspi: switch to managed controller allocation
  spi: ti-qspi: cleanup registration error path
  spi: uniphier: switch to managed controller allocation
  spi: zync-qspi: switch to managed controller allocation

 drivers/spi/spi-pic32-sqi.c      | 28 +++++++---------------
 drivers/spi/spi-pic32.c          | 11 +++------
 drivers/spi/spi-pl022.c          | 11 +++------
 drivers/spi/spi-qup.c            | 15 ++++--------
 drivers/spi/spi-rspi.c           | 19 ++++-----------
 drivers/spi/spi-sh-hspi.c        | 11 ++-------
 drivers/spi/spi-sh-msiof.c       | 28 +++++++---------------
 drivers/spi/spi-sifive.c         | 39 +++++++++----------------------
 drivers/spi/spi-slave-mt27xx.c   | 33 ++++++++------------------
 drivers/spi/spi-sprd.c           | 20 +++++-----------
 drivers/spi/spi-st-ssc4.c        | 14 ++++-------
 drivers/spi/spi-sun4i.c          | 35 +++++++++-------------------
 drivers/spi/spi-sun6i.c          | 38 ++++++++++--------------------
 drivers/spi/spi-synquacer.c      | 24 ++++++-------------
 drivers/spi/spi-tegra114.c       | 34 ++++++++++-----------------
 drivers/spi/spi-tegra20-sflash.c | 24 +++++++------------
 drivers/spi/spi-ti-qspi.c        | 37 +++++++++++------------------
 drivers/spi/spi-uniphier.c       | 33 +++++++++-----------------
 drivers/spi/spi-zynq-qspi.c      | 40 ++++++++++----------------------
 19 files changed, 152 insertions(+), 342 deletions(-)

-- 
2.53.0

On Tue, 05 May 2026 09:28:49 +0200, Johan Hovold wrote:
> spi: switch to managed controller allocation (part 2/3)
> 
> In preparation for fixing the SPI controller API so that it no longer
> drops a reference when deregistering (non-managed) controllers (cf.
> [1]), this series converts drivers using non-managed registration to use
> managed allocation.
> 
> [...]

Applied to

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

Thanks!

[01/20] spi: pic32: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/4af89d7d8552
[02/20] spi: pic32-sqi: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/dda3a77e1a32
[03/20] spi: pl022: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/02efc5557c8e
[04/20] spi: qup: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/86e8160240af
[05/20] spi: rspi: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/368d0e6c6f82
[06/20] spi: sh-hspi: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/042414e4da73
[07/20] spi: sh-msiof: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/354b0a4ad4eb
[08/20] spi: sifive: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/fd260013577d
[09/20] spi: slave-mt27xx: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/cd1cd2ff56bf
[10/20] spi: sprd: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/d68627cc76cd
[11/20] spi: st-ssc4: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/d3cf5ebdf1c9
[12/20] spi: sun4i: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/02b36d644ded
[13/20] spi: sun6i: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/9864636b1cd9
[14/20] spi: syncuacer: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/5d5bbf177d18
[15/20] spi: tegra114: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/3068e7063cc4
[16/20] spi: tegra20-sflash: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/3a14bf4f5453
[17/20] spi: ti-qspi: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/76a24627b98c
[18/20] spi: ti-qspi: cleanup registration error path
        https://git.kernel.org/broonie/spi/c/f8689d5a9ee4
[19/20] spi: uniphier: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/789986b14564
[20/20] spi: zync-qspi: switch to managed controller allocation
        https://git.kernel.org/broonie/spi/c/be552efa43ee

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