From: Luka Gejak <luka.gejak@linux.dev>
To: Ho Jie Feng <hjf3108@gmail.com>, Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Bitterblue Smith <rtl8821cerfe2@gmail.com>
Subject: Re: [PATCH rtw-next v3 1/5] wifi: rtw88: 8812a, 8814a: enable STBC for HT transmissions
Date: Fri, 13 Nov 2026 09:08:35 +0100 [thread overview]
Message-ID: <5B401960-03A0-4433-9607-ED5149E31844@linux.dev> (raw)
In-Reply-To: <20261112173246.3201729-2-hjf3108@gmail.com>
Hi Jie Feng,
Thanks for adding the 8822c note. One question below.
On November 12, 2026 6:32:40 PM GMT+01:00, Ho Jie Feng <hjf3108@gmail.com>
wrote:
> 8812a and 8814a support STBC, enable it.
The hardware seems to support it. The vendor driver reports TX STBC for
both chips unless they are 1T1R or 1T2R. But it keeps HT STBC TX off by
default, os_dep/linux/os_intfs.c in the 8812au driver has
int rtw_stbc_cap = 0x13;
and rtw_ht_use_default_setting() only enables HT STBC TX for BIT5, which
is not set there. VHT STBC TX (BIT1) is on. In rtw88 only 8822c has it,
from 81a68a1424ba ("rtw88: 8822c: add tx stbc support under HT mode"),
while 8822b stays off although it is 2T2R as well.
As far as I can see, a VHT peer already gets STBC through the VHT TX
STBC capability we advertise for rf_path_num > 1, so this patch only
changes HT peers, for example any AP on 2.4 GHz, where we don't
advertise VHT. Did you test it there or with an HT only AP? The numbers
in the cover letter would only show this patch if the test was done
that way.
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-11-13 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 17:32 [PATCH rtw-next v3 0/5] wifi: rtw88: extend 88xxA support Ho Jie Feng
2026-11-12 17:32 ` [PATCH rtw-next v3 1/5] wifi: rtw88: 8812a, 8814a: enable STBC for HT transmissions Ho Jie Feng
2026-11-13 8:08 ` Luka Gejak [this message]
2026-11-12 17:32 ` [PATCH rtw-next v3 2/5] wifi: rtw88: 88xxa: receive VHT SU beamformed transmissions Ho Jie Feng
2026-11-13 7:46 ` Luka Gejak
2026-11-13 8:01 ` Jie Feng
2026-11-13 8:07 ` Luka Gejak
2026-11-13 8:12 ` Jie Feng
2026-11-13 8:09 ` Luka Gejak
2026-11-13 8:20 ` Jie Feng
2026-11-12 17:32 ` [PATCH rtw-next v3 3/5] wifi: rtw88: prepare frequency-offset correction for more chips Ho Jie Feng
2026-11-12 17:32 ` [PATCH rtw-next v3 4/5] wifi: rtw88: 88xxa: correct carrier-frequency offset Ho Jie Feng
2026-11-13 7:52 ` Luka Gejak
2026-11-12 17:32 ` [PATCH rtw-next v3 5/5] wifi: rtw88: 8812a, 8821a: respect peer A-MPDU size limits Ho Jie Feng
2026-11-13 8:10 ` Luka Gejak
2026-11-13 8:16 ` Jie Feng
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=5B401960-03A0-4433-9607-ED5149E31844@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®