mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	<linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] wifi: rtw89: retry efuse physical map dump on transient failure
Date: Mon, 30 Mar 2026 09:44:43 +0800	[thread overview]
Message-ID: <a8a595ce-9795-4b78-938b-350cfbe26d6a@RTKEXHMBS04.realtek.com.tw> (raw)
In-Reply-To: <20260317112155.1939569-1-christianshewitt@gmail.com>

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.
> 
> The root cause is a timing race during boot: the WiFi driver's
> chip initialization (firmware download via PCIe) overlaps with
> Bluetooth firmware download to the same combo chip via USB. This
> can leave the efuse controller temporarily unavailable when the
> WiFi driver attempts to read the efuse map.
> 
> The firmware download path retries up to 5 times, but the efuse
> read that follows has no similar logic. Address this by adding
> retry loop logic (also up to 5 attempts) around physical efuse
> map dump.
> 
> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>

1 patch(es) applied to rtw-next branch of rtw.git, thanks.

d92f6ad6483e wifi: rtw89: retry efuse physical map dump on transient failure

---
https://github.com/pkshih/rtw.git


      reply	other threads:[~2026-03-30  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 11:21 Christian Hewitt
2026-03-30  1:44 ` Ping-Ke Shih [this message]

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=a8a595ce-9795-4b78-938b-350cfbe26d6a@RTKEXHMBS04.realtek.com.tw \
    --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

all inboxes | Powered by JetHome®