From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@kernel.org>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH v2] Bluetooth: btbcm: Add entry for BCM4356A3 UART bluetooth
Date: Fri, 25 Sep 2026 01:52:50 -0500 [thread overview]
Message-ID: <20260925-bcm4356a3-bt-v2-1-42098aca235b@gmail.com> (raw)
From: Aaron Kling <webgeek1234@gmail.com>
This patch adds the device ID for the bluetooth chip used in the
Nvidia specific Broadcom BCM4356 PCI-E WiFi / UART BT chip.
Startup log:
Bluetooth: hci0: BCM: chip id 122
Bluetooth: hci0: BCM: features 0x0f
Bluetooth: hci0: BCM4356A3
Bluetooth: hci0: BCM4356A3 (001.004.009) build 0000
Bluetooth: hci0: BCM4356A3 'brcm/BCM4356A3.nvidia,p2894-2551-b00.hcd' Patch
Bluetooth: hci0: BCM: features 0x0f
Bluetooth: hci0: BCM4356A3 37.4MHz Class 1.5 Nvidia mDarcy-0108
Bluetooth: hci0: BCM4356A3 (001.004.009) build 0109
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
Changes in v2:
- Add startup log to commit message
- Link to v1: https://lore.kernel.org/r/20260717-bcm4356a3-bt-v1-1-ffa2d5233360@gmail.com
---
drivers/bluetooth/btbcm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
index 63c4c788d9c48..065536d4ec762 100644
--- a/drivers/bluetooth/btbcm.c
+++ b/drivers/bluetooth/btbcm.c
@@ -508,6 +508,7 @@ static const struct bcm_subver_table bcm_uart_subver_table[] = {
{ 0x6606, "BCM4345C5" }, /* 003.006.006 */
{ 0x230f, "BCM4356A2" }, /* 001.003.015 */
{ 0x2310, "BCM4343A2" }, /* 001.003.016 */
+ { 0x2409, "BCM4356A3" }, /* 001.004.009 */
{ 0x220e, "BCM20702A1" }, /* 001.002.014 */
{ 0x420d, "BCM4349B1" }, /* 002.002.013 */
{ 0x420e, "BCM4349B1" }, /* 002.002.014 */
---
base-commit: 4c253ac4b29b8c6cc6fdef8f92d4facde62e63b9
change-id: 20260717-bcm4356a3-bt-cd78cc0f42e8
Best regards,
--
Aaron Kling <webgeek1234@gmail.com>
reply other threads:[~2026-09-25 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260925-bcm4356a3-bt-v2-1-42098aca235b@gmail.com \
--to=devnull+webgeek1234.gmail.com@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=webgeek1234@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®