All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <tony0620emma@gmail.com>, <kvalo@codeaurora.org>
Cc: <linux-wireless@vger.kernel.org>, <vincent_fann@realtek.com>,
	<phhuang@realtek.com>, <steventing@realtek.com>,
	<briannorris@chromium.org>
Subject: [PATCH 0/3] rtw88: fix some TX/RX bugs
Date: Thu, 15 Apr 2021 16:47:00 +0800	[thread overview]
Message-ID: <20210415084703.27255-1-pkshih@realtek.com> (raw)

This patchset fix bugs happened during TX/RX performance test.
First is 88221c doesn't set proper RX_FLAG_DECRYPTED. Second is to fix
count of available TX queue, and then it can wake ieee80211 queue
correctly; otherwise, it can't tx anymore. Third patch is to refine
NAPI deinit flow to safely stop PCI; without this fix, system spin while
it is going to down. 

Guo-Feng Fan (1):
  rtw88: 8821c: Don't set RX_FLAG_DECRYPTED if packet has no encryption

Po-Hao Huang (1):
  rtw88: refine napi deinit flow

Yu-Yen Ting (1):
  rtw88: Fix potential unrecoverable tx queue stop

 drivers/net/wireless/realtek/rtw88/pci.c      | 29 ++++++++++++++-----
 drivers/net/wireless/realtek/rtw88/pci.h      |  1 +
 drivers/net/wireless/realtek/rtw88/rtw8821c.c |  3 +-
 3 files changed, 25 insertions(+), 8 deletions(-)

-- 
2.21.0


             reply	other threads:[~2021-04-15  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  8:47 Ping-Ke Shih [this message]
2021-04-15  8:47 ` [PATCH 1/3] rtw88: 8821c: Don't set RX_FLAG_DECRYPTED if packet has no encryption Ping-Ke Shih
2021-04-21  9:38   ` Kalle Valo
2021-04-15  8:47 ` [PATCH 2/3] rtw88: Fix potential unrecoverable tx queue stop Ping-Ke Shih
2021-04-15  8:47 ` [PATCH 3/3] rtw88: refine napi deinit flow 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=20210415084703.27255-1-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=briannorris@chromium.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@realtek.com \
    --cc=steventing@realtek.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.