From: Luka Gejak <luka.gejak@linux.dev>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Ho Jie Feng <hjf3108@gmail.com>,
Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH rtw-next v2 6/7] wifi: rtw88: 88xxa: adapt channel sensing to receiver gain
Date: Tue, 10 Nov 2026 20:57:32 +0100 [thread overview]
Message-ID: <C4DC98F9-B999-478E-B7AA-7DAA15D6C996@linux.dev> (raw)
In-Reply-To: <45407e4f-9009-4f0b-a9a8-58b7052d25a1@gmail.com>
Hi Bitterblue and Jie Feng,
On November 10, 2026 3:36:35 PM GMT+01:00, Bitterblue Smith
<rtl8821cerfe2@gmail.com> wrote:
>On 06/11/2026 22:27, Luka Gejak wrote:
>> November 6, 2026 at 8:46 PM, "Bitterblue Smith"
><rtl8821cerfe2@gmail.com> wrote:
>>
>> JP. Bitterblue, is the adapter on a USB 3 port, and do you see the LPS
>> failures on 5 GHz as well?
>
> It's in a USB 2 port. I am seeing the LPS failures on 5 GHz too.
> Channel 100, 80 MHz wide.
Thanks, that rules out the USB 3 idea.
My next guess is the lower bound. Under ETSI the L2H starts 37 dB below
normal mode and is then raised to at least dm_info->l2h_th_lb, which is
only 2 above a floor measured once at power on, on 2.4 GHz at 20 MHz
with the LNA off. At 80 MHz that may be close to the noise, and with H2L
7 lower EDCCA may stay busy. In LPS the firmware can switch the RF off,
and in the watchdog the ADC mask toggle only runs after rtw_leave_lps(),
so a busy EDCCA from sleep would still block the null frame.
Bitterblue, could you try debug_mask=0x8000 to see whether L2H sits at
that bound (printed as "EDCCA L2H floor") when it fails, and maybe
EDCCA_DC_BACKOFF_88XXA raised from 2 to 8?
Jie Feng, until this is figured out, keeping 88xxa on the normal thresholds
like the vendor driver does by default, or leaving this patch
out of v3, seems to be the safest option.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-11-10 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261031070950.425176-1-hjf3108@gmail.com>
2026-10-31 7:09 ` [PATCH rtw-next v2 1/7] wifi: rtw88: 8812a, 8814a: enable STBC for HT transmissions Ho Jie Feng
2026-11-06 17:21 ` Luka Gejak
2026-10-31 7:09 ` [PATCH rtw-next v2 2/7] wifi: rtw88: 88xxa: receive VHT SU beamformed transmissions Ho Jie Feng
2026-11-06 17:23 ` Luka Gejak
2026-10-31 7:09 ` [PATCH rtw-next v2 3/7] wifi: rtw88: correctly expose beamformee capabilities Ho Jie Feng
2026-11-06 17:25 ` Luka Gejak
2026-10-31 7:09 ` [PATCH rtw-next v2 4/7] wifi: rtw88: prepare frequency-offset correction for more chips Ho Jie Feng
2026-10-31 7:09 ` [PATCH rtw-next v2 5/7] wifi: rtw88: 88xxa: correct carrier-frequency offset Ho Jie Feng
2026-11-06 17:27 ` Luka Gejak
2026-10-31 7:09 ` [PATCH rtw-next v2 6/7] wifi: rtw88: 88xxa: adapt channel sensing to receiver gain Ho Jie Feng
2026-11-06 17:34 ` Luka Gejak
2026-11-06 19:46 ` Bitterblue Smith
2026-11-06 20:27 ` Luka Gejak
2026-11-10 14:36 ` Bitterblue Smith
2026-11-10 19:57 ` Luka Gejak [this message]
2026-10-31 7:09 ` [PATCH rtw-next v2 7/7] wifi: rtw88: 8812a, 8821a: respect peer A-MPDU size limits Ho Jie Feng
2026-11-06 17:35 ` Luka Gejak
2026-11-08 18:09 ` Jie Feng
2026-11-09 7:25 ` Luka Gejak
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=C4DC98F9-B999-478E-B7AA-7DAA15D6C996@linux.dev \
--to=luka.gejak@linux.dev \
--cc=hjf3108@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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®