Re: [PATCH 00/26] spi: fix controller deregistration (part 2/2)

From: Mark Brown

Date: Fri Apr 10 2026 - 12:36:20 EST


On Fri, 10 Apr 2026 10:17:30 +0200, Johan Hovold wrote:
> spi: fix controller deregistration (part 2/2)
>
> Device managed registration generally only works if all involved
> resources are managed as otherwise resources may be disabled or freed
> while they are still in use.
>
> This series fixes the SPI controller drivers that get this wrong by
> disabling resources such as clocks, DMA and interrupts while the
> controller (and its devices) are still registered, which can lead to
> issues like system errors due to unclocked accesses, NULL-pointer
> dereferences, hangs or just prevent SPI device drivers from doing I/O
> during during deregistration (e.g. to power down devices).
>
> [...]

Applied to

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

Thanks!

[01/26] spi: mt65xx: fix controller deregistration
https://git.kernel.org/broonie/spi/c/2ad30599cccc
[02/26] spi: mtk-nor: fix controller deregistration
https://git.kernel.org/broonie/spi/c/76336f249346
[03/26] spi: mxs: fix controller deregistration
https://git.kernel.org/broonie/spi/c/8b0d0011af20
[04/26] spi: npcm-pspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/ebd81199e00e
[05/26] spi: omap2-mcspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/fb45f95c377e
[06/26] spi: pic32: fix controller deregistration
https://git.kernel.org/broonie/spi/c/6b627bfe0c44
[07/26] spi: pic32-sqi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/420df79d1a61
[08/26] spi: pl022: fix controller deregistration
https://git.kernel.org/broonie/spi/c/994b33366be9
[09/26] spi: qup: fix controller deregistration
https://git.kernel.org/broonie/spi/c/443e3a0005a4
[10/26] spi: rspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/9944fa6726af
[11/26] spi: s3c64xx: fix controller deregistration
https://git.kernel.org/broonie/spi/c/c1446b61e472
[12/26] spi: sh-hspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/e63982e6392e
[13/26] spi: sh-msiof: fix controller deregistration
https://git.kernel.org/broonie/spi/c/45170f67a08b
[14/26] spi: sifive: fix controller deregistration
https://git.kernel.org/broonie/spi/c/0f25236694a2
[15/26] spi: slave-mt27xx: fix controller deregistration
https://git.kernel.org/broonie/spi/c/ab840cbda4fe
[16/26] spi: sprd: fix controller deregistration
https://git.kernel.org/broonie/spi/c/123d17dbc5f0
[17/26] spi: st-ssc4: fix controller deregistration
https://git.kernel.org/broonie/spi/c/19857374010d
[18/26] spi: sun4i: fix controller deregistration
https://git.kernel.org/broonie/spi/c/42108a2f03e0
[19/26] spi: sun6i: fix controller deregistration
https://git.kernel.org/broonie/spi/c/d874a1c33aee
[20/26] spi: syncuacer: fix controller deregistration
https://git.kernel.org/broonie/spi/c/75d849c3452e
[21/26] spi: tegra114: fix controller deregistration
https://git.kernel.org/broonie/spi/c/9c9c27ff2058
[22/26] spi: tegra20-sflash: fix controller deregistration
https://git.kernel.org/broonie/spi/c/ad7310e98332
[23/26] spi: ti-qspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/0c18a1bacbb1
[24/26] spi: uniphier: fix controller deregistration
https://git.kernel.org/broonie/spi/c/0245435f7772
[25/26] spi: zynqmp-gqspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/6895fc4faafc
[26/26] spi: zynq-qspi: fix controller deregistration
https://git.kernel.org/broonie/spi/c/c9c012706c9f

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