From: Ping-Ke Shih <pkshih@realtek.com>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: retry efuse physical map dump on transient failure
Date: Mon, 9 Mar 2026 02:35:56 +0000 [thread overview]
Message-ID: <5ad1b7d20d1745bab0638d15731e7ccd@realtek.com> (raw)
In-Reply-To: <903C7E52-033F-455E-89DC-B78C67C0C732@gmail.com>
Christian Hewitt <christianshewitt@gmail.com> wrote:
>
> > On 2 Mar 2026, at 10:04 am, Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > Christian Hewitt <christianshewitt@gmail.com> wrote:
> >>> On 2 Mar 2026, at 9:47 am, Ping-Ke Shih <pkshih@realtek.com> wrote:
> >>>
> >>> Christian Hewitt <christianshewitt@gmail.com> wrote:
> >>>> On Radxa Rock 5B with a RTL8852BE combo WiFi/BT card, the efuse
> >>>> physical map dump intermittently fails with -EBUSY during probe.
> >>>> The failure occurs in rtw89_dump_physical_efuse_map_ddv() where
> >>>> read_poll_timeout_atomic() times out waiting for the B_AX_EF_RDY
> >>>> bit after 1 second.
> >>>
> >>> I'm checking internally how we handle this case.
Sorry for the late.
We encountered WiFi/BT reading efuse at the same time causing similar
problem as yours. The workaround is like yours, which adds timeout
time.
> >>>
> >>> [...]
> >>>
> >>>>
> >>>> For context, firmware also fails (and recovers) sometimes:
> >>>
> >>> Did you mean this doesn't always happen? sometimes?
> >>
> >> It’s another intermittent behaviour observed on this board (and not
> >> related to the issue this patch targets). It occurs less frequently
> >> than the efuse issue and the existing retry mechanism in the driver
> >> ensures firmware load always succeeds.
This might be the same cause due to reading efuse in firmware.
Though we can add more timeout and retry times as workaround, I wonder
if you can control loading time of WiFi and BT kernel modules?
More, can you do experiment that you load BT module first, and then load
WiFi module after 10 seconds (choose a large number intentionally, or
even larger)?
Ping-Ke
next prev parent reply other threads:[~2026-03-09 2:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 4:24 [PATCH] wifi: rtw89: retry efuse physical map dump on transient failure Christian Hewitt
2026-03-02 5:47 ` Ping-Ke Shih
2026-03-02 5:55 ` Christian Hewitt
2026-03-02 6:04 ` Ping-Ke Shih
2026-03-02 6:17 ` Christian Hewitt
2026-03-09 2:35 ` Ping-Ke Shih [this message]
2026-03-10 17:16 ` Christian Hewitt
2026-03-11 3:05 ` Ping-Ke Shih
2026-03-11 4:20 ` Christian Hewitt
2026-03-12 2:22 ` Ping-Ke Shih
2026-03-12 5:58 ` Christian Hewitt
2026-03-12 7:39 ` Ping-Ke Shih
2026-03-12 8:11 ` Christian Hewitt
2026-03-12 8:28 ` Ping-Ke Shih
2026-03-16 5:32 ` Ping-Ke Shih
2026-03-16 11:03 ` Christian Hewitt
2026-03-17 1:37 ` Ping-Ke Shih
2026-03-17 6:15 ` Christian Hewitt
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=5ad1b7d20d1745bab0638d15731e7ccd@realtek.com \
--to=pkshih@realtek.com \
--cc=christianshewitt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.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