Re: [PATCH wireless-next] wifi: brcmfmac: enable 2.4 GHz VHT on BCM4366 before AP bring-up

From: Arend van Spriel

Date: Tue Nov 17 2026 - 07:14:45 EST


On Wed, 4 Nov 2026 17:04:26 +0000, Jeff Campbell wrote:
> On BCM4366 firmware 10.28.2 (r769115) the 2.4 GHz radio defaults to
> vht_features 6: proprietary rates and 1024-QAM on, 2.4 GHz VHT off.
> brcmfmac never sets this iovar. As an AP the d11 PSM watchdog then fires
> repeatedly once a client passes traffic, the client disassociates and
> never completes DHCP. This renders the radio unusable as an AP.

[...]

> Set bit 0, keeping the other bits, on the primary 2.4 GHz BSS of the
> 4366 family while the radio is still down. 5 GHz is left alone: it
> keeps 6 and is stable. This stabilizes 2.4GHz AP and clients now
> associate, DHCP and pass traffic at normal levels.

[...]

> ---
> .../broadcom/brcm80211/brcmfmac/cfg80211.c | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)

> + if (chip != BRCM_CC_4366_CHIP_ID && chip != BRCM_CC_43664_CHIP_ID &&
> + chip != BRCM_CC_43666_CHIP_ID)
> + return;

Firmware 10.28.2 (r769115) is the version of both brcmfmac4366b-pcie.bin
and brcmfmac4366c-pcie.bin in linux-firmware, so the firmware is covered.
The radios are not: you tested the 43666 only (4366c image), while the
change also applies to the 4366 and the 43664. Please mention in the
commit message that the 4366 was not tested.

I ran this on a 43664 with the 4366c image. vht_features is 6 by default
there as well and the patch sets it to 7 when the AP starts. A phone
associates, gets DHCP, and the AP uses VHT rates (173 Mbit/s) on 2.4 GHz.
What I could not reproduce is the failure without the patch: the AP
started a minute after boot, on channel 6 at 20 MHz, ran 60 seconds of
iperf3 in each direction with the stock driver and showed no PSM watchdog
in the firmware console and no firmware halt. Which client and traffic
pattern trigger the watchdog for you? Please add that to the commit
message.

Also, bit 0 is the 2.4 GHz VHT enable. The firmware builds its own
beacon from its settings and brcmfmac only parses a few IEs of the beacon
that hostapd provides, so with this change the AP advertises VHT on
2.4 GHz even if hostapd is configured without VHT. Please say so in the
commit message. If that is not acceptable, start_ap() already parses the
beacon IEs, so bit 0 could be set only when hostapd provided a VHT
Capabilities IE. That leaves a non-VHT AP at the values you found
unstable, which would then need a different workaround.

[...]

Nit: "2.4GHz" should be "2.4 GHz" in the commit message.

Regards,
Arend