From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Subject: [PATCH rtw-next 0/9] wifi: rtw89: 8922d: add RTL8922DE part 2/2
Date: Mon, 30 Mar 2026 14:58:38 +0800 [thread overview]
Message-ID: <20260330065847.48946-1-pkshih@realtek.com> (raw)
Add part 2/2 of RTL8922DE, but yet enable it by Kconfig/Makefile because
we are still developing and testing BT coexistence mechanism, which is a
shared component and can affect all existing chips. Otherwise, RTL8922DE
can work with the highest rate and STA/AP modes.
Since we are continuously adjusting common flow to support new hardware
settings of RTL8922D, I'd add RTL8922D first followed by patches of new
settings, so people can be easier to understand why/how actually it does.
Ping-Ke Shih (9):
wifi: rtw89: 8922d: BB hardware pre-/post-init, TX/RX path and power
settings
wifi: rtw89: 8922d: add set channel with pre-/post- helpers
wifi: rtw89: 8922d: add RF calibration ops
wifi: rtw89: 8922d: add set TX power callback
wifi: rtw89: 8922d: configure TX/RX path assisting in BT coexistence
wifi: rtw89: 8922d: add RF ops of init hardware and get thermal
wifi: rtw89: 8922d: add ops related to BT coexistence mechanism
wifi: rtw89: 8922d: add chip_info and chip_ops struct
wifi: rtw89: 8922d: add PCI ID of RTL8922DE and RTL8922DE-VS
drivers/net/wireless/realtek/rtw89/core.h | 21 +
drivers/net/wireless/realtek/rtw89/fw.h | 23 +-
drivers/net/wireless/realtek/rtw89/pci.h | 3 +
drivers/net/wireless/realtek/rtw89/reg.h | 127 +-
drivers/net/wireless/realtek/rtw89/rtw8851b.c | 4 +
drivers/net/wireless/realtek/rtw89/rtw8852a.c | 4 +
drivers/net/wireless/realtek/rtw89/rtw8852b.c | 4 +
.../net/wireless/realtek/rtw89/rtw8852bt.c | 4 +
drivers/net/wireless/realtek/rtw89/rtw8852c.c | 4 +
drivers/net/wireless/realtek/rtw89/rtw8922a.c | 4 +
drivers/net/wireless/realtek/rtw89/rtw8922d.c | 1338 +++++++++++++++++
drivers/net/wireless/realtek/rtw89/rtw8922d.h | 3 +
.../net/wireless/realtek/rtw89/rtw8922d_rfk.c | 339 +++++
.../net/wireless/realtek/rtw89/rtw8922d_rfk.h | 8 +
.../net/wireless/realtek/rtw89/rtw8922de.c | 119 ++
15 files changed, 1996 insertions(+), 9 deletions(-)
create mode 100644 drivers/net/wireless/realtek/rtw89/rtw8922de.c
base-commit: 658e3c836969e1624a7572c75684f54ec503c2ed
--
2.25.1
next reply other threads:[~2026-03-30 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 6:58 Ping-Ke Shih [this message]
2026-03-30 6:58 ` [PATCH rtw-next 1/9] wifi: rtw89: 8922d: BB hardware pre-/post-init, TX/RX path and power settings Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 2/9] wifi: rtw89: 8922d: add set channel with pre-/post- helpers Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 3/9] wifi: rtw89: 8922d: add RF calibration ops Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 4/9] wifi: rtw89: 8922d: add set TX power callback Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 5/9] wifi: rtw89: 8922d: configure TX/RX path assisting in BT coexistence Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 6/9] wifi: rtw89: 8922d: add RF ops of init hardware and get thermal Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 7/9] wifi: rtw89: 8922d: add ops related to BT coexistence mechanism Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 8/9] wifi: rtw89: 8922d: add chip_info and chip_ops struct Ping-Ke Shih
2026-03-30 6:58 ` [PATCH rtw-next 9/9] wifi: rtw89: 8922d: add PCI ID of RTL8922DE and RTL8922DE-VS 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=20260330065847.48946-1-pkshih@realtek.com \
--to=pkshih@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