From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Bitterblue Smith" <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH rtw-next] wifi: rtw88: 8723b: don't set channel_invalid in query_phy_status()
Date: Mon, 12 Oct 2026 05:26:15 +0000 [thread overview]
Message-ID: <3ba621799df94d20bb5aac0f08fcfb28@realtek.com> (raw)
In-Reply-To: <20261009155838.169058-1-luka.gejak@linux.dev>
Luka Gejak <luka.gejak@linux.dev> wrote:
> rtw8723b_query_phy_status() sets pkt_stat->channel_invalid, which makes
> rtw_update_rx_freq_for_invalid() call rtw_update_rx_freq_from_ie() and
> overwrite rx_status->freq with rtwdev->hal.current_channel.
> rtw_update_channel() keeps the center channel in that field, not the
> primary one, so on a 40 MHz connection mac80211 is handed a frequency it
> rejects in ieee80211_rx_beacon_freq_valid() and reports beacon loss for
> beacons the driver did receive. Only beacons go through that check, so
> data traffic is unaffected.
>
> Remove it now, so that the non-SDIO members of the 8723B family do not
> report beacon loss once they are supported. SDIO is unaffected, because
> rtw_sdio_rx_skb() copies the status into the skb before the update runs.
>
> Reported-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
prev parent reply other threads:[~2026-10-12 5:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 15:58 [PATCH rtw-next] wifi: rtw88: 8723b: don't set channel_invalid in query_phy_status() Luka Gejak
2026-10-12 5:26 ` Ping-Ke Shih [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=3ba621799df94d20bb5aac0f08fcfb28@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.