Linux-Wireless Archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Ping-Ke Shih <pkshih@realtek.com>, <linux-wireless@vger.kernel.org>
Cc: <ku920601@realtek.com>
Subject: Re: [PATCH 1/9] wifi: rtw89: coex: Allow Bluetooth doing traffic during Wi-Fi scan
Date: Tue, 23 Apr 2024 20:00:06 +0800	[thread overview]
Message-ID: <bf6dede5-37ff-4405-923f-15ff90299abc@RTEXMBS04.realtek.com.tw> (raw)
In-Reply-To: <20240418021207.32173-2-pkshih@realtek.com>

Ping-Ke Shih <pkshih@realtek.com> wrote:

> From: Ching-Te Ku <ku920601@realtek.com>
> 
> The Wi-Fi/Bluetooth slot are toggled by firmware timer when Wi-Fi doing
> firmware scan, and Wi-Fi slot don't allow Bluetooth do traffic when
> Wi-Fi slot. It will trigger Bluetooth audio lag in a random rate, because
> Bluetooth can not have enough time slot to keep enough data to play audio.
> This patch make Bluetooth can do traffic during Wi-Fi slot, this can help
> Bluetooth to collect audio data in time.
> 
> Signed-off-by: Ching-Te Ku <ku920601@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>

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

a4f19fd7dcea wifi: rtw89: coex: Allow Bluetooth doing traffic during Wi-Fi scan
b5d8d19de284 wifi: rtw89: coex: Add v7 firmware cycle status report
ac83ba93b22d wifi: rtw89: coex: Add version 3 report map of H2C command
89d06325364a wifi: rtw89: coex: Add PTA path control condition for chip RTL8922A
c95d34c7d676 wifi: rtw89: coex: Update Bluetooth polluted Wi-Fi TX logic
b952cb0a6e2d wifi: rtw89: coex: Add register monitor report v7 format
de656c77c72e wifi: rtw89: coex: Add GPIO signal control version 7
45deb9e6a60b wifi: rtw89: coex: Add coexistence firmware control report version 8
4ea11e4db355 wifi: rtw89: coex: Re-order the index for the report from firmware

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


  reply	other threads:[~2024-04-23 12:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  2:11 [PATCH 0/9] wifi: rtw89: coex: update BT-coexistence mechanism for 8922A Ping-Ke Shih
2024-04-18  2:11 ` [PATCH 1/9] wifi: rtw89: coex: Allow Bluetooth doing traffic during Wi-Fi scan Ping-Ke Shih
2024-04-23 12:00   ` Ping-Ke Shih [this message]
2024-04-18  2:12 ` [PATCH 2/9] wifi: rtw89: coex: Add v7 firmware cycle status report Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 3/9] wifi: rtw89: coex: Add version 3 report map of H2C command Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 4/9] wifi: rtw89: coex: Add PTA path control condition for chip RTL8922A Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 5/9] wifi: rtw89: coex: Update Bluetooth polluted Wi-Fi TX logic Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 6/9] wifi: rtw89: coex: Add register monitor report v7 format Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 7/9] wifi: rtw89: coex: Add GPIO signal control version 7 Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 8/9] wifi: rtw89: coex: Add coexistence firmware control report version 8 Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 9/9] wifi: rtw89: coex: Re-order the index for the report from firmware Ping-Ke Shih

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=bf6dede5-37ff-4405-923f-15ff90299abc@RTEXMBS04.realtek.com.tw \
    --to=pkshih@realtek.com \
    --cc=ku920601@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).