From: Mehmet Fide <mehmet.fide@gmail.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: Ping-Ke Shih <pkshih@realtek.com>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: Re: [PATCH rtw-next v11 3/3] wifi: rtw88: time the countdown downloads from the TBTT
Date: Mon, 16 Nov 2026 22:49:33 +0100 [thread overview]
Message-ID: <20261116214933.1569681-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <781999FE-B0CB-4D6E-8A1B-06A38082202F@linux.dev>
Hi Luka,
> Could the next step wait for a TBTT that can send the first download,
> including when the first work has missed its scheduled one?
Yes. In v12 each step reads the TSF after its download and queues the
next one 10 ms after the first TBTT at least 10 ms away, so every count,
the first too, has a TBTT. A step that would run less than 5 ms after
a TBTT or less than 10 ms before one waits until 10 ms after that TBTT.
With the first work held back by 90 to 100 ms and a count of 2, v11
switched without any CSA beacon in 10 of 12 tries. With v12 and the
first work held back by 95 ms, every count went out in 48 of 50
switches with counts 2 and 5 on an RTL8821CU, an RTL8822BU and an
RTL8822CE; in the other two one count is missing in the capture.
Thanks,
Mehmet
prev parent reply other threads:[~2026-11-16 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 7:19 [PATCH rtw-next v11 0/3] wifi: rtw88: channel switch in AP mode Mehmet Fide
2026-11-16 7:19 ` [PATCH rtw-next v11 1/3] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-11-16 7:19 ` [PATCH rtw-next v11 2/3] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-11-16 14:24 ` Luka Gejak
2026-11-16 21:49 ` Mehmet Fide
2026-11-16 7:19 ` [PATCH rtw-next v11 3/3] wifi: rtw88: time the countdown downloads from the TBTT Mehmet Fide
2026-11-16 14:26 ` Luka Gejak
2026-11-16 21:49 ` Mehmet Fide [this message]
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=20261116214933.1569681-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
all inboxes | Powered by JetHome®