From: "Vinícius Ramon Fontanela" <vfontanela@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: arend.vanspriel@broadcom.com, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
"Vinícius Ramon Fontanela" <vfontanela@gmail.com>
Subject: [PATCH v2] wifi: brcmfmac: allow ISO3166 fallback for BCM4350
Date: Tue, 15 Sep 2026 14:43:00 -0300 [thread overview]
Message-ID: <20260915174300.28363-1-vfontanela@gmail.com> (raw)
In-Reply-To: <20260914200357.1743468-1-arend.vanspriel@broadcom.com>
BCM4350 devices using brcmfmac on x86/PCIe may have no platform-provided
country code map. In that case brcmf_translate_country_code() falls back to
ISO3166 codes only for chips accepted by
brmcf_use_iso3166_ccode_fallback().
BCM4350 is currently missing from that list, despite the adjacent BCM4345
and BCM4356 being present. Add BCM4350 so these devices can use the ISO3166
country code with revision 0.
Signed-off-by: Vinícius Ramon Fontanela <vfontanela@gmail.com>
---
v2: resend using git send-email to avoid line wrapping/corruption in v1.
drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
index 9d8ce7bb0..2b819dbe6 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
@@ -8076,6 +8076,7 @@ static bool brmcf_use_iso3166_ccode_fallback(struct brcmf_pub *drvr)
switch (drvr->bus_if->chip) {
case BRCM_CC_43430_CHIP_ID:
case BRCM_CC_4345_CHIP_ID:
+ case BRCM_CC_4350_CHIP_ID:
case BRCM_CC_4356_CHIP_ID:
case BRCM_CC_43602_CHIP_ID:
return true;
--
2.55.0
next prev parent reply other threads:[~2026-09-15 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 18:49 [PATCH] wifi: brcmfmac: allow ISO3166 fallback for BCM4350 Vinícius Ramon Fontanela
2026-09-14 20:03 ` Arend van Spriel
2026-09-15 17:43 ` Vinícius Ramon Fontanela [this message]
2026-10-04 9:45 ` [PATCH v2] " Arend van Spriel
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=20260915174300.28363-1-vfontanela@gmail.com \
--to=vfontanela@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
/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