From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ho Jie Feng <hjf3108@gmail.com>, linux-wireless@vger.kernel.org
Cc: Ping-Ke Shih <pkshih@realtek.com>
Subject: Re: [PATCH 2/6] wifi: rtw88: 88xxa: receive VHT SU beamformed transmissions
Date: Thu, 29 Oct 2026 23:06:26 +0200 [thread overview]
Message-ID: <8b058551-e608-4f8b-b3a5-2ee9f17bfa29@gmail.com> (raw)
In-Reply-To: <20261029141357.152345-1-hjf3108@gmail.com>
On 29/10/2026 16:13, Ho Jie Feng wrote:
> On 29/10/2026 14:33, Bitterblue Smith wrote:
>> On 29/10/2026 07:52, Ho Jie Feng wrote:
>>> Implement beamformee support for 88xxa since they have
>>> support for it.
>>>
>>> Signed-off-by: Ho Jie Feng <hjf3108@gmail.com>
>>> ---
>>> drivers/net/wireless/realtek/rtw88/bf.h | 2 +
>>> drivers/net/wireless/realtek/rtw88/main.c | 12 ++--
>>> drivers/net/wireless/realtek/rtw88/reg.h | 1 +
>>> drivers/net/wireless/realtek/rtw88/rtw8812a.c | 3 +-
>>> drivers/net/wireless/realtek/rtw88/rtw8814a.c | 36 ++++++++++-
>>> drivers/net/wireless/realtek/rtw88/rtw8821a.c | 3 +-
>>> drivers/net/wireless/realtek/rtw88/rtw88xxa.c | 62 +++++++++++++++++++
>>> drivers/net/wireless/realtek/rtw88/rtw88xxa.h | 2 +
>>> 8 files changed, 112 insertions(+), 9 deletions(-)
>>>
>>
>> Is it really this simple? The vendor driver has a lot more
>> beamforming code than this.
>
> Yes, this is the beamformee code, not the beamformer,
> which has way more code than this. The RTL8812AU is acting as
> the target for the AP to beamform to for this one.
>
Oh, I see. I didn't look very closely at the vendor code.
> I have the beamformer code, which the RTL8812AU
> beamforms, but I dropped it since it reduces throughput.
>
> I can put the patch out if you wish to see it, but
> won't be enabling for 88xxa.
>
> Reference:
> https://github.com/aircrack-ng/rtl8812au/blob/v5.6.4.2/hal/phydm/txbf/haltxbfjaguar.c#L229
>
By the way, there is a newer version:
https://github.com/morrownr/8812au-20210820
I don't know if there are any differences in the beamforming code.
> Vendor driver and rtw88 can be sometimes confusing for
> the bfee vs bfer distinction.
>
>>> ...
>>> if (rtwdev->hal.rf_path_num > 1)
>>> vht_cap->cap |= IEEE80211_VHT_CAP_TXSTBC;
>>> - vht_cap->cap |= IEEE80211_VHT_CAP_MU_BEAMFORMEE_CAPABLE |
>>> - IEEE80211_VHT_CAP_SU_BEAMFORMEE_CAPABLE;
>>> - vht_cap->cap |= (rtwdev->hal.bfee_sts_cap <<
>>> - IEEE80211_VHT_CAP_BEAMFORMEE_STS_SHIFT);
>>> + if (rtw_bf_support && chip->bfer_su_max_num) {
>>> + vht_cap->cap |= IEEE80211_VHT_CAP_SU_BEAMFORMEE_CAPABLE;
>>> + vht_cap->cap |= rtwdev->hal.bfee_sts_cap <<
>>> + IEEE80211_VHT_CAP_BEAMFORMEE_STS_SHIFT;
>>> + }
>>> + if (rtw_bf_support && chip->bfer_mu_max_num)
>>> + vht_cap->cap |= IEEE80211_VHT_CAP_MU_BEAMFORMEE_CAPABLE;
>>>
>>> if (rtw_chip_has_rx_ldpc(rtwdev))
>>> vht_cap->cap |= IEEE80211_VHT_CAP_RXLDPC;
>>
>> This could be a separate patch, since it doesn't look related to 88xxa.
>
> I can put this in v2.
>
>>> ...
next prev parent reply other threads:[~2026-10-29 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 5:52 [PATCH 0/6] wifi: rtw88: extend 88xxA support Ho Jie Feng
2026-10-29 5:52 ` [PATCH 1/6] wifi: rtw88: 8812a, 8814a: enable STBC for HT transmissions Ho Jie Feng
2026-10-29 5:52 ` [PATCH 2/6] wifi: rtw88: 88xxa: receive VHT SU beamformed transmissions Ho Jie Feng
2026-10-29 12:33 ` Bitterblue Smith
2026-10-29 14:13 ` Ho Jie Feng
2026-10-29 21:06 ` Bitterblue Smith [this message]
2026-10-29 5:52 ` [PATCH 3/6] wifi: rtw88: prepare frequency-offset correction for more chips Ho Jie Feng
2026-10-29 5:52 ` [PATCH 4/6] wifi: rtw88: 88xxa: correct carrier-frequency offset Ho Jie Feng
2026-10-29 5:52 ` [PATCH 5/6] wifi: rtw88: 88xxa: adapt channel sensing to receiver gain Ho Jie Feng
2026-10-29 5:52 ` [PATCH 6/6] wifi: rtw88: 8812a, 8821a: respect peer A-MPDU size limits Ho 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=8b058551-e608-4f8b-b3a5-2ee9f17bfa29@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=hjf3108@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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