From: 3 <elespink@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth adapter
Date: Sun, 31 Aug 2025 01:35:15 +0200 [thread overview]
Message-ID: <02cf444e-d05f-4af9-89ce-96276e29be14@gmail.com> (raw)
From 5d970b05c726749908540bf7d5ee34d634bf16c2 Mon Sep 17 00:00:00 2001
From: elespink <elespink@gmail.com>
Date: Sun, 31 Aug 2025 01:06:10 +0200
Subject: [PATCH] Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth
adapter
Add support for a Realtek-based Mercusys MA530 Bluetooth 5.3 USB dongle
which works with USB ID 2c4e:0115. This device was not recognized by the
kernel with the original device list and thus was non-functional.
The device is misreported in lsusb as "Mercucys INC Meucusys MA530 Adapter".
---
drivers/bluetooth/btusb.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 8085fabadde8..94984791e454 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -597,6 +597,10 @@ static const struct usb_device_id quirks_table[] = {
{ USB_VENDOR_AND_INTERFACE_INFO(0x0bda, 0xe0, 0x01, 0x01),
.driver_info = BTUSB_REALTEK },
+ /* Mercusys MA530 Adapter */
+ { USB_DEVICE(0x2c4e, 0x0115), .driver_info = BTUSB_REALTEK |
+ BTUSB_WIDEBAND_SPEECH },
+
/* MediaTek Bluetooth devices */
{ USB_VENDOR_AND_INTERFACE_INFO(0x0e8d, 0xe0, 0x01, 0x01),
.driver_info = BTUSB_MEDIATEK |
--
2.51.0
next reply other threads:[~2025-08-30 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 23:35 3 [this message]
2025-08-30 23:37 ` Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth adapter bluez.test.bot
-- strict thread matches above, loose matches on Subject: below --
2025-08-30 23:57 [PATCH] " 3
2025-08-31 10:50 3
2025-08-31 10:57 ` Paul Menzel
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=02cf444e-d05f-4af9-89ce-96276e29be14@gmail.com \
--to=elespink@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).