linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Hans Ulli Kroll <linux@ulli-kroll.de>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Pkshih <pkshih@realtek.com>, Tim K <tpkuester@gmail.com>,
	"Alex G ." <mr.nuke.me@gmail.com>,
	Nick Morrow <morrownr@gmail.com>,
	Viktor Petrenko <g0000ga@gmail.com>,
	Andreas Henriksson <andreas@fatal.se>,
	ValdikSS <iam@valdikss.org.ru>,
	kernel@pengutronix.de, stable@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH 0/2] RTW88 USB bug fixes
Date: Fri, 31 Mar 2023 14:10:52 +0200	[thread overview]
Message-ID: <20230331121054.112758-1-s.hauer@pengutronix.de> (raw)

This series fixes two bugs in the RTW88 USB driver I was reported from
several people and that I also encountered myself.

The first one resulted in "timed out to flush queue 3" messages from the
driver and sometimes a complete stall of the TX queues.

The second one is specific to the RTW8821CU chipset. Here 2GHz networks
were hardly seen and impossible to connect to. This goes down to
misinterpreting the rfe_option field in the efuse.

Sascha Hauer (2):
  wifi: rtw88: usb: fix priority queue to endpoint mapping
  wifi: rtw88: rtw8821c: Fix rfe_option field width

 drivers/net/wireless/realtek/rtw88/rtw8821c.c |  3 +-
 drivers/net/wireless/realtek/rtw88/usb.c      | 70 +++++++++++++------
 2 files changed, 48 insertions(+), 25 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-03-31 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 12:10 Sascha Hauer [this message]
2023-03-31 12:10 ` [PATCH 1/2] wifi: rtw88: usb: fix priority queue to endpoint mapping Sascha Hauer
2023-03-31 14:31   ` Jonathan Bither
2023-04-04  7:11     ` Sascha Hauer
2023-03-31 12:10 ` [PATCH 2/2] wifi: rtw88: rtw8821c: Fix rfe_option field width Sascha Hauer
2023-03-31 13:16   ` Greg KH
2023-03-31 20:34 ` [PATCH 0/2] RTW88 USB bug fixes Alex G.
2023-04-01  2:05   ` Larry Finger
2023-04-01  2:08   ` ValdikSS

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=20230331121054.112758-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=andreas@fatal.se \
    --cc=g0000ga@gmail.com \
    --cc=iam@valdikss.org.ru \
    --cc=kernel@pengutronix.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@ulli-kroll.de \
    --cc=morrownr@gmail.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=pkshih@realtek.com \
    --cc=stable@vger.kernel.org \
    --cc=tpkuester@gmail.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).