All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessio Ferri <alessio.ferri@mythread.it>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Michael Buesch" <m@bues.ch>
Cc: vit9696 <vit9696@protonmail.com>,
	ville+git@takio.fi, egc112@msn.com,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [PATCH wireless-next v4 10/10] wifi: b43: add the 2.4 GHz BCM4352/BCM4360 to the supported bands
Date: Mon, 9 Nov 2026 02:26:22 +0100	[thread overview]
Message-ID: <20261109022622.000056e3@mythread.it> (raw)
In-Reply-To: <20261109-bcma-ac-rev1-v4-0-de1262c18b54@mythread.it>


Report the 2.4 GHz BCM4360 (0x43a1) and BCM4352 (0x43b2) as 2.4 GHz
only devices, as their 5 GHz variants are reported as 5 GHz only.

Signed-off-by: Alessio Ferri <alessio.ferri@mythread.it>
---
 drivers/net/wireless/broadcom/b43/main.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/net/wireless/broadcom/b43/main.c b/drivers/net/wireless/broadcom/b43/main.c
index 3825b6ad9..350b47b4b 100644
--- a/drivers/net/wireless/broadcom/b43/main.c
+++ b/drivers/net/wireless/broadcom/b43/main.c
@@ -5366,6 +5366,12 @@ static void b43_supported_bands(struct b43_wldev *dev, bool *have_2ghz_phy,
 		*have_2ghz_phy = false;
 		*have_5ghz_phy = true;
 		return;
+	case 0x43a1: /* BCM4360 */
+	case 0x43b2: /* BCM4352 */
+		/* 2.4 GHz only devices */
+		*have_2ghz_phy = true;
+		*have_5ghz_phy = false;
+		return;
 	}
 
 	/* As a fallback, try to guess using PHY type */
-- 
2.34.1


_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev

WARNING: multiple messages have this Message-ID (diff)
From: Alessio Ferri <alessio.ferri@mythread.it>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Michael Buesch" <m@bues.ch>
Cc: vit9696 <vit9696@protonmail.com>,
	ville+git@takio.fi, egc112@msn.com,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [PATCH wireless-next v4 10/10] wifi: b43: add the 2.4 GHz BCM4352/BCM4360 to the supported bands
Date: Mon, 9 Nov 2026 02:26:22 +0100	[thread overview]
Message-ID: <20261109022622.000056e3@mythread.it> (raw)
In-Reply-To: <20261109-bcma-ac-rev1-v4-0-de1262c18b54@mythread.it>


Report the 2.4 GHz BCM4360 (0x43a1) and BCM4352 (0x43b2) as 2.4 GHz
only devices, as their 5 GHz variants are reported as 5 GHz only.

Signed-off-by: Alessio Ferri <alessio.ferri@mythread.it>
---
 drivers/net/wireless/broadcom/b43/main.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/net/wireless/broadcom/b43/main.c b/drivers/net/wireless/broadcom/b43/main.c
index 3825b6ad9..350b47b4b 100644
--- a/drivers/net/wireless/broadcom/b43/main.c
+++ b/drivers/net/wireless/broadcom/b43/main.c
@@ -5366,6 +5366,12 @@ static void b43_supported_bands(struct b43_wldev *dev, bool *have_2ghz_phy,
 		*have_2ghz_phy = false;
 		*have_5ghz_phy = true;
 		return;
+	case 0x43a1: /* BCM4360 */
+	case 0x43b2: /* BCM4352 */
+		/* 2.4 GHz only devices */
+		*have_2ghz_phy = true;
+		*have_5ghz_phy = false;
+		return;
 	}
 
 	/* As a fallback, try to guess using PHY type */
-- 
2.34.1


  parent reply	other threads:[~2026-11-09  1:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  1:17 [PATCH wireless-next v4 00/10] bcma-ac-rev1: support 4352/4360 rev3 chips Alessio Ferri
2026-11-09  1:17 ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 01/10] bcma: core: clear only FORCEHT for BCMA_CLKMODE_DYNAMIC Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 02/10] bcma: pmu: init PLL and resources on BCM4352/BCM4360 Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 03/10] bcma: pcie2: request HT " Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 04/10] bcma: chipcommon: enable asynchronous GPIO interrupts Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 05/10] bcma: extract SPROM revision 11 Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 06/10] firmware: bcm47xx_sprom: read the SPROM revision 11 fields from NVRAM Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 07/10] firmware: bcm47xx_sprom: read ledbh4..ledbh15 " Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:17 ` [PATCH wireless-next v4 08/10] firmware: bcm47xx_sprom: read boardflags3 from NVRAM over the SPROM Alessio Ferri
2026-11-09  1:17   ` Alessio Ferri
2026-11-09  1:25 ` [PATCH wireless-next v4 09/10] bcma: add the single-band BCM4352/BCM4360 PCI IDs Alessio Ferri
2026-11-09  1:25   ` Alessio Ferri
2026-11-09  1:26 ` Alessio Ferri [this message]
2026-11-09  1:26   ` [PATCH wireless-next v4 10/10] wifi: b43: add the 2.4 GHz BCM4352/BCM4360 to the supported bands Alessio Ferri

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=20261109022622.000056e3@mythread.it \
    --to=alessio.ferri@mythread.it \
    --cc=b43-dev@lists.infradead.org \
    --cc=egc112@msn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m@bues.ch \
    --cc=ville+git@takio.fi \
    --cc=vit9696@protonmail.com \
    --cc=zajec5@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.