* [PATCH] Bluetooth: btusb: Add Lite-On 04ca:3807 for MediaTek MT7921
@ 2026-02-19 19:11 Dylan Eray
2026-02-19 19:17 ` Paul Menzel
0 siblings, 1 reply; 2+ messages in thread
From: Dylan Eray @ 2026-02-19 19:11 UTC (permalink / raw)
To: linux-bluetooth
Cc: luiz.dentz, sean.wang, linux-mediatek, linux-kernel, Dylan Eray
Add USB device ID (04ca:3807) for a Lite-On Wireless_Device containing
a MediaTek MT7921 (MT7920) Bluetooth chipset found in Acer laptops.
Without this entry, btusb binds via the generic USB class-based wildcard
match but never sets the BTUSB_MEDIATEK flag. This means btmtk never
triggers firmware loading, and the driver sends a raw HCI Reset that
the uninitialized chip cannot respond to, resulting in:
Bluetooth: hci0: Opcode 0x0c03 failed: -110
Signed-off-by: Dylan Eray <dylan.eray6@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 fcec8e5..fd637cf 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -705,6 +705,8 @@ static const struct usb_device_id quirks_table[] = {
BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x04ca, 0x3804), .driver_info = BTUSB_MEDIATEK |
BTUSB_WIDEBAND_SPEECH },
+ { USB_DEVICE(0x04ca, 0x3807), .driver_info = BTUSB_MEDIATEK |
+ BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x04ca, 0x38e4), .driver_info = BTUSB_MEDIATEK |
BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x13d3, 0x3568), .driver_info = BTUSB_MEDIATEK |
--
2.53.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Bluetooth: btusb: Add Lite-On 04ca:3807 for MediaTek MT7921
2026-02-19 19:11 [PATCH] Bluetooth: btusb: Add Lite-On 04ca:3807 for MediaTek MT7921 Dylan Eray
@ 2026-02-19 19:17 ` Paul Menzel
0 siblings, 0 replies; 2+ messages in thread
From: Paul Menzel @ 2026-02-19 19:17 UTC (permalink / raw)
To: Dylan Eray
Cc: linux-bluetooth, luiz.dentz, sean.wang, linux-mediatek,
linux-kernel
Dear Dylan,
Thank you for your patch.
Am 19.02.26 um 20:11 schrieb Dylan Eray:
> Add USB device ID (04ca:3807) for a Lite-On Wireless_Device containing
> a MediaTek MT7921 (MT7920) Bluetooth chipset found in Acer laptops.
>
> Without this entry, btusb binds via the generic USB class-based wildcard
> match but never sets the BTUSB_MEDIATEK flag. This means btmtk never
> triggers firmware loading, and the driver sends a raw HCI Reset that
> the uninitialized chip cannot respond to, resulting in:
>
> Bluetooth: hci0: Opcode 0x0c03 failed: -110
It’s common to add
> The information in /sys/kernel/debug/usb/devices about the Bluetooth
> device is listed as the below:
and paste the relevant output into the commit message.
> Signed-off-by: Dylan Eray <dylan.eray6@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 fcec8e5..fd637cf 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -705,6 +705,8 @@ static const struct usb_device_id quirks_table[] = {
> BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x04ca, 0x3804), .driver_info = BTUSB_MEDIATEK |
> BTUSB_WIDEBAND_SPEECH },
> + { USB_DEVICE(0x04ca, 0x3807), .driver_info = BTUSB_MEDIATEK |
> + BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x04ca, 0x38e4), .driver_info = BTUSB_MEDIATEK |
> BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x13d3, 0x3568), .driver_info = BTUSB_MEDIATEK |
The diff looks good.
With the changes above, feel free to add:
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-02-19 19:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-19 19:11 [PATCH] Bluetooth: btusb: Add Lite-On 04ca:3807 for MediaTek MT7921 Dylan Eray
2026-02-19 19:17 ` Paul Menzel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox