https://bugzilla.kernel.org/show_bug.cgi?id=60824 --- Comment #206 from Jack (ostroffjh@xxxxxxxxxxxxxxxxxxxxx) --- I just upgraded to kernel 5.15.0. My dongle seemed to be recognized, but was not recognized as a controller. Adding the patch I have labelled as skip-HCI_FLT_CLEAR_ALL.patch got things working. So, one of the patches (which I had labelled as Bluetooth-btusb-Make-the-CSR-clone-chip-force-suspend-workaround-more-generic.diff) is included in the upstream kernel sources as of 5.14.somethign, but only part of the other one. Similar to my earlier comment 195, selected output from dmesg: [ 11.715825] usb 1-2: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 [ 11.715831] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 11.715833] usb 1-2: Product: BT DONGLE10 [ 20.888671] btusb: unknown parameter 'fixups' ignored [ 20.889220] usbcore: registered new interface driver btusb [ 20.891778] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once... [ 20.891788] Bluetooth: hci0: CSR: Failed to suspend the device for our Barrot 8041a02 receive-issue workaround [ 27.326897] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 27.326903] Bluetooth: BNEP filters: protocol multicast [ 27.326910] Bluetooth: BNEP socket layer initialized [ 58.539089] Bluetooth: RFCOMM TTY layer initialized [ 58.539100] Bluetooth: RFCOMM socket layer initialized [ 58.539107] Bluetooth: RFCOMM ver 1.11 [ 109.777696] input: WH-CH700N (AVRCP) as /devices/virtual/input/input23 I'm also still curious how to get the "fixups" recognized, although it doesn't appear I actually need any now. -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
