From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Cc: <kevin_yang@realtek.com>
Subject: [PATCH rtw-next 0/6] wifi: rtw89: fw: reduce memory use of firmware, and support board file
Date: Wed, 23 Sep 2026 13:44:59 +0800 [thread overview]
Message-ID: <20260923054505.43329-1-pkshih@realtek.com> (raw)
The first three patches aim to reduce memory use of firmware, because
RTL8922D has many variants and each of them uses different firmware.
Therefore, firmware binary file becomes large, but actually only need
one copy to specific variant. Duplicate the necessary part and persistent
them, and free memory allocated by request_firmware() after device
probes done.
The other three patches are to define TX power values (for now) by an
external a board file corresponding to a specific board (with specific
VID/PID). This is necessary because TX power values depends on board
(module) design, not on chip only. Add this as a initial work to make it
possible to record settings for customized module (not standard PCIE
module).
Ping-Ke Shih (3):
wifi: rtw89: fw: duplicate recognized firmware elements
wifi: rtw89: fw: release firmware after recognizing firmware elements
wifi: rtw89: fw: duplicate firmware suit data by vmalloc to reduce
memory fragment
Zong-Zhe Yang (3):
wifi: rtw89: led: check if board variant assigns led desc
wifi: rtw89: support variants of FW elements
wifi: rtw89: 8852cu: take board ID 1 for FW elements 28de/2432
drivers/net/wireless/realtek/rtw89/core.c | 6 +
drivers/net/wireless/realtek/rtw89/core.h | 19 ++
drivers/net/wireless/realtek/rtw89/fw.c | 252 +++++++++++++++---
drivers/net/wireless/realtek/rtw89/fw.h | 15 ++
drivers/net/wireless/realtek/rtw89/led.c | 2 +-
.../net/wireless/realtek/rtw89/rtw8852cu.c | 1 +
6 files changed, 253 insertions(+), 42 deletions(-)
base-commit: 2f77c66694108785a1f6ae6c5de06453e7f7a91f
--
2.25.1
next reply other threads:[~2026-09-23 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 5:44 Ping-Ke Shih [this message]
2026-09-23 5:45 ` [PATCH rtw-next 1/6] wifi: rtw89: fw: duplicate recognized firmware elements Ping-Ke Shih
2026-09-30 1:56 ` Ping-Ke Shih
2026-09-23 5:45 ` [PATCH rtw-next 2/6] wifi: rtw89: fw: release firmware after recognizing " Ping-Ke Shih
2026-09-23 5:45 ` [PATCH rtw-next 3/6] wifi: rtw89: fw: duplicate firmware suit data by vmalloc to reduce memory fragment Ping-Ke Shih
2026-09-23 5:45 ` [PATCH rtw-next 4/6] wifi: rtw89: led: check if board variant assigns led desc Ping-Ke Shih
2026-09-23 5:45 ` [PATCH rtw-next 5/6] wifi: rtw89: support variants of FW elements Ping-Ke Shih
2026-09-23 5:45 ` [PATCH rtw-next 6/6] wifi: rtw89: 8852cu: take board ID 1 for FW elements 28de/2432 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=20260923054505.43329-1-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=kevin_yang@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