linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <kvalo@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <damon.chen@realtek.com>,
	<phhuang@realtek.com>
Subject: [PATCH 00/11] rtw89: add TDLS and various fixes
Date: Fri, 10 Jun 2022 15:25:59 +0800	[thread overview]
Message-ID: <20220610072610.27095-1-pkshih@realtek.com> (raw)

Patch 1/11 ~ 4/11 are related to TDLS. To support TDLS, we need to create
CAM entries like STA in AP mode. Besides, it also needs BSSID CAM by
hardware design.

The remaining patches are to fix various issues met in field, so fix them.

Since patches have dependency, I submit them together.

Kuan-Chung Chen (2):
  rtw89: fix potential TX stuck
  rtw89: enable VO TX AMPDU

Ping-Ke Shih (8):
  rtw89: allocate address CAM and MAC ID to TDLS peer
  rtw89: separate BSSID CAM operations
  rtw89: allocate BSSID CAM per TDLS peer
  rtw89: support TDLS
  rtw89: add UNEXP debug mask to keep monitor messages unexpected to
    happen frequently
  rtw89: drop invalid TX rate report of legacy rate
  rtw89: fix long RX latency in low power mode
  rtw89: pci: fix PCI doesn't reclaim TX BD properly

Po-Hao Huang (1):
  rtw89: disable invalid phy reports for all ICs

 drivers/net/wireless/realtek/rtw89/cam.c      |  29 ++--
 drivers/net/wireless/realtek/rtw89/cam.h      |   9 +-
 drivers/net/wireless/realtek/rtw89/core.c     | 148 +++++++++++++++---
 drivers/net/wireless/realtek/rtw89/core.h     |  33 +++-
 drivers/net/wireless/realtek/rtw89/debug.c    |   3 +-
 drivers/net/wireless/realtek/rtw89/debug.h    |   2 +
 drivers/net/wireless/realtek/rtw89/fw.c       |   2 +-
 drivers/net/wireless/realtek/rtw89/mac80211.c |   2 +-
 drivers/net/wireless/realtek/rtw89/pci.c      |  16 +-
 drivers/net/wireless/realtek/rtw89/phy.c      |  18 ++-
 drivers/net/wireless/realtek/rtw89/ser.c      |  15 +-
 11 files changed, 218 insertions(+), 59 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-06-10  7:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  7:25 Ping-Ke Shih [this message]
2022-06-10  7:26 ` [PATCH 01/11] rtw89: allocate address CAM and MAC ID to TDLS peer Ping-Ke Shih
2022-06-21  6:16   ` [01/11] wifi: " Kalle Valo
2022-06-10  7:26 ` [PATCH 02/11] rtw89: separate BSSID CAM operations Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 03/11] rtw89: allocate BSSID CAM per TDLS peer Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 04/11] rtw89: support TDLS Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 05/11] rtw89: fix potential TX stuck Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 06/11] rtw89: enable VO TX AMPDU Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 07/11] rtw89: add UNEXP debug mask to keep monitor messages unexpected to happen frequently Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 08/11] rtw89: drop invalid TX rate report of legacy rate Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 09/11] rtw89: fix long RX latency in low power mode Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 10/11] rtw89: pci: fix PCI doesn't reclaim TX BD properly Ping-Ke Shih
2022-06-10  7:26 ` [PATCH 11/11] rtw89: disable invalid phy reports for all ICs 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=20220610072610.27095-1-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=damon.chen@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@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;
as well as URLs for NNTP newsgroup(s).