From: <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Cc: <damon.chen@realtek.com>
Subject: [PATCH rtw-next 0/8] wifi: rtw89: update rate/bw/GI for injection, and add diagnosis to debugfs
Date: Tue, 4 Nov 2025 17:14:05 +0800 [thread overview]
Message-ID: <1762247653-26864-1-git-send-email-pkshih@realtek.com> (raw)
From: Ping-Ke Shih <pkshih@realtek.com>
First three patches are to add diagnosis to debugfs. This feature is to
provide hints to see if MAC hardware went wrong to assist debugging quickly.
Patches 6-8 are related to monitor mode. First is to support injection with
rate/bw/GI. Second is to do calibration on the channel running monitor mode
to have better receiving performance. Third is to configure RX antenna, so
we can test RX performance individually.
Others are patch 4 which implements extension of thermal value programmed
in efuse, and patch 5 fixes Coverity warnings.
Kuan-Chung Chen (1):
wifi: rtw89: phy: fix out-of-bounds access in
rtw89_phy_read_txpwr_limit()
Ping-Ke Shih (7):
wifi: rtw89: pci: add to read PCI configuration space from common code
wifi: rtw89: fw: parse firmware element of DIAG_MAC
wifi: rtw89: debug: add parser to diagnose along DIAG_MAC fw element
wifi: rtw89: 8852c: add compensation of thermal value from efuse
calibration
wifi: rtw89: consider data rate/bandwidth/GI for injected packets
wifi: rtw89: do RF calibration once setting channel when running pure
monitor mode
wifi: rtw89: configure RX antenna if chips can support
drivers/net/wireless/realtek/rtw89/core.c | 85 +++++
drivers/net/wireless/realtek/rtw89/core.h | 17 +
drivers/net/wireless/realtek/rtw89/debug.c | 299 ++++++++++++++++++
drivers/net/wireless/realtek/rtw89/fw.c | 15 +
drivers/net/wireless/realtek/rtw89/fw.h | 6 +
drivers/net/wireless/realtek/rtw89/mac.h | 2 -
drivers/net/wireless/realtek/rtw89/mac80211.c | 9 +
drivers/net/wireless/realtek/rtw89/pci.c | 16 +
drivers/net/wireless/realtek/rtw89/phy.c | 20 ++
.../wireless/realtek/rtw89/rtw8852b_common.c | 6 +-
drivers/net/wireless/realtek/rtw89/rtw8852c.c | 41 ++-
drivers/net/wireless/realtek/rtw89/rtw8922a.c | 12 +-
12 files changed, 517 insertions(+), 11 deletions(-)
--
2.25.1
next reply other threads:[~2025-11-04 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 9:14 pkshih [this message]
2025-11-04 9:14 ` [PATCH rtw-next 1/8] wifi: rtw89: pci: add to read PCI configuration space from common code pkshih
2025-11-04 9:14 ` [PATCH rtw-next 2/8] wifi: rtw89: fw: parse firmware element of DIAG_MAC pkshih
2025-11-04 9:14 ` [PATCH rtw-next 3/8] wifi: rtw89: debug: add parser to diagnose along DIAG_MAC fw element pkshih
2025-11-04 9:14 ` [PATCH rtw-next 4/8] wifi: rtw89: 8852c: add compensation of thermal value from efuse calibration pkshih
2025-11-04 9:14 ` [PATCH rtw-next 5/8] wifi: rtw89: phy: fix out-of-bounds access in rtw89_phy_read_txpwr_limit() pkshih
2025-11-04 9:14 ` [PATCH rtw-next 6/8] wifi: rtw89: consider data rate/bandwidth/GI for injected packets pkshih
2025-11-04 9:14 ` [PATCH rtw-next 7/8] wifi: rtw89: do RF calibration once setting channel when running pure monitor mode pkshih
2025-11-04 9:14 ` [PATCH rtw-next 8/8] wifi: rtw89: configure RX antenna if chips can support 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=1762247653-26864-1-git-send-email-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=damon.chen@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 NNTP newsgroup(s).