From: Ping-Ke Shih <pkshih@realtek.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"andrej.skvortzov@gmail.com" <andrej.skvortzov@gmail.com>
Subject: RE: [PATCH rtw] wifi: rtw88: limit indirect IO under powered off for RTL8822CS
Date: Tue, 25 Nov 2025 01:40:56 +0000 [thread overview]
Message-ID: <799749958ece4b8e9a6f460c1b5aacac@realtek.com> (raw)
In-Reply-To: <1764034729-1251-1-git-send-email-pkshih@realtek.com>
Hi Andrey,
Ping-Ke Shih <pkshih@realtek.com> wrote:
(for record for patchwork)
The subject missed to point out "sdio: " which I will add during getting merged.
>
> The indirect IO is necessary for RTL8822CS, but not necessary for other
> chips. Otherwiese, it throws errors and becomes unusable.
>
> rtw88_8723cs mmc1:0001:1: WOW Firmware version 11.0.0, H2C version 0
> rtw88_8723cs mmc1:0001:1: Firmware version 11.0.0, H2C version 0
> rtw88_8723cs mmc1:0001:1: sdio read32 failed (0xf0): -110
> rtw88_8723cs mmc1:0001:1: sdio write8 failed (0x1c): -110
> rtw88_8723cs mmc1:0001:1: sdio read32 failed (0xf0): -110
>
> By vendor driver, only RTL8822CS and RTL8822ES need indirect IO, but
> RTL8822ES isn't supported yet. Therefore, limit it to RTL8822CS only.
>
> Reported-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
> Closes:
> https://lore.kernel.org/linux-wireless/07a32e2d6c764eb1bd9415b5a921a652@realtek.com/T/#m997b4522f7209b
> a629561c776bfd1d13ab24c1d4
> Fixes: 58de1f91e033 ("wifi: rtw88: sdio: use indirect IO for device registers before power-on")
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
Could you please test this patch and give a Tested-by tag if it can fix issue
you encountered?
next prev parent reply other threads:[~2025-11-25 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 1:38 [PATCH rtw] wifi: rtw88: limit indirect IO under powered off for RTL8822CS Ping-Ke Shih
2025-11-25 1:40 ` Ping-Ke Shih [this message]
2025-11-25 11:23 ` Andrey Skvortsov
2025-12-15 8:42 ` 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=799749958ece4b8e9a6f460c1b5aacac@realtek.com \
--to=pkshih@realtek.com \
--cc=andrej.skvortzov@gmail.com \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.