From: Ping-Ke Shih <pkshih@realtek.com>
To: Mehmet Fide <mehmet.fide@gmail.com>, Luka Gejak <luka.gejak@linux.dev>
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 1/2] wifi: rtw88: download the beacon the reserved page was built with
Date: Wed, 30 Sep 2026 03:33:42 +0000 [thread overview]
Message-ID: <fd3beaf9c2e34b03890707e4dc663ef7@realtek.com> (raw)
In-Reply-To: <20260929210529.1848479-1-mehmet.fide@gmail.com>
Mehmet Fide <mehmet.fide@gmail.com> wrote:
> Hi Luka,
>
> On 2026-09-29 Luka Gejak wrote:
> > This breaks hardware scan offload while an AP is active.
> >
> > rtw_download_beacon() no longer fetches a beacon of its own. It reads
> > rsvd_pkt->skb, and rtw_fw_download_rsvd_page() clears that skb right
> > before it returns:
> [...]
> > Could the scan path fetch its own beacon, or could the retained skb be
> > released only after the standalone download, with care taken to not
> > advance the CSA countdown twice?
>
> Thanks, you are right: I checked the callers of
> rtw_fw_download_rsvd_page() and missed rtw_hw_scan_offload().
>
> v2 takes your first option. rtw_build_rsvd_page() hands the page-0
> beacon skb out to rtw_fw_download_rsvd_page(), which passes it to
> rtw_download_beacon() and frees it afterwards, and rtw_download_beacon()
> fetches (and frees) its own beacon when it is called without one, which
> is what the scan path does. So the countdown still advances once per
> page update and the scan keeps its beacon.
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).
Ping-Ke
next prev parent reply other threads:[~2026-09-30 3:34 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 [this message]
2026-09-30 7:27 ` Mehmet Fide
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=fd3beaf9c2e34b03890707e4dc663ef7@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--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®