mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Fri, 06 Nov 2026 20:27:28 +0000	[thread overview]
Message-ID: <1d7fe388a84ba7a078efbf1972869d63cb8234ea@linux.dev> (raw)
In-Reply-To: <3bd7d396-bb54-41bc-890a-bfeab90dca3a@gmail.com>

November 6, 2026 at 8:46 PM, "Bitterblue Smith" <rtl8821cerfe2@gmail.com> wrote:

> 
> On 06/11/2026 19:34, Luka Gejak wrote:
> 
>> 

[ ... ]

>>  
>>  Bitterblue, did you turn EDCCA off through the edcca_enable debugfs file?
>> 
> Yes, that's what I did.
> 

Thanks for the answer. So I think EDCCA itself is fine with this patch,
and it is the lower thresholds of the adaptivity mode that keep the
firmware from leaving LPS.

To me this looks a lot like b0435910e47d ("wifi: rtw88: 8822b: Relax
ETSI EDCCA threshold on 2.4 GHz"). There an RTL8812BU running as a 2.4
GHz AP wasn't seen in scans and failed to get TX reports under the
ETSI threshold, mostly because of energy from the adapter's own USB 3
link. The fix was to use the normal threshold on 2.4 GHz under ETSI,
capped for EN 300 328. Your network is on channel 13, so that would fit.

The 8812au vendor drivers don't use the adaptivity thresholds by default
either. Both v5.6.4.2 and 8812au-20210820 build with

        CONFIG_RTW_ADAPTIVITY_EN = disable

and as far as I can see phydm_adaptivity() then stays on the normal
(mode2) thresholds.

Jie Feng, maybe doing the same as 8822b would work for v3, the normal
thresholds on 2.4 GHz under ETSI and the adaptivity ones for 5 GHz and
JP. Bitterblue, is the adapter on a USB 3 port, and do you see the LPS
failures on 5 GHz as well?

Best regards,
Luka Gejak

  reply	other threads:[~2026-11-06 20:27 UTC|newest]

Thread overview: 15+ 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 [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

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=1d7fe388a84ba7a078efbf1972869d63cb8234ea@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®