Linux wireless drivers development
 help / color / mirror / Atom feed
From: Maxim Skokov <skokovmaksimevg@gmail.com>
To: pkshih@realtek.com
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Maxim Skokov <skokovmaksimevg@gmail.com>
Subject: rtw89: BT connect state differs between scoreboard and bt_info on RTL8851B
Date: Tue, 15 Sep 2026 15:26:22 +0300	[thread overview]
Message-ID: <20260915122625.6341-1-skokovmaksimevg@gmail.com> (raw)

On RTL8851B with an A2DP sink connected and playing, btc_info shows
bt->link_info.status.map.connect flipping between Y and N, while the
scoreboard value stays the same:

  reason                connect   action     BT0->WL
  NTFY_RADIO_STATE      N         WL_OFF     0x40000013
  UPDATE_BT_INFO        Y         FREERUN    0x40000013
  UPDATE_BT_INFO        Y         FREERUN    0x40000013
  NTFY_RADIO_STATE      N         WL_OFF     0x40000013

BTC_BSCB_BT_CONNECT, BIT(16), is never set in BT0->WL, while the bt_info
mailbox reports the device as connected:

  [bt_info] : raw_data[49 00 d0 00 04 00]
              raw_info[2] = 0x49: connect=1, acl_busy=1, a2dp=1
              raw_info[6] = 0x04: a2dp_active=1

The field is written from both paths, _update_bt_info() and the
scoreboard read in _update_bt_scbd(), so it ends up holding whichever
event arrived last.

Is the scoreboard connect bit expected to be set by BT firmware here, or
is the mailbox the authoritative source and the scoreboard write
intentional?

WL_FW 0.29.41.3, BT_FW 0xf8ad230(patch), Coex 9.24.1, kernel 7.3.0-rc1.

             reply	other threads:[~2026-09-15 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 12:26 Maxim Skokov [this message]
2026-09-15 12:36 ` rtw89: BT connect state differs between scoreboard and bt_info on RTL8851B Maxim Skokov
2026-09-16  2:39   ` Ping-Ke Shih
2026-09-16  5:32     ` Maxim Skokov
2026-09-17  0:30       ` Ping-Ke Shih
2026-09-17  7:06         ` Maxim Skokov

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=20260915122625.6341-1-skokovmaksimevg@gmail.com \
    --to=skokovmaksimevg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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