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 1/2] wifi: rtw88: download the beacon the reserved page was built with
Date: Wed, 30 Sep 2026 09:27:02 +0200 [thread overview]
Message-ID: <20260930072702.1981397-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <fd3beaf9c2e34b03890707e4dc663ef7@realtek.com>
Hi Ping-Ke,
On 2026-09-30 Ping-Ke Shih wrote:
> If scan request while doing channel switching, we might deny the scan
> since peer (STA) might countdown itself and jump to target channel
> but no beacon listened causes disconnection.
>
> Therefore, rtw_download_beacon() fetches its own beacon without affecting
> countdown (channel switch isn't operating).
Agreed. v2 refuses a hardware scan with -EBUSY while csa_active is set
on any interface, and rtw_download_beacon() fetches its own beacon on
the scan path, which then never runs during a countdown.
Best regards,
Mehmet
next prev parent reply other threads:[~2026-09-30 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:43 [PATCH rtw-next 0/2] wifi: rtw88: channel switch in AP mode Mehmet Fide
2026-09-29 12:43 ` [PATCH rtw-next 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-09-29 19:11 ` Luka Gejak
2026-09-29 21:05 ` Mehmet Fide
2026-09-30 3:33 ` Ping-Ke Shih
2026-09-30 7:27 ` Mehmet Fide [this message]
2026-09-29 12:44 ` [PATCH rtw-next 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-09-30 3:45 ` Ping-Ke Shih
2026-09-30 7:27 ` 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=20260930072702.1981397-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®