From: Ping-Ke Shih <pkshih@realtek.com>
To: <tony0620emma@gmail.com>, <kvalo@codeaurora.org>
Cc: <linux-wireless@vger.kernel.org>, <vincent_fann@realtek.com>
Subject: [PATCH 0/3] rtw89: 8822c: add GAPK
Date: Fri, 26 Mar 2021 15:29:23 +0800 [thread overview]
Message-ID: <20210326072926.28313-1-pkshih@realtek.com> (raw)
GAPK is used to calibrate RF character to make every module good
performance. With a debug switch, we can make sure if it helps in field.
Besides, we sort the register definition to make it looks better. Since
previous patchset "rtw88: add some fixes and 8822c features" also changes
the registers, I create this patchset based on the previous one, expecting
this patchset is merged later than it.
Guo-Feng Fan (3):
rtw88: 8822c: reorder macro position according to the register number
rtw88: 8822c: Add gap-k calibration to improve long range performance
rtw88: 8822c: debug: allow debugfs to enable/disable TXGAPK
drivers/net/wireless/realtek/rtw88/debug.c | 91 +++
drivers/net/wireless/realtek/rtw88/fw.c | 12 +
drivers/net/wireless/realtek/rtw88/fw.h | 5 +
drivers/net/wireless/realtek/rtw88/main.h | 31 +
drivers/net/wireless/realtek/rtw88/reg.h | 8 +
drivers/net/wireless/realtek/rtw88/rtw8822c.c | 724 +++++++++++++++++-
drivers/net/wireless/realtek/rtw88/rtw8822c.h | 336 ++++----
7 files changed, 1065 insertions(+), 142 deletions(-)
--
2.21.0
next reply other threads:[~2021-03-26 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 7:29 Ping-Ke Shih [this message]
2021-03-26 7:29 ` [PATCH 1/3] rtw88: 8822c: reorder macro position according to the register number Ping-Ke Shih
2021-04-18 6:30 ` Kalle Valo
2021-03-26 7:29 ` [PATCH 2/3] rtw88: 8822c: Add gap-k calibration to improve long range performance Ping-Ke Shih
2021-03-26 7:29 ` [PATCH 3/3] rtw88: 8822c: debug: allow debugfs to enable/disable TXGAPK 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=20210326072926.28313-1-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tony0620emma@gmail.com \
--cc=vincent_fann@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).