From: Ping-Ke Shih <pkshih@realtek.com>
To: Mehmet Fide <mehmet.fide@gmail.com>, Luka Gejak <luka.gejak@linux.dev>
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 v8 2/3] wifi: rtw88: support channel switch in AP mode
Date: Tue, 27 Oct 2026 02:02:32 +0000 [thread overview]
Message-ID: <64d3a24e0afd460db4a182bfa2214aa0@realtek.com> (raw)
In-Reply-To: <20261025184749.1045907-1-mehmet.fide@gmail.com>
Mehmet Fide <mehmet.fide@gmail.com> wrote:
> Hi Luka,
>
> Thanks for the review.
>
> > Would clearing csa_active in ieee80211_ibss_disconnect(), same way
> > ieee80211_stop_ap() does, be the right fix?
>
> Yes. I reproduced it on an RTL8822CU. mac80211 refuses the next switch
> itself as well, so I will send the fix to mac80211 separately.
>
> > Maybe rtw_ops_resume() could restart the countdown when the AP still has
> > csa_active set?
>
> Agreed, v9 does that. It is not run here, I have no 8822CE.
During the WoW suspend, I think AP stays on original channel and sends
beacon without countdown. How does associated STA do? Will it switch to
target channel and disconnect result from no beacon?
next prev parent reply other threads:[~2026-10-27 2:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 11:45 [PATCH rtw-next v8 0/3] wifi: rtw88: " Mehmet Fide
2026-10-21 11:45 ` [PATCH rtw-next v8 1/3] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-21 11:45 ` [PATCH rtw-next v8 2/3] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-25 13:24 ` Luka Gejak
2026-10-25 18:47 ` Mehmet Fide
2026-10-27 2:02 ` Ping-Ke Shih [this message]
2026-10-27 9:13 ` Mehmet Fide
2026-10-21 11:45 ` [PATCH rtw-next v8 3/3] wifi: rtw88: time the countdown downloads from the TBTT Mehmet Fide
2026-10-22 1:57 ` Ping-Ke Shih
2026-10-25 12:50 ` Luka Gejak
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=64d3a24e0afd460db4a182bfa2214aa0@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®