From: Paul Menzel <pmenzel@molgen.mpg.de>
To: elespink@gmail.com
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Add support for Mercusys MA530 Bluetooth adapter
Date: Sun, 31 Aug 2025 12:57:25 +0200 [thread overview]
Message-ID: <a80e0cb6-0c2a-4b83-9461-5e2dfc7f6d29@molgen.mpg.de> (raw)
In-Reply-To: <12b048b5-aadd-4b06-a9a7-8480f27c65af@gmail.com>
Dear lespink,
Thank you for your patch.
Am 31.08.25 um 12:50 schrieb 3:
> From becb0b090d9783afddf7d43d739ee69b82fbb32a Mon Sep 17 00:00:00 2001
> From: lespink <lespinks9@gmail.com>
> 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.
> 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.)
> 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.
> Signed-off-by: lespink <lespinks9@gmail.com>
> ---
> drivers/bluetooth/btusb.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 8085fabadde8..84ebeb317dda 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -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
The diff looks fine.
Kind regards,
Paul
next prev parent reply other threads:[~2025-08-31 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 10:50 3
2025-08-31 10:57 ` Paul Menzel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-30 23:57 3
2025-08-30 23:35 3
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=a80e0cb6-0c2a-4b83-9461-5e2dfc7f6d29@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=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
all inboxes | Powered by JetHome®