mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v3 2/2] wifi: rtw88: support channel switch in AP mode
Date: Tue,  6 Oct 2026 09:46:30 +0200	[thread overview]
Message-ID: <20261006074630.372808-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <20261005173326.2306-1-luka.gejak@linux.dev>

Hi Luka,

On 2026-10-05 Luka Gejak wrote:
> so an association during the countdown moves the count a second time in
> the same interval. Can this download skip the page while a switch is
> announced, the way set_key does?

Yes. v4 skips the download and the H2C on association while a switch is
announced; the next countdown download carries the pages of the new
station. Of the remaining callers, the WoWLAN ones run after the
countdown work is cancelled and the beacon change is the countdown
itself.

> so the AP leaves the channel during the countdown anyway. Can the check
> move above the feature test?

Yes, v4 takes the mutex first and refuses the scan before the offload
test and the scanning flag, so firmware without scan offload gets -EBUSY
as well instead of a software scan.

Both verified on an RTL8821CU, whose firmware has no scan offload: a
scan during a countdown returned 32 BSSs with v3 and -EBUSY with v4,
and an association that completes inside a count-2 countdown hits the
mac80211 warning about the counter reaching 0 with v3, not with v4.

Best regards,
Mehmet

  reply	other threads:[~2026-10-06  7:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 14:35 [PATCH rtw-next v3 0/2] wifi: rtw88: " Mehmet Fide
2026-10-05 14:35 ` [PATCH rtw-next v3 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-05 17:36   ` Luka Gejak
2026-10-06  7:46     ` Mehmet Fide
2026-10-05 14:35 ` [PATCH rtw-next v3 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-05 17:33   ` [PATCH " Luka Gejak
2026-10-06  7:46     ` Mehmet Fide [this message]
2026-10-06  1:26   ` [PATCH rtw-next " Ping-Ke Shih
2026-10-06  7:46     ` Mehmet Fide
2026-10-06  7:54       ` Ping-Ke Shih
2026-10-06  8:16         ` Mehmet Fide
  -- strict thread matches above, loose matches on Subject: below --
2026-10-05 14:33 [PATCH rtw-next v3 0/2] wifi: rtw88: " Mehmet Fide
2026-10-05 14:33 ` [PATCH rtw-next v3 2/2] wifi: rtw88: support " 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=20261006074630.372808-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®