From: Mehmet Fide <mehmet.fide@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Mehmet Fide <mehmet.fide@screeningeagle.com>
Subject: Re: [PATCH rtw-next v5 3/3] wifi: rtw88: support channel switch in AP mode
Date: Mon, 12 Oct 2026 08:57:43 +0200 [thread overview]
Message-ID: <20261012065743.17665-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <04b18579ec644839af3d5baa1790618f@realtek.com>
Hi Ping-Ke,
On 2026-10-12 Ping-Ke Shih wrote:
> > - if (!test_bit(RTW_FLAG_RUNNING, rtwdev->flags))
> > + if (!test_bit(RTW_FLAG_RUNNING, rtwdev->flags) ||
> > + rtw_fw_csa_active(rtwdev))
>
> As my comment in patch 2/3, I think we should cancel the work at core_stop.
Yes. In v6 rtw_core_stop() cancels csa_beacon_work next to
update_beacon_work and clears csa_vif, which also covers the firmware
recovery, so the wiphy_lock() in rtw_fw_recovery_work() goes away.
> > + if (conf->csa_active)
> > + rtw_fw_csa_start(rtwdev, vif);
>
> Is this a necessary case? Can't rtw_ops_channel_switch_beacon() handle it?
It is the restart case. After ieee80211_restart_hw(),
ieee80211_reconfig() replays BSS_CHANGED_BEACON with csa_active still
set, and drv_channel_switch_beacon() is only called from
__ieee80211_channel_switch(), so without this the countdown would not
resume after a firmware recovery. v6 says so in a comment, and the
same path stops the countdown when the beacon comes back without
csa_active, which is how mac80211 ends a switch.
Mehmet
prev parent reply other threads:[~2026-10-12 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 6:21 [PATCH rtw-next v5 0/3] wifi: rtw88: " Mehmet Fide
2026-10-08 6:21 ` [PATCH rtw-next v5 1/3] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-08 6:21 ` [PATCH rtw-next v5 2/3] wifi: rtw88: update the beacon from a wiphy work Mehmet Fide
2026-10-12 3:16 ` Ping-Ke Shih
2026-10-12 3:21 ` Ping-Ke Shih
2026-10-12 6:57 ` Mehmet Fide
2026-10-08 6:21 ` [PATCH rtw-next v5 3/3] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-12 3:59 ` Ping-Ke Shih
2026-10-12 6:57 ` Mehmet Fide [this message]
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=20261012065743.17665-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=mehmet.fide@screeningeagle.com \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@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
all inboxes | Powered by JetHome®