Bluetooth: btusb: Add Lite-On 04ca:3807 for MediaTek MT7921
Subsystems (2)
PATCH 1/1 Bluetooth: btusb: Add Lite-On 04ca:3807 for MediaTek MT7921
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
--- drivers/bluetooth/btusb.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/bluetooth/btusb.c +2 -0
@@ -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 |
Signature · 1 line
2.53.0
Dear Dylan,
Thank you for your patch.
Am 19.02.26 um 20:11 schrieb Dylan Eray:
Quoted 9 lines
Add USB device ID (04ca:3807) for a Lite-On
Wireless_Devicecontaining 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_MEDIATEKflag. 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
Quoted 1 line
The information in
/sys/kernel/debug/usb/devicesabout the Bluetooth device is listed as the below:
and paste the relevant output into the commit message.
Quoted 10 lines
Signed-off-by Dylan Eray <[email protected]>--- drivers/bluetooth/btusb.c | 2 ++ 1 file changed, 2 insertions(+)drivers/bluetooth/btusb.c +0
-0
drivers/bluetooth/btusb.c static const struct usb_device_id quirks_table[] = { · line 712
Quoted 8 lines
drivers/bluetooth/btusb.c +2
-0@@ -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:
Kind regards,
Paul
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1055639
---Test result---
Test Summary:
CheckPatch PENDING 0.42 seconds GitLint PENDING 0.29 seconds SubjectPrefix PASS 0.06 seconds BuildKernel PASS 25.52 seconds CheckAllWarning PASS 28.37 seconds CheckSparse WARNING 36.21 seconds BuildKernel32 PASS 25.20 seconds TestRunnerSetup PASS 561.05 seconds TestRunner_l2cap-tester PASS 28.11 seconds TestRunner_iso-tester PASS 86.15 seconds TestRunner_bnep-tester PASS 6.39 seconds TestRunner_mgmt-tester FAIL 125.07 seconds TestRunner_rfcomm-tester PASS 9.67 seconds TestRunner_sco-tester FAIL 14.55 seconds TestRunner_ioctl-tester PASS 10.20 seconds TestRunner_mesh-tester FAIL 11.53 seconds TestRunner_smp-tester PASS 8.69 seconds TestRunner_userchan-tester PASS 6.67 seconds IncrementalBuild PENDING 0.96 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:drivers/bluetooth/btusb.c:4661:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4662:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4664:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4665:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4667:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4668:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4670:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4671:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4673:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4674:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4675:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4676:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4676:1: error: bad constant expression
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.103 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.802 seconds Mesh - Send cancel - 2 Timed out 1.992 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series Output:
---
Regards,
Linux Bluetooth