From: Andre Eikmeyer <dev@deq.rocks>
To: marcel@holtmann.org, luiz.dentz@gmail.com
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
sven@kernel.org, j@jannau.net, neal@gompa.dev,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
66ton99@gmail.com, josemiguelo.ochoa@gmail.com,
aditya.garg@linux.dev, Andre Eikmeyer <dev@deq.rocks>
Subject: [PATCH 0/4] Bluetooth: Broadcom controllers of the Apple T2 Macs
Date: Wed, 4 Nov 2026 16:15:57 +0100 [thread overview]
Message-ID: <20261104151601.70493-1-dev@deq.rocks> (raw)
Hello everyone,
This series is for the Broadcom Bluetooth controllers of the Apple T2
Macs, the BCM4364 over UART (hci_bcm) and the BCM4377 over PCIe
(hci_bcm4377).
1 raise ACL priority on Apple Broadcom controllers
2 clear vendor bits in LE advertising report types
3 Revert "Bluetooth: hci_event: strip Broadcom vendor bits from
legacy adv report type"
4 set the strict duplicate filter quirk on Apple Broadcom controllers
Patch 2 and 3 belong together. Commit 88397423671f ("Bluetooth:
hci_event: strip Broadcom vendor bits from legacy adv report type") in
bluetooth-next masks the event type of legacy LE Advertising Reports for
every controller with manufacturer 15. The controllers known to set these
bits are the ones of the T2 Macs. Aditya Garg asked about this on the
list:
https://lore.kernel.org/linux-bluetooth/F4853998-F2A8-4AFE-99EA-544657EAB0E8@linux.dev/
Masking the type to its low nibble goes back to a t2linux patch by Jose
Miguel Ochoa. Patch 2 clears the bits in the two drivers of these
controllers before the event reaches the core, and patch 3 reverts the
check in hci_event.c. Patch 2 comes first, so every commit in between
keeps the reports.
Patch 1 builds on a vendor command the Android Broadcom vendor library
uses, 0xfc57, to keep A2DP from dropping out while WLAN runs on 2.4 GHz.
Patch 4 sets the strict duplicate filter quirk in both drivers, so a
discovery reports changed advertisement data before its next cycle.
The KaiT2en community, about 280 members, runs these patches with its
kernels. Users reported them working on the MacBookPro15,1, 15,2, 15,3,
15,4, 16,1, 16,4, MacBookAir9,1 and iMac20,1, and nobody reported a
regression.
Andre Eikmeyer (4):
Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers
Bluetooth: btbcm: clear vendor bits in LE advertising report types
Revert "Bluetooth: hci_event: strip Broadcom vendor bits from legacy
adv report type"
Bluetooth: set the strict duplicate filter quirk on Apple Broadcom
controllers
drivers/bluetooth/Kconfig | 1 +
drivers/bluetooth/btbcm.c | 102 ++++++++++++++++++++++++++++++++
drivers/bluetooth/btbcm.h | 12 ++++
drivers/bluetooth/hci_bcm.c | 28 ++++++++-
drivers/bluetooth/hci_bcm4377.c | 9 +++
net/bluetooth/hci_event.c | 11 ----
6 files changed, 149 insertions(+), 14 deletions(-)
base-commit: 3f425f95ba3923d605f6a8b382e8fcdc59d479db
next reply other threads:[~2026-11-04 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:15 Andre Eikmeyer [this message]
2026-11-04 15:15 ` [PATCH 1/4] Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers Andre Eikmeyer
2026-11-04 15:15 ` [PATCH 2/4] Bluetooth: btbcm: clear vendor bits in LE advertising report types Andre Eikmeyer
2026-11-04 15:24 ` Luiz Augusto von Dentz
2026-11-04 15:34 ` Aditya Garg
2026-11-04 15:46 ` André Eikmeyer
2026-11-04 16:29 ` Luiz Augusto von Dentz
2026-11-04 16:47 ` André Eikmeyer
2026-11-04 15:16 ` [PATCH 3/4] Revert "Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type" Andre Eikmeyer
2026-11-04 15:16 ` [PATCH 4/4] Bluetooth: set the strict duplicate filter quirk on Apple Broadcom controllers Andre Eikmeyer
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=20261104151601.70493-1-dev@deq.rocks \
--to=dev@deq.rocks \
--cc=66ton99@gmail.com \
--cc=aditya.garg@linux.dev \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=josemiguelo.ochoa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neal@gompa.dev \
--cc=sven@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