From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next] wifi: rtw88: WARN only once in rtw_phy_get_tx_power_limit()
Date: Thu, 26 Mar 2026 01:58:55 +0000 [thread overview]
Message-ID: <6e49be57199f4db788b02c70626f20d5@realtek.com> (raw)
In-Reply-To: <491d5140-f16d-44a6-bf01-8f35e43e2fdf@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>
> On 09/02/2026 10:01, Ping-Ke Shih wrote:
> > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >> This function WARNs when the wifi band, channel number, channel width,
> >> rate, or RF path are invalid. Two or three people have reported that it
> >> floods the kernel log with warnings because they try to switch to
> >> invalid channel numbers, like 130.
> >>
> >> One warning is probably enough, so turn WARN into WARN_ONCE.
> >>
> >> Closes: https://github.com/lwfinger/rtw88/issues/428
> >
> > As the issue says "invalid arguments, band=1, bw=2, path=1, rate=83, ch=130",
> > I think it operates on bandwidth 80MHz and primary channel 130.
> > But I don't see 20MHz primary channel, for example [1].
> >
> > Can we stop using this channel at set_channel() ahead to avoid this error?
> >
> > [1] https://en.wikipedia.org/wiki/List_of_WLAN_channels
> >
>
> Is there a standard which says what channels are allowed?
>
> Six weeks ago I asked people to test another patch which adds a check
> in rtw_set_channel() like you said, but no one replied. I guess I will
> send it as v2.
We are working on a patch to stop this kind of channels. I'd send a RFC
in coming week.
>
> By the way, there is another patch related to this problem:
>
> https://lore.kernel.org/linux-wireless/20260306-rtw88_channel130-v1-1-ff25a5
> bc930a@igalia.com/
>
I see.
Ping-Ke
prev parent reply other threads:[~2026-03-26 1:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 18:00 [PATCH rtw-next] wifi: rtw88: WARN only once in rtw_phy_get_tx_power_limit() Bitterblue Smith
2026-02-09 8:01 ` Ping-Ke Shih
2026-03-25 23:03 ` Bitterblue Smith
2026-03-26 1:58 ` 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=6e49be57199f4db788b02c70626f20d5@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--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