From: Ping-Ke Shih <pkshih@realtek.com>
To: "Ondřej Jirman" <megi@xff.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "open list:REALTEK WIRELESS DRIVER (rtw89)"
<linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] net: wireless: rtw89: Sleep while waiting for firmware init
Date: Wed, 10 Sep 2025 00:37:54 +0000 [thread overview]
Message-ID: <4a3f6b40a0064de1acd80f4eeb1cdd0f@realtek.com> (raw)
In-Reply-To: <20250909211255.1486851-1-megi@xff.cz>
Ondřej Jirman <megi@xff.cz> wrote:
> From: Ondrej Jirman <megi@xff.cz>
>
> This avoids RCU stalls caused by waiting up to 400ms for firmware init.
>
> Signed-off-by: Ondrej Jirman <megi@xff.cz>
> ---
> drivers/net/wireless/realtek/rtw89/fw.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtw89/fw.c b/drivers/net/wireless/realtek/rtw89/fw.c
> index 16e59a4a486e..2c034b764a0a 100644
> --- a/drivers/net/wireless/realtek/rtw89/fw.c
> +++ b/drivers/net/wireless/realtek/rtw89/fw.c
> @@ -109,9 +109,9 @@ int rtw89_fw_check_rdy(struct rtw89_dev *rtwdev, enum rtw89_fwdl_check_type type
> u8 val;
> int ret;
>
> - ret = read_poll_timeout_atomic(mac->fwdl_get_status, val,
> - val == RTW89_FWDL_WCPU_FW_INIT_RDY,
> - 1, FWDL_WAIT_CNT, false, rtwdev, type);
> + ret = read_poll_timeout(mac->fwdl_get_status, val,
> + val == RTW89_FWDL_WCPU_FW_INIT_RDY,
> + 1, FWDL_WAIT_CNT, false, rtwdev, type);
As I know, sleeping while RCU lock is not allowed. Please share kernel log
about the RCU stall and your perspective.
> if (ret) {
> switch (val) {
> case RTW89_FWDL_CHECKSUM_FAIL:
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-09-10 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 21:12 [PATCH] net: wireless: rtw89: Sleep while waiting for firmware init Ondřej Jirman
2025-09-10 0:37 ` Ping-Ke Shih [this message]
2025-09-10 8:57 ` Ondřej Jirman
2025-09-11 2:46 ` 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=4a3f6b40a0064de1acd80f4eeb1cdd0f@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=megi@xff.cz \
/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