On Mon, May 13, 2024 at 2:14 PM Данил <danstiv404@xxxxxxxxx> wrote: > > Hello! > I encountered a problem with a USB bluetooth adapter which probably uses > an ATS2851. > I'm not 100% sure about this, but the symptoms match the problem > described in the patch. > > Here are the patches I found. > 1. It seems to have been applied. > https://lore.kernel.org/linux-bluetooth/168150781825.20001.4973139468540739153.git-patchwork-notify@xxxxxxxxxx/T/#t > > 2. It seems it was not applied. > https://lore.kernel.org/linux-bluetooth/20230323135804.3962783-1-raul.cheleguini@xxxxxxxxx/T/#t > > 3. It seems it was not applied. > https://patchwork.kernel.org/project/bluetooth/patch/20230426184017.2051211-1-raul.cheleguini@xxxxxxxxx/#25314789 > > Patches 2 and 3 were not applied, as I understand, due to some minor > problems with code formatting, is it possible to complete the process of > applying them? > > Here is some information about the device: > > dmesg > [ 0.000000] Linux version 6.6.13+bpo-rt-amd64 > (debian-kernel@xxxxxxxxxxxxxxxx) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU > ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_RT Debian > 6.6.13-1~bpo12+1 (2024-02-15) > [ 0.000000] Command line: > BOOT_IMAGE=/boot/vmlinuz-6.6.13+bpo-rt-amd64 > root=UUID=b9338182-ab4b-48cb-b492-60e7ed340018 ro > systemd.unified_cgroup_hierarchy=false quiet reboot=pci > ... > [ 110.420763] usb 1-2: new full-speed USB device number 2 using uhci_hcd > [ 110.609798] usb 1-2: New USB device found, idVendor=10d7, > idProduct=b012, bcdDevice=88.91 > [ 110.609814] usb 1-2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 110.609820] usb 1-2: Product: general adapter > [ 110.609824] usb 1-2: Manufacturer: Actions > [ 110.609829] usb 1-2: SerialNumber: ACTIONS1234 > [ 110.614223] Bluetooth: hci1: HCI Read Default Erroneous Data > Reporting command is advertised, but not supported. > [ 110.614245] Bluetooth: hci1: HCI Read Transmit Power Level command is > advertised, but not supported. > [ 110.614252] Bluetooth: hci1: HCI LE Set Random Private Address > Timeout command is advertised, but not supported. > [ 110.666673] Bluetooth: MGMT ver 1.22 > > lsusb -v > ... > Bus 001 Device 002: ID 10d7:b012 Actions general adapter > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 224 Wireless > bDeviceSubClass 1 Radio Frequency > bDeviceProtocol 1 Bluetooth > bMaxPacketSize0 64 > idVendor 0x10d7 > idProduct 0xb012 > bcdDevice 88.91 > iManufacturer 1 Actions > iProduct 2 general adapter > iSerial 3 ACTIONS1234 > bNumConfigurations 1 > ... > > btmon > ... > < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 58 #48 > [hci0] 2.000505 > Filter policy: Accept list is not used (0x00) > Own address type: Public (0x00) > Peer address type: Random (0x01) > Peer address: E8:42:26:5C:0F:07 (Static) > Initiating PHYs: 0x07 > Entry 0: LE 1M > Scan interval: 60.000 msec (0x0060) > Scan window: 60.000 msec (0x0060) > Min connection interval: 30.00 msec (0x0018) > Max connection interval: 50.00 msec (0x0028) > Connection latency: 0 (0x0000) > Supervision timeout: 420 msec (0x002a) > Min connection length: 0.000 msec (0x0000) > Max connection length: 0.000 msec (0x0000) > Entry 1: LE 2M > Scan interval: 60.000 msec (0x0060) > Scan window: 60.000 msec (0x0060) > Min connection interval: 30.00 msec (0x0018) > Max connection interval: 50.00 msec (0x0028) > Connection latency: 0 (0x0000) > Supervision timeout: 420 msec (0x002a) > Min connection length: 0.000 msec (0x0000) > Max connection length: 0.000 msec (0x0000) > Entry 2: LE Coded > Scan interval: 60.000 msec (0x0060) > Scan window: 60.000 msec (0x0060) > Min connection interval: 30.00 msec (0x0018) > Max connection interval: 50.00 msec (0x0028) > Connection latency: 0 (0x0000) > Supervision timeout: 420 msec (0x002a) > Min connection length: 0.000 msec (0x0000) > Max connection length: 0.000 msec (0x0000) > > HCI Event: Command Status (0x0f) plen 4 #49 [hci0] 2.001242 > LE Extended Create Connection (0x08|0x0043) ncmd 1 > Status: Unknown HCI Command (0x01) > ... > The adapter supports le, I was able to connect to a le device from > windows 11. > Hello, To provide some context on the patches. With all patches applied locally I managed to pair my Logitech mouse and use it, but the solution I don't feel is ideal, there were errors and other devices might not pair well. At the time I asked the datasheet for this adapter to multiple vendors, without success. I extensively researched forums, pdf repositories, and I did not find relevant documentation. One thing that I noticed watching the HCI dumps of a pairing process in Windows and Linux is that, in Linux the dump is chaotic and parallel. In other hand, the dump in Windows is organized and more serialized. I don't know if I missed something related to this at that time. Anyways, my debug setup for this is disassembled right now, if anyone is willing to resume and progress this issue is more than welcomed.
