From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Eddie James <eajames@linux.ibm.com>,
Yang Shen <shenyang39@huawei.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH 00/12] spi: switch to managed controller allocation (part 3/3)
Date: Mon, 11 May 2026 17:03:56 +0200 [thread overview]
Message-ID: <20260511150408.796155-1-johan@kernel.org> (raw)
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 managed registration to also
use managed allocation.
Included is also a related cleanup of a lp8841-rtc.
This 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 (12):
spi: altera-platform: switch to managed controller allocation
spi: armada-3700: switch to managed controller allocation
spi: clps711x: switch to managed controller allocation
spi: falcon: switch to managed controller allocation
spi: fsi: switch to managed controller allocation
spi: hisi-sfc-v3xx: switch to managed controller allocation
spi: jcore: switch to managed controller allocation
spi: lp8841-rtc: switch to managed controller allocation
spi: lp8841-rtc: drop unused ifdef
spi: meson-spifc: switch to managed controller allocation
spi: mux: switch to managed controller allocation
spi: xlp: switch to managed controller allocation
drivers/spi/spi-altera-platform.c | 27 +++++++------------
drivers/spi/spi-armada-3700.c | 44 ++++++++++---------------------
drivers/spi/spi-clps711x.c | 31 +++++++---------------
drivers/spi/spi-falcon.c | 8 ++----
drivers/spi/spi-fsi.c | 8 +++---
drivers/spi/spi-hisi-sfc-v3xx.c | 20 +++++---------
drivers/spi/spi-jcore.c | 23 +++++-----------
drivers/spi/spi-lp8841-rtc.c | 16 +++--------
drivers/spi/spi-meson-spifc.c | 22 ++++++----------
drivers/spi/spi-mux.c | 19 +++----------
drivers/spi/spi-xlp.c | 3 +--
11 files changed, 68 insertions(+), 153 deletions(-)
--
2.53.0
next reply other threads:[~2026-05-11 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:03 Johan Hovold [this message]
2026-05-11 15:03 ` [PATCH 01/12] spi: altera-platform: switch to managed controller allocation Johan Hovold
2026-05-11 15:03 ` [PATCH 02/12] spi: armada-3700: " Johan Hovold
2026-05-11 15:03 ` [PATCH 03/12] spi: clps711x: " Johan Hovold
2026-05-11 15:04 ` [PATCH 04/12] spi: falcon: " Johan Hovold
2026-05-11 15:04 ` [PATCH 05/12] spi: fsi: " Johan Hovold
2026-05-11 15:04 ` [PATCH 06/12] spi: hisi-sfc-v3xx: " Johan Hovold
2026-05-11 15:04 ` [PATCH 07/12] spi: jcore: " Johan Hovold
2026-05-11 15:04 ` [PATCH 08/12] spi: lp8841-rtc: " Johan Hovold
2026-05-11 15:04 ` [PATCH 09/12] spi: lp8841-rtc: drop unused ifdef Johan Hovold
2026-05-11 15:04 ` [PATCH 10/12] spi: meson-spifc: switch to managed controller allocation Johan Hovold
2026-05-11 15:04 ` [PATCH 11/12] spi: mux: " Johan Hovold
2026-05-11 15:04 ` [PATCH 12/12] spi: xlp: " Johan Hovold
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=20260511150408.796155-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=broonie@kernel.org \
--cc=eajames@linux.ibm.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=shenyang39@huawei.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