Re: rtw89: BT connect state differs between scoreboard and bt_info on RTL8851B

[Maxim Skokov <skokovmaksimevg@gmail.com>]

> To be clear. The problem you encountered was failed to connect an AP, or
> this was newly introduced by the patch I shared?

Not introduced by the patch. It predates it by a day.

On 15 September, with an unmodified driver, the same machine logged 21
"authentication timed out" and one 4WAY_HANDSHAKE_TIMEOUT in a single
boot, with an A2DP sink connected and playing:

  wlp2s0: authentication with 02:0c:43:16:60:e8 timed out
  wlp2s0: deauthenticated from b2:39:56:12:24:f0 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)

It follows the audio, not the driver build. With the sink stopped,
association completes in a few seconds on both the patched and the
unpatched module; while it plays, the interface stays in STA mode
retrying. That is the coexistence behaviour from the first mail in this
thread. I mentioned it in the last one only to describe the conditions of
the sampling, not as a regression.

> The BTC_BSCB_BT_CONNECT should be set by BT firmware. The internal BT
> expert is helping to dig the cause.

Understood. In case it is relevant to what they find, btc_info here
reports the BT side as

  [coex_version] : BT_FW_coex:0(Mismatch, desired:7)
  [sub_module]   : BT_FW:0x0(patch)

while the mailbox itself works, mailbox_avl:Y and raw_data updating.

I can run any test build you want on RTL8851BE.