Linux wireless drivers development
 help / color / mirror / Atom feed
From: Zhao Li <enderaoelyther@gmail.com>
To: Jeff Chen <jeff.chen_1@nxp.com>
Cc: Jeff Chen <jeff.chen_1@oss.nxp.com>,
	Francesco Dolcini <francesco@dolcini.it>,
	Johannes Berg <johannes@sipsolutions.net>,
	Arend van Spriel <arend.vanspriel@broadcom.com>,
	Jiangshan Yi <yijiangshan@kylinos.cn>,
	Linmao Li <lilinmao@kylinos.cn>,
	Kees Cook <kees+treewide@kernel.org>,
	Rosen Penev <rosenp@gmail.com>,
	Benjamin Berg <benjamin.berg@intel.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH wireless v2 0/4] wifi: nxpwifi: fix AP channel-switch lifetime and failures
Date: Thu, 19 Nov 2026 02:35:02 +0800	[thread overview]
Message-ID: <20261118183506.45749-1-enderaoelyther@gmail.com> (raw)

Fix four problems in the nxpwifi AP channel-switch path: the delayed
work survives an AP stop, TX is stopped before the switch is prepared,
the work reads beacon data after the nl80211 request is freed, and a
failed switch leaves TX enabled over a stopped AP.

Changes in v2:
- Include v1 patch 1, which is not in wireless or nxpwifi-current yet
  and which patch 3 builds on. It now also clears uap_stop_tx when the
  AP stops.
- Patch 2: keep nxpwifi_queue_delayed_wiphy_work() instead of switching
  to wiphy_delayed_work_queue(). v1 patch 2 is the one with review
  comments; v1 patch 3 had none.
- Patch 3: minor style cleanup in nxpwifi_dup_csa_update().
- Patch 4: free the beacon update on every exit of the work, and clear
  uap_stop_tx when the switch fails.
- Shorten the changelogs and move the AI assistance note below "---".

v1: https://lore.kernel.org/r/20261028141819.7556-1-enderaoelyther@gmail.com

Zhao Li (4):
  wifi: nxpwifi: cancel channel switch work on teardown
  wifi: nxpwifi: stop AP TX after preparing channel switch
  wifi: nxpwifi: own beacon data used by channel switch work
  wifi: nxpwifi: stop AP when delayed channel switch fails

 drivers/net/wireless/nxp/nxpwifi/11h.c      | 23 +++++--
 drivers/net/wireless/nxp/nxpwifi/cfg80211.c | 72 +++++++++++++++++++--
 drivers/net/wireless/nxp/nxpwifi/main.h     |  2 +-
 3 files changed, 83 insertions(+), 14 deletions(-)


base-commit: 763b13f622e2758726e8e3ecaef819db8fa0430a
-- 
2.56.1


             reply	other threads:[~2026-11-18 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 18:35 Zhao Li [this message]
2026-11-18 18:35 ` [PATCH wireless v2 1/4] wifi: nxpwifi: cancel channel switch work on teardown Zhao Li
2026-11-18 18:35 ` [PATCH wireless v2 2/4] wifi: nxpwifi: stop AP TX after preparing channel switch Zhao Li
2026-11-18 18:35 ` [PATCH wireless v2 3/4] wifi: nxpwifi: own beacon data used by channel switch work Zhao Li
2026-11-18 18:35 ` [PATCH wireless v2 4/4] wifi: nxpwifi: stop AP when delayed channel switch fails Zhao Li

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=20261118183506.45749-1-enderaoelyther@gmail.com \
    --to=enderaoelyther@gmail.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=benjamin.berg@intel.com \
    --cc=francesco@dolcini.it \
    --cc=jeff.chen_1@nxp.com \
    --cc=jeff.chen_1@oss.nxp.com \
    --cc=johannes@sipsolutions.net \
    --cc=kees+treewide@kernel.org \
    --cc=lilinmao@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rosenp@gmail.com \
    --cc=yijiangshan@kylinos.cn \
    /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