From: Ping-Ke Shih <pkshih@realtek.com>
To: Ryan Walklin <ryan@testtoast.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>
Subject: RE: [BUG] RTL8821CS panic on entering power-save mode
Date: Wed, 13 Mar 2024 06:05:43 +0000 [thread overview]
Message-ID: <2afd1590823740a2b6a8f7e485a33842@realtek.com> (raw)
In-Reply-To: <f3656995-b8fe-49c4-93b7-67612c685954@app.fastmail.com>
> -----Original Message-----
> From: Ryan Walklin <ryan@testtoast.com>
> Sent: Wednesday, March 13, 2024 6:43 AM
> To: Ping-Ke Shih <pkshih@realtek.com>; linux-wireless@vger.kernel.org
> Cc: linux-sunxi@lists.linux.dev
> Subject: [BUG] RTL8821CS panic on entering power-save mode
>
> Hi,
>
> I have an Allwinner-H700-based platform (Anbernic RG35XX+) which I am working on mainline u-boot/kernel
> support for. The RGL8821CS chip on this board works when configured with a 32MHz clock and 3.3v VCC and
> the RTW88 kernel driver,
>
Did the extensive logging of LPS state happen always? Or happen after a while?
Try module parameter rtw_disable_lps_deep_mode=1 to see if it works well.
The IO of SDIO is slower than PCIE, so maybe we can try to enlarge timeout time
in rtw_power_mode_change():
diff --git a/drivers/net/wireless/realtek/rtw88/ps.c b/drivers/net/wireless/realtek/rtw88/ps.c
index add5a20b8432..d959e3ebba07 100644
--- a/drivers/net/wireless/realtek/rtw88/ps.c
+++ b/drivers/net/wireless/realtek/rtw88/ps.c
@@ -92,7 +92,7 @@ void rtw_power_mode_change(struct rtw_dev *rtwdev, bool enter)
/* Check firmware get the power requset and ack via cpwm register */
ret = read_poll_timeout_atomic(rtw_read8, polling,
(polling ^ confirm) & BIT_RPWM_TOGGLE,
- 100, 15000, true, rtwdev,
+ 100, 15000 * 100, true, rtwdev,
rtwdev->hci.cpwm_addr);
if (ret) {
/* Hit here means that driver failed to get an ack from firmware.
> however the BT is unstable with extensive logging about LPS state entry failures,
> and the driver will eventually crash with the following:
Not sure why this could lead crash, because it is only a warning.
Anyway, please try above suggestions.
Ping-Ke
next prev parent reply other threads:[~2024-03-13 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 22:42 [BUG] RTL8821CS panic on entering power-save mode Ryan Walklin
2024-03-13 6:05 ` Ping-Ke Shih [this message]
2024-03-13 20:11 ` [BUG] rtw88: RTL8821CS warning " Ryan Walklin
2024-03-15 9:30 ` [BUG] RTL8821CS panic " Ryan Walklin
2024-03-15 13:47 ` Ping-Ke Shih
2024-03-17 8:40 ` Ryan Walklin
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=2afd1590823740a2b6a8f7e485a33842@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=ryan@testtoast.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