From: "Rosen Penev" <rosenp@gmail.com>
To: "Luca Casati" <luk00casati@gmail.com>, <linux-wireless@vger.kernel.org>
Cc: <johannes@sipsolutions.net>, <arend.vanspriel@broadcom.com>,
<b43-dev@lists.infradead.org>
Subject: Re: [PATCH wireless-next 0/5] b43: N-PHY: fix calibrations on rev7+ (BCM43228)
Date: Wed, 28 Oct 2026 11:12:08 -0700 [thread overview]
Message-ID: <DMGOAJTSLTRX.3NHOMSGMQXH1X@gmail.com> (raw)
In-Reply-To: <20261026181543.77763-1-luk00casati@gmail.com>
On Mon Oct 26, 2026 at 11:15 AM PDT, Luca Casati wrote:
> On a BCM43228 (14e4:4359, N-PHY rev 16, radio 2057 rev 9) b43
> associates but transmits poorly: high retry counts and low rates.
> Comparing mmiotraces of b43 and the proprietary wl driver
> (6.30.223.271) on the same card, together with brcmsmac, turned up
> several bugs in the N-PHY calibration code:
>
> 1. The TX tone sample table was loaded as all zeros, so every
> tone-based calibration ran without a signal.
> 2. TX IQ/LO calibration: inverted busy poll, reversed final copy,
> and missing rev7+ cleanup that left TX dead after a cal.
> 3. RSSI calibration: wrong VCM written on rev7+, wrong distance
> formula, wrong rounding of negative offsets.
> 4. 2057 RC calibration: the first run was polled before it started,
> leaving SCAP at 0 and the TX low-pass filter detuned.
> 5. A missing field in the rev7 TX_PU RF override.
>
> After these, the register writes for the cals match wl's on this card.
>
> Patches 4 and 5 and the cleanup parts of patch 2 only affect rev7+.
> Patch 1, the poll and final-copy fixes in patch 2, and the
> distance/rounding fixes in patch 3 also change code that runs on older
> N-PHYs (rev3+); I could only test rev 16, so testing on other N-PHY
> cards would be welcome.
>
> Tested on the BCM43228 only (2.4 GHz, 11g/HT20), on v7.0; the series
> also applies to wireless-next. Throughput to the internet went from
> about 5.7/4.1 to 11.1/5.2 Mbit/s down/up, with fewer TX retries. That
> number is limited by the line and noisy, so take it as a rough
> indication; wl reaches 21-32 Mbit/s down on the same setup, so there
> is more to do (PAPD and TX power control on rev7+).
>
> Comments and changelogs refer to wl where the fix was checked against
> its register writes. If citing the proprietary driver is not
> acceptable here, I am happy to reword them.
>
> The bugs were found and the fixes drafted with the help of an AI
> coding assistant (Claude Opus 5.5), working from the mmiotrace diffs
> between b43 and wl and from brcmsmac. I reviewed and tested every
> patch on the hardware above.
I'll just comment here instead of the individual patches.
For all of these, Fixes: tags are appropriate. They help linux-stable
pick them up. Meaning that wireless, instead of wireless-next is the
more appropriate place for them.
The whole Assisted-by thing is deprecated. It is no longer desired to
advertize such a thing in individual commits. It's fine for a cover
letter.
>
> Luca Casati (5):
> b43: N-PHY: fix the TX tone sample table
> b43: N-PHY: fix TX IQ/LO calibration
> b43: N-PHY: fix rev3+ RSSI calibration
> b43: N-PHY: wait for the first 2057 RC calibration run
> b43: N-PHY: add the missing override to the rev7 TX_PU command
>
> drivers/net/wireless/broadcom/b43/phy_n.c | 120 +++++++++++++++++++---
> 1 file changed, 106 insertions(+), 14 deletions(-)
>
>
> base-commit: 028ef9c96e96197026887c0f092424679298aae8
WARNING: multiple messages have this Message-ID (diff)
From: "Rosen Penev" <rosenp@gmail.com>
To: "Luca Casati" <luk00casati@gmail.com>, <linux-wireless@vger.kernel.org>
Cc: <johannes@sipsolutions.net>, <arend.vanspriel@broadcom.com>,
<b43-dev@lists.infradead.org>
Subject: Re: [PATCH wireless-next 0/5] b43: N-PHY: fix calibrations on rev7+ (BCM43228)
Date: Wed, 28 Oct 2026 11:12:08 -0700 [thread overview]
Message-ID: <DMGOAJTSLTRX.3NHOMSGMQXH1X@gmail.com> (raw)
In-Reply-To: <20261026181543.77763-1-luk00casati@gmail.com>
On Mon Oct 26, 2026 at 11:15 AM PDT, Luca Casati wrote:
> On a BCM43228 (14e4:4359, N-PHY rev 16, radio 2057 rev 9) b43
> associates but transmits poorly: high retry counts and low rates.
> Comparing mmiotraces of b43 and the proprietary wl driver
> (6.30.223.271) on the same card, together with brcmsmac, turned up
> several bugs in the N-PHY calibration code:
>
> 1. The TX tone sample table was loaded as all zeros, so every
> tone-based calibration ran without a signal.
> 2. TX IQ/LO calibration: inverted busy poll, reversed final copy,
> and missing rev7+ cleanup that left TX dead after a cal.
> 3. RSSI calibration: wrong VCM written on rev7+, wrong distance
> formula, wrong rounding of negative offsets.
> 4. 2057 RC calibration: the first run was polled before it started,
> leaving SCAP at 0 and the TX low-pass filter detuned.
> 5. A missing field in the rev7 TX_PU RF override.
>
> After these, the register writes for the cals match wl's on this card.
>
> Patches 4 and 5 and the cleanup parts of patch 2 only affect rev7+.
> Patch 1, the poll and final-copy fixes in patch 2, and the
> distance/rounding fixes in patch 3 also change code that runs on older
> N-PHYs (rev3+); I could only test rev 16, so testing on other N-PHY
> cards would be welcome.
>
> Tested on the BCM43228 only (2.4 GHz, 11g/HT20), on v7.0; the series
> also applies to wireless-next. Throughput to the internet went from
> about 5.7/4.1 to 11.1/5.2 Mbit/s down/up, with fewer TX retries. That
> number is limited by the line and noisy, so take it as a rough
> indication; wl reaches 21-32 Mbit/s down on the same setup, so there
> is more to do (PAPD and TX power control on rev7+).
>
> Comments and changelogs refer to wl where the fix was checked against
> its register writes. If citing the proprietary driver is not
> acceptable here, I am happy to reword them.
>
> The bugs were found and the fixes drafted with the help of an AI
> coding assistant (Claude Opus 5.5), working from the mmiotrace diffs
> between b43 and wl and from brcmsmac. I reviewed and tested every
> patch on the hardware above.
I'll just comment here instead of the individual patches.
For all of these, Fixes: tags are appropriate. They help linux-stable
pick them up. Meaning that wireless, instead of wireless-next is the
more appropriate place for them.
The whole Assisted-by thing is deprecated. It is no longer desired to
advertize such a thing in individual commits. It's fine for a cover
letter.
>
> Luca Casati (5):
> b43: N-PHY: fix the TX tone sample table
> b43: N-PHY: fix TX IQ/LO calibration
> b43: N-PHY: fix rev3+ RSSI calibration
> b43: N-PHY: wait for the first 2057 RC calibration run
> b43: N-PHY: add the missing override to the rev7 TX_PU command
>
> drivers/net/wireless/broadcom/b43/phy_n.c | 120 +++++++++++++++++++---
> 1 file changed, 106 insertions(+), 14 deletions(-)
>
>
> base-commit: 028ef9c96e96197026887c0f092424679298aae8
_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
next prev parent reply other threads:[~2026-10-28 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 18:15 [PATCH wireless-next 0/5] b43: N-PHY: fix calibrations on rev7+ (BCM43228) Luca Casati
2026-10-26 18:15 ` Luca Casati
2026-10-26 18:15 ` [PATCH wireless-next 1/5] b43: N-PHY: fix the TX tone sample table Luca Casati
2026-10-26 18:15 ` Luca Casati
2026-10-26 18:15 ` [PATCH wireless-next 2/5] b43: N-PHY: fix TX IQ/LO calibration Luca Casati
2026-10-26 18:15 ` Luca Casati
2026-10-26 18:15 ` [PATCH wireless-next 3/5] b43: N-PHY: fix rev3+ RSSI calibration Luca Casati
2026-10-26 18:15 ` Luca Casati
2026-10-26 18:15 ` [PATCH wireless-next 4/5] b43: N-PHY: wait for the first 2057 RC calibration run Luca Casati
2026-10-26 18:15 ` Luca Casati
2026-10-26 18:15 ` [PATCH wireless-next 5/5] b43: N-PHY: add the missing override to the rev7 TX_PU command Luca Casati
2026-10-26 18:15 ` Luca Casati
2026-10-28 18:12 ` Rosen Penev [this message]
2026-10-28 18:12 ` [PATCH wireless-next 0/5] b43: N-PHY: fix calibrations on rev7+ (BCM43228) Rosen Penev
2026-10-29 7:13 ` Johannes Berg
2026-10-29 7:13 ` Johannes Berg
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=DMGOAJTSLTRX.3NHOMSGMQXH1X@gmail.com \
--to=rosenp@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luk00casati@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.