mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v6 2/2] wifi: rtw88: support channel switch in AP mode
Date: Mon, 19 Oct 2026 03:31:23 +0000	[thread overview]
Message-ID: <b9bdebf6dac043ce9b3e285e0d12209b@realtek.com> (raw)
In-Reply-To: <20261013073010.358756-3-mehmet.fide@gmail.com>

Mehmet Fide <mehmet.fide@gmail.com> wrote:

[...]

>     - the downloads are paced from the first one with an absolute due time:
>       queued after each download, the countdown drifted by about 10 ms per
>       beacon interval on the ordered mac80211 workqueue, and a station
>       switched ahead of the AP on a count of 50

If you download beacon to firmware twice within a period of beacon_int,
a countdown in the air will not present, no? Like this

t (TU)                       0            100             200           300
download beacon            5                   4      3               2
firmware TX beacon           x            x               x             x
air                          5            5               3             2

The 4 is missing.

> +/* paced from the first download: a late one does not delay the next */
> +static void rtw_fw_csa_queue(struct rtw_dev *rtwdev, struct ieee80211_vif *vif)
> +{
> +       u32 interval = ieee80211_tu_to_usec(vif->bss_conf.beacon_int);
> +       s64 delay;
> +
> +       rtwdev->csa_due = ktime_add_us(rtwdev->csa_due, interval);
> +       delay = ktime_us_delta(rtwdev->csa_due, ktime_get());
> +       ieee80211_queue_delayed_work(rtwdev->hw, &rtwdev->csa_beacon_work,
> +                                    usecs_to_jiffies(max(delay, 0)));
> +}

Otherwise, looks good to me. 


  reply	other threads:[~2026-10-19  3: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 [this message]
2026-10-19  8:31     ` Mehmet Fide
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=b9bdebf6dac043ce9b3e285e0d12209b@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®