From: Ping-Ke Shih <pkshih@realtek.com>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mehmet.fide@screeningeagle.com" <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 03:59:42 +0000 [thread overview]
Message-ID: <04b18579ec644839af3d5baa1790618f@realtek.com> (raw)
In-Reply-To: <ab6a510713267fee446e511c87d5b162827353fb.1791362281.git.mehmet.fide@screeningeagle.com>
Mehmet Fide <mehmet.fide@gmail.com> wrote:
> void rtw_fw_update_beacon_work(struct wiphy *wiphy, struct wiphy_work *work)
> {
> struct rtw_dev *rtwdev = container_of(work, struct rtw_dev,
> @@ -1811,7 +1840,8 @@ void rtw_fw_update_beacon_work(struct wiphy *wiphy, struct wiphy_work *work)
>
> mutex_lock(&rtwdev->mutex);
>
> - 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.
> goto out;
>
> rtw_fw_download_rsvd_page(rtwdev);
[...]
> @@ -438,6 +443,8 @@ static void rtw_ops_bss_info_changed(struct ieee80211_hw *hw,
> rtw_set_dtim_period(rtwdev, conf->dtim_period);
> rtw_fw_download_rsvd_page(rtwdev);
> rtw_send_rsvd_page_h2c(rtwdev);
> + if (conf->csa_active)
> + rtw_fw_csa_start(rtwdev, vif);
Is this a necessary case? Can't rtw_ops_channel_switch_beacon() handle it?
> }
>
> if (changed & BSS_CHANGED_BEACON_ENABLED) {
[...]
next prev parent reply other threads:[~2026-10-12 3:59 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 [this message]
2026-10-12 6:57 ` Mehmet Fide
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=04b18579ec644839af3d5baa1790618f@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.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®