* [PATCH] Bluetooth: btbcm: Add entries for BCM4364B3 UART Bluetooth
@ 2026-11-16 21:38 Jason Perlow
2026-11-17 2:25 ` bluez.test.bot
0 siblings, 1 reply; 2+ messages in thread
From: Jason Perlow @ 2026-11-16 21:38 UTC (permalink / raw)
To: Marcel Holtmann, Luiz Augusto von Dentz, linux-bluetooth; +Cc: linux-kernel
The BCM4364B3 combo chip on Apple T2 Macs, e.g. the MacBookPro16,1, has a
UART Bluetooth controller that reports LMP subversion 0x3032 (001.016.050)
on some units and 0x305b (001.016.091) on others. Neither has an entry in
bcm_uart_subver_table, so the controller is logged without a name:
Bluetooth: hci0: BCM4364B3 Trinidad Olympic GEN (MFG)
Bluetooth: hci0: BCM (001.016.091) build 0115
and the firmware lookup only tries the generic "brcm/BCM.hcd".
Add both subversions so the controller is named and its firmware is looked
up as "brcm/BCM4364B3.hcd" first. Tested on two MacBookPro16,1 with a
v7.4-rc3 based kernel carrying an equivalent change, one reporting 0x3032
and one reporting 0x305b. They now log:
Bluetooth: hci0: BCM4364B3 (001.016.050) build 0082
Bluetooth: hci0: BCM4364B3 (001.016.091) build 0115
Signed-off-by: Jason Perlow <jperlow@gmail.com>
---
drivers/bluetooth/btbcm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
index 065536d4ec..92ba7aeac3 100644
--- a/drivers/bluetooth/btbcm.c
+++ b/drivers/bluetooth/btbcm.c
@@ -519,6 +519,8 @@ static const struct bcm_subver_table
bcm_uart_subver_table[] = {
{ 0x2119, "BCM4373A0" }, /* 001.001.025 */
{ 0x2128, "BCM4384A0" }, /* 001.001.040 */
{ 0x4119, "BCM4384B0" }, /* 002.001.025 */
+ { 0x3032, "BCM4364B3" }, /* 001.016.050 */
+ { 0x305b, "BCM4364B3" }, /* 001.016.091 */
{ }
};
-- 2.56.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* RE: Bluetooth: btbcm: Add entries for BCM4364B3 UART Bluetooth
2026-11-16 21:38 [PATCH] Bluetooth: btbcm: Add entries for BCM4364B3 UART Bluetooth Jason Perlow
@ 2026-11-17 2:25 ` bluez.test.bot
0 siblings, 0 replies; 2+ messages in thread
From: bluez.test.bot @ 2026-11-17 2:25 UTC (permalink / raw)
To: linux-bluetooth, jperlow
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.
----- Output -----
error: corrupt patch at line 12
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-17 2:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-16 21:38 [PATCH] Bluetooth: btbcm: Add entries for BCM4364B3 UART Bluetooth Jason Perlow
2026-11-17 2:25 ` bluez.test.bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox