From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jack Murray <kernel@c0rporation.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] bluetooth: Add support for EP-B3536 USB Bluetooth adapter
Date: Sun, 16 Jan 2022 07:07:54 +0100 [thread overview]
Message-ID: <d2b50954-5303-a547-3be8-35e6c3208a1d@molgen.mpg.de> (raw)
In-Reply-To: <a96af59d-089f-1018-74fc-355e96fcf0c3@c0rporation.com>
Dear Jack,
Am 15.01.22 um 22:30 schrieb Jack Murray:
> From: Jack Murray <kernel@c0rporation.com>
>
> This patch adds support for the EP-B3536 USB bluetooth 5.1 adapter based
Who manufactures that device? Is it Teledyne? 0x2550 is 9552 (decimal),
and according to [1] that is Teledyne. Maybe, add that to the commit
message.
> on the 8761B chipset. The existing driver and firmware work fine for this
> device from what I can tell, so this patch just adds the vendor/product IDs
> for it to the supported device list.
>
> Signed-off-by: Jack Murray <kernel@c0rporation.com>
> ---
> drivers/bluetooth/btusb.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 60d2fce59a71..207c8289c5c2 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -436,6 +436,8 @@ static const struct usb_device_id blacklist_table[] = {
> /* Additional Realtek 8761BU Bluetooth devices */
> { USB_DEVICE(0x0b05, 0x190e), .driver_info = BTUSB_REALTEK |
> BTUSB_WIDEBAND_SPEECH },
> + { USB_DEVICE(0x2550, 0x8761), .driver_info = BTUSB_REALTEK |
> + BTUSB_WIDEBAND_SPEECH }, >
> /* Additional Realtek 8821AE Bluetooth devices */
> { USB_DEVICE(0x0b05, 0x17dc), .driver_info = BTUSB_REALTEK },
Kind regards,
Paul
[1]: https://www.usb.org/sites/default/files/vendor_ids082119_0.pdf
next prev parent reply other threads:[~2022-01-16 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 21:30 [PATCH] bluetooth: Add support for EP-B3536 USB Bluetooth adapter Jack Murray
2022-01-16 6:07 ` Paul Menzel [this message]
2022-01-16 13:17 ` Jack Murray
2022-02-07 15:40 ` Marcel Holtmann
2022-02-08 19:35 ` Jack Murray
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=d2b50954-5303-a547-3be8-35e6c3208a1d@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=kernel@c0rporation.com \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.