From: Ping-Ke Shih <pkshih@realtek.com>
To: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"piotr.oniszczuk@gmail.com" <piotr.oniszczuk@gmail.com>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: RE: [PATCH rtw-next] wifi: rtw88: sdio: use indirect IO for device registers before power-on
Date: Mon, 24 Nov 2025 08:16:29 +0000 [thread overview]
Message-ID: <4562797ed9514344b562f7a8e58e6988@realtek.com> (raw)
In-Reply-To: <aSHrhbt29k6GJB8e@skv.local>
Andrey Skvortsov <andrej.skvortzov@gmail.com> wrote:
> Hi,
>
> This patch was recently backported to stable kernels (v6.12.58) and it broke
> wlan on PinePhone, that uses 8723cs SDIO chip. The same problem
> appears of course on latest 6.18-rc6. Reverting this change resolves
> the problem.
>
> ```
> $ sudo dmesg | grep -i rtw88
> [ 24.940551] rtw88_8723cs mmc1:0001:1: WOW Firmware version 11.0.0, H2C version 0
> [ 24.953085] rtw88_8723cs mmc1:0001:1: Firmware version 11.0.0, H2C version 0
> [ 24.955892] rtw88_8723cs mmc1:0001:1: sdio read32 failed (0xf0): -110
> [ 24.973135] rtw88_8723cs mmc1:0001:1: sdio write8 failed (0x1c): -110
> [ 24.980673] rtw88_8723cs mmc1:0001:1: sdio read32 failed (0xf0): -110
> ...
> [ 25.446691] rtw88_8723cs mmc1:0001:1: sdio read8 failed (0x100): -110
> [ 25.453569] rtw88_8723cs mmc1:0001:1: mac power on failed
> [ 25.459077] rtw88_8723cs mmc1:0001:1: failed to power on mac
> [ 25.464841] rtw88_8723cs mmc1:0001:1: failed to setup chip efuse info
> [ 25.464856] rtw88_8723cs mmc1:0001:1: failed to setup chip information
> [ 25.478341] rtw88_8723cs mmc1:0001:1: probe with driver rtw88_8723cs failed with error -114
> ```
>
Check original link of this patch [1] that 8822cs read incorrect from 0xf0
resulting in "rtw88_8822cs mmc1:0001:1: unsupported rf path (1)".
I wonder if we can add additional checking rule of chip ID, like:
--- a/drivers/net/wireless/realtek/rtw88/sdio.c
+++ b/drivers/net/wireless/realtek/rtw88/sdio.c
@@ -144,8 +144,10 @@ static u32 rtw_sdio_to_io_address(struct rtw_dev *rtwdev, u32 addr,
static bool rtw_sdio_use_direct_io(struct rtw_dev *rtwdev, u32 addr)
{
+ bool might_indirect_under_power_off = rtwdev->chip->id != RTW_CHIP_TYPE_8703B;
+
if (!test_bit(RTW_FLAG_POWERON, rtwdev->flags) &&
- !rtw_sdio_is_bus_addr(addr))
+ !rtw_sdio_is_bus_addr(addr) && might_indirect_under_power_off)
return false;
return !rtw_sdio_is_sdio30_supported(rtwdev) ||
[1] https://lore.kernel.org/linux-wireless/699C22B4-A3E3-4206-97D0-22AB3348EBF6@gmail.com/T/#t
next prev parent reply other threads:[~2025-11-24 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250724004815.7043-1-pkshih@realtek.com>
2025-11-22 16:57 ` [PATCH rtw-next] wifi: rtw88: sdio: use indirect IO for device registers before power-on Andrey Skvortsov
2025-11-24 8:16 ` Ping-Ke Shih [this message]
2025-11-24 23:08 ` Andrey Skvortsov
2025-11-25 0:36 ` Ping-Ke Shih
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=4562797ed9514344b562f7a8e58e6988@realtek.com \
--to=pkshih@realtek.com \
--cc=andrej.skvortzov@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=piotr.oniszczuk@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=rtl8821cerfe2@gmail.com \
--cc=stable@vger.kernel.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