This series patches will introduce a new designed DMA busy watchdog
and fix two small issues when calling ieee80211_restart_hw().
Changes in v2:
* Disable DMA watchdog for USB NICs because they don't have relevant
register.
* Extend 'watchdog' module parameter to support different watchdogs.
* Clear the 'intf->enable_beacon' flag instead of hacking the
conditions of the 'else if' block. The logic still the same but
should be easy to understand what happened there.
* Clear the beacon before restarting the beacon queue. It should be
like this.
* Unconditional stop the beacon queue in rt2x00lib_disable_radio().
It is no need to check the reset status because there is a flag in
rt2x00 queue struct to record the queue start/stop status. It won't
be stopped twice. The procedure still the same as patch v1.
P.S. It seems that this cover letter won't be included in the patch
series in https://lore.kernel.org/. It's an issue with the Outlook
email or I missed something?
Shiji Yang (3):
wifi: rt2x00: introduce DMA busy check watchdog for rt2800
wifi: rt2x00: disable RTS threshold for rt2800 by default
wifi: rt2x00: restart beacon queue when hardware reset
drivers/net/wireless/ralink/rt2x00/rt2800.h | 4 +
.../net/wireless/ralink/rt2x00/rt2800lib.c | 81 ++++++++++++++++---
drivers/net/wireless/ralink/rt2x00/rt2x00.h | 3 +
.../net/wireless/ralink/rt2x00/rt2x00dev.c | 3 +
.../net/wireless/ralink/rt2x00/rt2x00mac.c | 11 +++
5 files changed, 89 insertions(+), 13 deletions(-)
--
2.39.2
On 11/4/2023 1:57 AM, Shiji Yang wrote:
> P.S. It seems that this cover letter won't be included in the patch
> series in https://lore.kernel.org/. It's an issue with the Outlook
> email or I missed something?
Outlook e-mail is apparently rewriting your e-mail headers:
Subject: [PATCH v2 0/3] wifi: rt2x00: improve watchdog support
Message-ID:
<TYAP286MB0315D63EBE1DE458D6B9D42ABCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
X-Microsoft-Original-Message-ID:
<[email protected]>
Subject: [PATCH v2 1/3] wifi: rt2x00: introduce DMA busy check watchdog
for rt2800
Message-ID:
<TYAP286MB0315D7462CE08A119A99DE34BCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <[email protected]>
References: <[email protected]>
Subject: [PATCH v2 2/3] wifi: rt2x00: disable RTS threshold for rt2800
by default
Message-ID:
<TYAP286MB03155DDB953155B7A2DE849ABCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <[email protected]>
References: <[email protected]>
Your actual patches are being threaded since they all reference the same
Message ID, but the cover letter no longer has that Message ID.
You might want to look at using b4
(<https://b4.docs.kernel.org/en/latest/contributor/overview.html>)
instead of git send-email.
From the linked page:
The main benefit of b4 send is that you no longer have to really care if
your mail server performs some kind of content mangling that causes
patches to become corrupted, or if it doesn’t provide a way to send mail
via SMTP.