From: Mehmet Fide <mehmet.fide@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH rtw-next v6 2/2] wifi: rtw88: support channel switch in AP mode
Date: Mon, 19 Oct 2026 10:31:35 +0200 [thread overview]
Message-ID: <20261019083135.3251458-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <b9bdebf6dac043ce9b3e285e0d12209b@realtek.com>
Hi Ping-Ke,
On 2026-10-19, Ping-Ke Shih wrote:
> If you download beacon to firmware twice within a period of beacon_int,
> a countdown in the air will not present, no? Like this
[...]
> The 4 is missing.
Yes, when a download runs late past the next TBTT. The absolute due
time keeps the pace, one download per beacon interval on average, so
the AP switches when its stations expect it; v5 queued relative to
the previous download and drifted 10 ms per beacon on USB. The price
of a download that late is one stale beacon and one count never sent.
A station takes its switch time from the counts it sees; at worst one
whose first count is the stale one switches one interval late.
Forced on an RTL8821CU with a 90 ms delay on every second download: a
sniffer saw 9, 8, 8, 6, 4, 4, 2, 2 for count 10, the AP finished on
time, and a Windows station followed ten such switches (counts 10 and
50) without a re-association. Without the delay it happened once in
nine switches.
If you would rather not have it: timing the downloads from the TSF,
10 ms after each TBTT, leaves nearly a whole interval before a beacon
goes out without the download. I tried that briefly on the 8821CU;
with a 60 ms delay every count stays on the air. Which do you prefer?
Thanks,
Mehmet
next prev parent reply other threads:[~2026-10-19 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 7:30 [PATCH rtw-next v6 0/2] wifi: rtw88: " Mehmet Fide
2026-10-13 7:30 ` [PATCH rtw-next v6 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-13 7:30 ` [PATCH rtw-next v6 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-19 3:31 ` Ping-Ke Shih
2026-10-19 8:31 ` Mehmet Fide [this message]
2026-10-19 8:52 ` Ping-Ke Shih
2026-10-19 10:56 ` 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=20261019083135.3251458-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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®