From: <pkshih@realtek.com>
To: <kvalo@codeaurora.org>
Cc: <tony0620emma@gmail.com>, <ku920601@realtek.com>,
<linux-wireless@vger.kernel.org>
Subject: [PATCH v2 00/10] rtw88: coex: enhance coex performance and synchronize coex code
Date: Thu, 26 Nov 2020 10:10:49 +0800 [thread overview]
Message-ID: <20201126021059.11981-1-pkshih@realtek.com> (raw)
From: Ping-Ke Shih <pkshih@realtek.com>
This is the last patchset of my total 32 coex patches, fixing some issues
to improve user experience in field. And, some patches synchronized the
code from our internal tree are necessary for us to merge fixes, though
they doesn't really affect the behavior for now.
v2:
* fix "set but not used" warnings reported by kernel test robot on
"[PATCH 09/10] rtw88: coex: upgrade coexistence A2DP mechanism".
I move some variables to PATCH 10/10 because they are used there, and
delete others that are not used.
Ching-Te Ku (10):
rtw88: coex: run coexistence when WLAN entering/leaving LPS
rtw88: coex: add debug message
rtw88: coex: update the mechanism for A2DP + PAN
rtw88: coex: update AFH information while in free-run mode
rtw88: coex: change the coexistence mechanism for HID
rtw88: coex: change the coexistence mechanism for WLAN connected
rtw88: coex: add function to avoid cck lock
rtw88: coex: add action for coexistence in hardware initial
rtw88: coex: upgrade coexistence A2DP mechanism
rtw88: coex: add feature to enhance HID coexistence performance
drivers/net/wireless/realtek/rtw88/coex.c | 714 ++++++++++++++----
drivers/net/wireless/realtek/rtw88/coex.h | 6 +
drivers/net/wireless/realtek/rtw88/debug.c | 23 +
drivers/net/wireless/realtek/rtw88/debug.h | 1 +
drivers/net/wireless/realtek/rtw88/main.c | 5 +
drivers/net/wireless/realtek/rtw88/main.h | 21 +
drivers/net/wireless/realtek/rtw88/rtw8723d.c | 1 +
drivers/net/wireless/realtek/rtw88/rtw8821c.c | 1 +
drivers/net/wireless/realtek/rtw88/rtw8822b.c | 1 +
drivers/net/wireless/realtek/rtw88/rtw8822c.c | 1 +
10 files changed, 618 insertions(+), 156 deletions(-)
--
2.21.0
next reply other threads:[~2020-11-26 2:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 2:10 pkshih [this message]
2020-11-26 2:10 ` [PATCH v2 01/10] rtw88: coex: run coexistence when WLAN entering/leaving LPS pkshih
2020-12-02 19:24 ` Kalle Valo
2020-11-26 2:10 ` [PATCH v2 02/10] rtw88: coex: add debug message pkshih
2020-11-26 2:10 ` [PATCH v2 03/10] rtw88: coex: update the mechanism for A2DP + PAN pkshih
2020-11-26 2:10 ` [PATCH v2 04/10] rtw88: coex: update AFH information while in free-run mode pkshih
2020-11-26 2:10 ` [PATCH v2 05/10] rtw88: coex: change the coexistence mechanism for HID pkshih
2020-11-26 2:10 ` [PATCH v2 06/10] rtw88: coex: change the coexistence mechanism for WLAN connected pkshih
2020-11-26 2:10 ` [PATCH v2 07/10] rtw88: coex: add function to avoid cck lock pkshih
2020-11-26 2:10 ` [PATCH v2 08/10] rtw88: coex: add action for coexistence in hardware initial pkshih
2020-11-26 2:10 ` [PATCH v2 09/10] rtw88: coex: upgrade coexistence A2DP mechanism pkshih
2020-11-26 2:10 ` [PATCH v2 10/10] rtw88: coex: add feature to enhance HID coexistence performance pkshih
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=20201126021059.11981-1-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=ku920601@realtek.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tony0620emma@gmail.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;
as well as URLs for NNTP newsgroup(s).