From: Shiji Yang <yangshiji66@outlook.com>
To: linux-wireless@vger.kernel.org
Cc: Stanislaw Gruszka <stf_xl@wp.pl>, Kalle Valo <kvalo@kernel.org>,
linux-kernel@vger.kernel.org,
Shiji Yang <yangshiji66@outlook.com>
Subject: [PATCH v2 0/3] wifi: rt2x00: improve watchdog support
Date: Sat, 4 Nov 2023 16:57:57 +0800 [thread overview]
Message-ID: <TYAP286MB0315D63EBE1DE458D6B9D42ABCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM> (raw)
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
next reply other threads:[~2023-11-04 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 8:57 Shiji Yang [this message]
2023-11-06 16:33 ` Jeff Johnson
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=TYAP286MB0315D63EBE1DE458D6B9D42ABCA4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM \
--to=yangshiji66@outlook.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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
all inboxes | Powered by JetHome®