Linux bluetooth development
 help / color / mirror / Atom feed
From: Kenzi Voyer <kenzivoyer@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com
Subject: [PATCH] Bluetooth: btusb: Add USB ID 13d3:3631 for MediaTek MT7925
Date: Thu, 24 Sep 2026 13:53:28 +0200	[thread overview]
Message-ID: <20260924115328.15987-1-kenzivoyer@gmail.com> (raw)

The Mercusys (TP-Link) MA37BE Wi-Fi/Bluetooth adapter uses a MediaTek
MT7925 chip whose Bluetooth part enumerates as USB ID 13d3:3631.
This ID is not present in the btusb device table, so the interfaces
bind without MediaTek driver data and HCI initialization fails with:

    Bluetooth: hci0: Opcode 0x0c03 failed: -16

leaving no usable Bluetooth controller. Adding the ID to the MT7925
section of the table makes the driver run the MediaTek setup path
(firmware load) and the adapter works normally afterwards.

Signed-off-by: Kenzi Voyer <kenzivoyer@gmail.com>
---
 drivers/bluetooth/btusb.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index dc7191bf4..68396d553 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -831,6 +831,8 @@ static const struct usb_device_id quirks_table[] = {
 						     BTUSB_WIDEBAND_SPEECH },
 	{ USB_DEVICE(0x13d3, 0x3630), .driver_info = BTUSB_MEDIATEK |
 						     BTUSB_WIDEBAND_SPEECH },
+	{ USB_DEVICE(0x13d3, 0x3631), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH },
 	{ USB_DEVICE(0x2c7c, 0x7009), .driver_info = BTUSB_MEDIATEK |
 						     BTUSB_WIDEBAND_SPEECH },
 
-- 
2.55.0


             reply	other threads:[~2026-09-24 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 11:53 Kenzi Voyer [this message]
2026-09-24 15:01 ` Bluetooth: btusb: Add USB ID 13d3:3631 for MediaTek MT7925 bluez.test.bot
2026-09-24 16:01 ` [PATCH] " Kenzi Voyer

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=20260924115328.15987-1-kenzivoyer@gmail.com \
    --to=kenzivoyer@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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