Skip to contentSkip to conversation

Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth adapter

PATCH In review 3 3 participants 3 messages Aug 31, 2025 Bluetooth drivers

lore
Share & tools
lore

3

author
#0 lore raw

PATCH 1/1 Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth adapter

From becb0b090d9783afddf7d43d739ee69b82fbb32a Mon Sep 17 00:00:00 2001
From: lespink <[email protected]>
Date: Sun, 31 Aug 2025 12:35:47 +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.

---
 drivers/bluetooth/btusb.c | 4 ++++

 1 file changed, 4 insertions(+)
drivers/bluetooth/btusb.c +0 -0
index 8085fabadde8..84ebeb317dda 100644
@@ -593,6 +593,10 @@ static const struct usb_device_id quirks_table[] = {

     { USB_DEVICE(0x0489, 0xe130), .driver_info = BTUSB_REALTEK | BTUSB_WIDEBAND_SPEECH },

+    /* Mercusys MA530 Adapter */
+    { USB_DEVICE(0x2c4e, 0x0115), .driver_info = BTUSB_REALTEK | +                             BTUSB_WIDEBAND_SPEECH }, +
     /* Realtek Bluetooth devices */
     { USB_VENDOR_AND_INTERFACE_INFO(0x0bda, 0xe0, 0x01, 0x01), .driver_info = BTUSB_REALTEK },
--
2.51.0

#1 lore raw

Dear lespink,

Thank you for your patch.

Am 31.08.25 um 12:50 schrieb 3:

Quoted 4 lines

From becb0b090d9783afddf7d43d739ee69b82fbb32a Mon Sep 17 00:00:00 2001
From: lespink <[email protected]>
Date: Sun, 31 Aug 2025 12:35:47 +0200
Subject: [PATCH] Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth adapter

Please use git send-email or b4 to send the patch, as currently it’s not formatted correctly.

Quoted 2 lines

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

… having the id 2c4e:0115.

(Maybe add that id to the summary/title too.)

Quoted 1 line

kernel with the original device list and thus was non-functional.

According to git log drivers/bluetooth it’s common to paste the information from /sys/kernel/debug/usb/devices to the commit message.

Quoted 22 lines
---
  drivers/bluetooth/btusb.c | 4 ++++
  1 file changed, 4 insertions(+)
drivers/bluetooth/btusb.c +4 -0
index 8085fabadde8..84ebeb317dda 100644
@@ -593,6 +593,10 @@ static const struct usb_device_id quirks_table[] = {
      { USB_DEVICE(0x0489, 0xe130), .driver_info = BTUSB_REALTEK |
                               BTUSB_WIDEBAND_SPEECH },
 
+    /* Mercusys MA530 Adapter */
+    { USB_DEVICE(0x2c4e, 0x0115), .driver_info = BTUSB_REALTEK |
+                             BTUSB_WIDEBAND_SPEECH },
+
      /* Realtek Bluetooth devices */
      { USB_VENDOR_AND_INTERFACE_INFO(0x0bda, 0xe0, 0x01, 0x01),
        .driver_info = BTUSB_REALTEK },
Signature · 1 line
2.51.0

The diff looks fine.

Kind regards,

Paul

#2 lore raw
In reply to 3

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 -----

Please resolve the issue and submit the patches again.

---
Regards,
Linux Bluetooth