From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Karun Eagalapati <karun256@gmail.com>,
Amitkumar Karwar <amit.karwar@redpinesignals.com>,
Kalle Valo <kvalo@codeaurora.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: [PATCH v1 0/4] sdio: Use bus type function for shutdown
Date: Wed, 17 Dec 2025 12:09:22 +0100 [thread overview]
Message-ID: <cover.1765968841.git.ukleinek@kernel.org> (raw)
Hello,
this series is part of an effort to get rid of the .shutdown() callback
(and .probe() and .remove()) in struct device_driver. Preparing that,
all sdio drivers that up to now use this callback are converted to a new
sdio specific shutdown callback.
Patch #2 is just a cleanup I noticed while working on
drivers/net/wireless/rsi/rsi_91x_sdio.c. Note that it's uncommon to have
the shutdown callback conditionalized by #ifdef CONFIG_PM. I guess this
dependency was introduced by mistake in commit 063848c3e155 ("rsi: sdio:
Add WOWLAN support for S5 shutdown state"), but I didn't address it
here.
Patches #3 and #4 depend on the first patch, and with just the first
patch applied there is a runtime warning (emitted by the driver core in
driver_register()) for each unconverted driver. So it would be nice to
get the whole series in during a single merge window to not let users
face the warning.
This series was build tested on amd64 and arm64 using allmodconfig.
Best regards
Uwe
Uwe Kleine-König (4):
sdio: Provide a bustype shutdown function
wifi: rsi: sdio: Reduce use of #ifdef for CONFIG_PM
wifi: rsi: sdio: Migrate to use sdio specific shutdown function
wifi: rtw88: sdio: Migrate to use sdio specific shutdown function
drivers/mmc/core/sdio_bus.c | 25 +++++++++++++++++++
.../net/wireless/realtek/rtw88/rtw8723cs.c | 2 +-
.../net/wireless/realtek/rtw88/rtw8723ds.c | 2 +-
.../net/wireless/realtek/rtw88/rtw8821cs.c | 2 +-
.../net/wireless/realtek/rtw88/rtw8822bs.c | 2 +-
.../net/wireless/realtek/rtw88/rtw8822cs.c | 2 +-
drivers/net/wireless/realtek/rtw88/sdio.c | 3 +--
drivers/net/wireless/realtek/rtw88/sdio.h | 2 +-
drivers/net/wireless/rsi/rsi_91x_sdio.c | 11 +++-----
include/linux/mmc/sdio_func.h | 1 +
10 files changed, 36 insertions(+), 16 deletions(-)
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
--
2.47.3
next reply other threads:[~2025-12-17 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:09 Uwe Kleine-König [this message]
2025-12-17 11:09 ` [PATCH v1 2/4] wifi: rsi: sdio: Reduce use of #ifdef for CONFIG_PM Uwe Kleine-König
2025-12-20 16:20 ` kernel test robot
2025-12-20 17:59 ` kernel test robot
2025-12-29 10:36 ` Johannes Berg
2025-12-30 18:56 ` Uwe Kleine-König
2025-12-17 11:09 ` [PATCH v1 3/4] wifi: rsi: sdio: Migrate to use sdio specific shutdown function Uwe Kleine-König
2025-12-19 12:24 ` Ulf Hansson
2025-12-17 11:09 ` [PATCH v1 4/4] wifi: rtw88: " Uwe Kleine-König
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=cover.1765968841.git.ukleinek@kernel.org \
--to=u.kleine-koenig@baylibre.com \
--cc=amit.karwar@redpinesignals.com \
--cc=karun256@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).