From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rtits2.realtek.com.tw (rtits2.realtek.com [211.75.126.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E4A6E1E8320; Mon, 30 Mar 2026 01:44:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=211.75.126.72 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774835089; cv=none; b=hOh8l1brRfouNS8fPnGu1GSBLoRblLAXPwtvEZi5W0t6LW8YJVNVhi4x1/EBheNMo72s0lcq/F3LrEbUwwk78NCaljyx0ez64Ifgx01ADJd5OMeceXVoSUeNrPLSHbLrJSerzeyzWBgXjPWi6Y2tA8FDASqKRAm6hOPkw55nmjc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774835089; c=relaxed/simple; bh=YwKFXyJIdB7x73K8gZrHbKPZ6HGYmpaoUwCG+gcv06Y=; h=From:To:Subject:In-Reply-To:References:Message-ID:Date: MIME-Version:Content-Type; b=BSElNI+5RbZumW3wDbYtj4VoTSFJAlIRXsbLDMlZWTFcWH47oMRfBPa7tqf/l4TyOwmd05F6mf562oBj+FAss0/4+4R6IB870vlYGVb6jQxKKw0lwksxnZrZlUpNkYeSNNvFXv/tGvZCaIqN7e56mbo01N6M6nrsGWR9QsUsryc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=realtek.com; spf=pass smtp.mailfrom=realtek.com; dkim=pass (2048-bit key) header.d=realtek.com header.i=@realtek.com header.b=Bz+xWtOb; arc=none smtp.client-ip=211.75.126.72 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=realtek.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=realtek.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=realtek.com header.i=@realtek.com header.b="Bz+xWtOb" X-SpamFilter-By: ArmorX SpamTrap 5.80 with qID 62U1ihSdB068335, This message is accepted by code: ctloc85258 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=realtek.com; s=dkim; t=1774835083; bh=Gq2uvplEJb3FjVhRqm4hGrcdqstxpPiAifLXEOZfwYc=; h=From:To:Subject:In-Reply-To:References:Message-ID:Date: MIME-Version:Content-Type; b=Bz+xWtObJ5x9jCru4xBxegyiEaAdI38qDPU2Uue4K2M6ZBuSKBUAxcYeP/D+KMyfT lM4mPDTPCQDOyOTRoDuvvEM0I8OQ1zADM28zdBhnUxaQbVN5jRdQ9r2nUVYSzU6Y/T tgFPS2Y0yWunobjjPMeUNVtBZpzviYKUQ4Kg+U/WLURaqP1Husg3Vkik8UfoUZfJQn ip5ktBaHQPpYqW4ccqhpaGa+PrjIy4xufp8yGuPn4zZm5mKArZU7iOImwZ/WJ9DBeB M6EEukQ+X7VxAcsXnV3afzONIjJ1vG4if8FV4mExIauh5b9htrdWLgNv/e7hLQpdv1 Qfxuw+PIRPNyQ== Received: from mail.realtek.com (rtkexhmbs03.realtek.com.tw[10.21.1.53]) by rtits2.realtek.com.tw (8.15.2/3.26/5.94) with ESMTPS id 62U1ihSdB068335 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 30 Mar 2026 09:44:43 +0800 Received: from RTKEXHMBS04.realtek.com.tw (10.21.1.54) by RTKEXHMBS03.realtek.com.tw (10.21.1.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.10; Mon, 30 Mar 2026 09:44:43 +0800 Received: from [127.0.1.1] (172.21.40.75) by RTKEXHMBS04.realtek.com.tw (10.21.1.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.10 via Frontend Transport; Mon, 30 Mar 2026 09:44:43 +0800 From: Ping-Ke Shih To: Christian Hewitt , Ping-Ke Shih , Bitterblue Smith , , Subject: Re: [PATCH v2] wifi: rtw89: retry efuse physical map dump on transient failure In-Reply-To: <20260317112155.1939569-1-christianshewitt@gmail.com> References: <20260317112155.1939569-1-christianshewitt@gmail.com> Message-ID: Date: Mon, 30 Mar 2026 09:44:43 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Christian Hewitt 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 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