Linux wireless drivers development
 help / color / mirror / Atom feed
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@screeningeagle.com
Subject: Re: [PATCH rtw-next v8 2/3] wifi: rtw88: support channel switch in AP mode
Date: Tue, 27 Oct 2026 10:13:12 +0100	[thread overview]
Message-ID: <20261027091312.1421798-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <64d3a24e0afd460db4a182bfa2214aa0@realtek.com>

Hi Ping-Ke,

> 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?

Yes. I tried it with mac80211_hwsim on wireless/main: the station
switches on its timer even when the AP goes on beaconing on the old
channel without the CSA element, and disconnects after the beacon
loss. From the code, only drivers with abort_channel_switch (iwlwifi,
mt7921, mt7925) abort the switch on such a beacon and stay.

The AP stays up during WoWLAN only with AP + station on the 8822C:
WoWLAN takes a station vif only, so with an AP alone rtw_ops_suspend()
returns 1 and cfg80211 stops the AP before suspending. I checked this
on an RTL8822CU during a countdown.

Refusing WoWLAN during a switch would not help the stations, cfg80211
would stop the AP as well, so I would keep v9. The resume path does
not run on USB, the device is unbound during suspend; an 8822CE is on
order, it takes two to three weeks, and I can test it when it arrives.

Mehmet

  reply	other threads:[~2026-10-27  9:13 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: channel switch in AP mode 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
2026-10-27  9:13         ` Mehmet Fide [this message]
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=20261027091312.1421798-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