linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <yhchuang@realtek.com>
To: <kvalo@codeaurora.org>
Cc: <linux-wireless@vger.kernel.org>, <pkshih@realtek.com>,
	<bigeasy@linutronix.de>
Subject: [PATCH v4 0/8] rtw88: 8723d: add BB related routines
Date: Mon, 4 May 2020 18:50:02 +0800	[thread overview]
Message-ID: <20200504105010.10780-1-yhchuang@realtek.com> (raw)

From: Yan-Hsuan Chuang <yhchuang@realtek.com>

Add BB related routines for 8723D.
The BB controls the channel, RX decoding, and RX gain. So, add DIG
parameters and RX descriptor parsing for the RX frames. And the false
alarm statistics help the driver to choose better DIG values.
The 8723D devices have more settings for CCK rates for DIG, mostly
because that the 8723D is 802.11n device.

The 8723D devices cannot recieve LDPC frames, do not advertise it.


v1 -> v2
  * make a patchset contains less patches for review

v2 -> v3
  * move defined macros to header file

v3 -> v4
  * rx ldpc cap fix
  * set channel flow refine


Ping-Ke Shih (8):
  rtw88: 8723d: Add DIG parameter
  rtw88: 8723d: Add query_rx_desc
  rtw88: 8723d: Add set_channel
  rtw88: handle C2H_CCX_TX_RPT to know if packet TX'ed successfully
  rtw88: 8723d: some chips don't support LDPC
  rtw88: 8723d: Add chip_ops::false_alarm_statistics
  rtw88: 8723d: Set IG register for CCK rate
  rtw88: 8723d: add interface configurations table

 drivers/net/wireless/realtek/rtw88/fw.c       |   6 +-
 drivers/net/wireless/realtek/rtw88/fw.h       |   7 +-
 drivers/net/wireless/realtek/rtw88/mac.c      |   3 +
 drivers/net/wireless/realtek/rtw88/main.c     |   9 +-
 drivers/net/wireless/realtek/rtw88/main.h     |   7 +
 drivers/net/wireless/realtek/rtw88/phy.c      |   4 +
 drivers/net/wireless/realtek/rtw88/rtw8723d.c | 376 ++++++++++++++++++
 drivers/net/wireless/realtek/rtw88/rtw8723d.h |  94 +++++
 drivers/net/wireless/realtek/rtw88/rtw8822b.c |   2 +
 drivers/net/wireless/realtek/rtw88/rtw8822c.c |   2 +
 drivers/net/wireless/realtek/rtw88/tx.c       |  11 +-
 drivers/net/wireless/realtek/rtw88/tx.h       |   2 +-
 12 files changed, 514 insertions(+), 9 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-05-04 10:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 10:50 yhchuang [this message]
2020-05-04 10:50 ` [PATCH v4 1/8] rtw88: 8723d: Add DIG parameter yhchuang
2020-05-06  8:35   ` Kalle Valo
2020-05-04 10:50 ` [PATCH v4 2/8] rtw88: 8723d: Add query_rx_desc yhchuang
2020-05-05 13:38   ` Sebastian Andrzej Siewior
2020-05-04 10:50 ` [PATCH v4 3/8] rtw88: 8723d: Add set_channel yhchuang
2020-05-04 10:50 ` [PATCH v4 4/8] rtw88: handle C2H_CCX_TX_RPT to know if packet TX'ed successfully yhchuang
2020-05-04 10:50 ` [PATCH v4 5/8] rtw88: 8723d: some chips don't support LDPC yhchuang
2020-05-04 10:50 ` [PATCH v4 6/8] rtw88: 8723d: Add chip_ops::false_alarm_statistics yhchuang
2020-05-04 10:50 ` [PATCH v4 7/8] rtw88: 8723d: Set IG register for CCK rate yhchuang
2020-05-04 10:50 ` [PATCH v4 8/8] rtw88: 8723d: add interface configurations table yhchuang
2020-05-05 13:30 ` [PATCH v4 0/8] rtw88: 8723d: add BB related routines Sebastian Andrzej Siewior

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=20200504105010.10780-1-yhchuang@realtek.com \
    --to=yhchuang@realtek.com \
    --cc=bigeasy@linutronix.de \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@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).