From: Ping-Ke Shih <pkshih@realtek.com>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: 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 2/2] wifi: rtw88: support channel switch in AP mode
Date: Wed, 30 Sep 2026 03:45:11 +0000 [thread overview]
Message-ID: <bef3467b008b4bc790ae2baedc1f4625@realtek.com> (raw)
In-Reply-To: <20260929124400.3856049-3-mehmet.fide@gmail.com>
Mehmet Fide <mehmet.fide@gmail.com> wrote:
> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
> hostapd's CHAN_SWITCH is refused because the driver does not announce
> channel switch support, so an AP on rtw88 can only change its channel
> by being torn down and started again.
>
> Declare WIPHY_FLAG_HAS_CHANNEL_SWITCH and implement
> ieee80211_ops::channel_switch_beacon the way rtw89 does:
No need to mention rtw89, which you have mentioned in cover letter.
> the firmware
> repeats the beacon held in the reserved page, so while a switch is
> announced the beacon is downloaded again every beacon interval to renew
> the countdown, and ieee80211_csa_finish() is called once it completes.
>
> Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
[...]
> diff --git a/drivers/net/wireless/realtek/rtw88/mac80211.c
> b/drivers/net/wireless/realtek/rtw88/mac80211.c
> index 2a9b09fa76e7..915e810470aa 100644
> --- a/drivers/net/wireless/realtek/rtw88/mac80211.c
> +++ b/drivers/net/wireless/realtek/rtw88/mac80211.c
> @@ -164,6 +164,8 @@ static int rtw_ops_add_interface(struct ieee80211_hw *hw,
> memset(&rtwvif->bfee, 0, sizeof(struct rtw_bfee));
> rtw_txq_init(rtwdev, vif->txq);
> INIT_LIST_HEAD(&rtwvif->rsvd_page_list);
> + rtwvif->rtwdev = rtwdev;
Move to be first statement of this function followed by a blank line.
> + INIT_DELAYED_WORK(&rtwvif->csa_beacon_work, rtw_fw_csa_beacon_work);
>
> mutex_lock(&rtwdev->mutex);
>
next prev parent reply other threads:[~2026-09-30 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:43 [PATCH rtw-next 0/2] wifi: rtw88: " Mehmet Fide
2026-09-29 12:43 ` [PATCH rtw-next 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-09-29 19:11 ` Luka Gejak
2026-09-29 21:05 ` Mehmet Fide
2026-09-30 3:33 ` Ping-Ke Shih
2026-09-30 7:27 ` Mehmet Fide
2026-09-29 12:44 ` [PATCH rtw-next 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-09-30 3:45 ` Ping-Ke Shih [this message]
2026-09-30 7:27 ` 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=bef3467b008b4bc790ae2baedc1f4625@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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®