RE: [PATCH rtw-next 00/12] wifi: rtw89: Add support for RTL8922AU

[Ping-Ke Shih <pkshih@realtek.com>]

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> 
> On 02/04/2026 03:48, Ping-Ke Shih wrote:
> > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >> On 30/03/2026 05:53, Ping-Ke Shih wrote:
> >>> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >>>> Often one or more of these messages appears when the chip powers on:
> >>>>
> >>>> [  +2.167037] rtw89_8922au 1-2:1.0: failed to wait RF DACK
> >>>>
> >>>> [  +2.942749] rtw89_8922au 1-2:1.0: failed to wait RF TSSI
> >>>>
> >>>> [  +0.019006] rtw89_8922au 2-4:1.0: failed to wait RF PRE_NTFY
> >>>>
> >>>> [  +5.985900] rtw89_8922au 2-4:1.0: failed to wait RF DPK
> >>>>
> >>>> It's unclear why.
> >>>
> >>> RTL8922D done RF calibrations by firmware one by one, so driver should
> >>> wait for previous one done, and trigger next one. However, it'd be
> >>> well to just do waiting at the last to wait for all calibrations.
> >>>
> >>> Try to enlarge waiting time in rtw8922a_rfk_channel().
> >>>
> >>
> >> I was convinced I tried that already, but no.
> >>
> >> After increasing all delays a bit the warnings are much more rare.
> >
> > Turn of debug mask RTW89_DBG_RFK and set a very large timeout time, and
> > do connection >20 times and then check "RF %s takes %lld ms to complete"
> > to see the maximum value in your environment.
> >
> > Please share the number for each RF calibration after your experiments.
> >
> 
> I changed every delay to 500, then ran this, once with the adapter in
> USB 2, once in USB 3:
> 
> for i in {01..20}; do nmcli connection up "<2.4 GHz SSID>"; sleep 10; nmcli connection up "<5 GHz SSID>";
> sleep 10; done
> 
> There were no "failed to wait RF" warnings.
> 
> These are the results after processing with "sort --unique":
> 
> RF DACK takes 15 ms to complete
> RF DACK takes 16 ms to complete
> RF DACK takes 44 ms to complete
> RF DACK takes 72 ms to complete
> 
> RF DPK takes 23 ms to complete
> RF DPK takes 24 ms to complete
> RF DPK takes 27 ms to complete
> RF DPK takes 30 ms to complete
> 
> RF IQK takes 48 ms to complete
> RF IQK takes 49 ms to complete
> RF IQK takes 50 ms to complete
> 
> RF PRE_NTFY takes 0 ms to complete
> RF PRE_NTFY takes 1 ms to complete
> 
> RF RX_DCK takes 8 ms to complete
> RF RX_DCK takes 9 ms to complete
> RF RX_DCK takes 11 ms to complete
> RF RX_DCK takes 23 ms to complete
> RF RX_DCK takes 24 ms to complete
> RF RX_DCK takes 27 ms to complete
> RF RX_DCK takes 38 ms to complete
> RF RX_DCK takes 39 ms to complete
> RF RX_DCK takes 53 ms to complete
> RF RX_DCK takes 54 ms to complete
> RF RX_DCK takes 58 ms to complete
> RF RX_DCK takes 70 ms to complete
> RF RX_DCK takes 110 ms to complete
> 
> RF TSSI takes 1 ms to complete
> RF TSSI takes 2 ms to complete
> RF TSSI takes 23 ms to complete
> RF TSSI takes 24 ms to complete
> 
> RF TXGAPK takes 9 ms to complete
> RF TXGAPK takes 10 ms to complete
> RF TXGAPK takes 17 ms to complete
> RF TXGAPK takes 18 ms to complete
> 
> I also left it unconnected and constantly scanning for a few minutes.
> RTW89_TSSI_SCAN always takes 1-2 ms.
> 

You can make a set of number or a constant multiple for USB devices.
As we want hardware restart flow including RF calibration within a
limited time, I'd not enlarge these numbers for PCIE devices. 

Ping-Ke