[Bug 219553] Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) not able to connnect to Logitech MX Master 3S

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=219553

Ike Devolder (ike.devolder@xxxxxxxxx) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ike.devolder@xxxxxxxxx

--- Comment #2 from Ike Devolder (ike.devolder@xxxxxxxxx) ---
Hi,

I think this is the exact same issue encountered on the Starlite Mk V

I have bisected the issue with a generic LE bluetooth keyboard here:
https://github.com/StarLabsLtd/firmware/issues/180#issuecomment-2732540740

And currently have that keyboard working on the Starlite Mk V with kernel
6.13.8 as it was working before with kernel 6.1.131 lts.

The change made to have it work is the following:

```
commit 49de268ad2d7f217579090da90a5d93cad281477 (HEAD ->
refs/heads/blackikeeagle-starlite-btintel)
Author: BlackEagle <ike.devolder@xxxxxxxxx>
Date:   Tue Mar 18 09:06:21 2025 +0100

    Bluetooth: btintel, don't reclassify signal for GfP2 and GaP

    Should fix issue with LE devices not being found or able to connect.

diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
index d496cf2c3411..4ecebae58792 100644
--- a/drivers/bluetooth/btintel.c
+++ b/drivers/bluetooth/btintel.c
@@ -3249,9 +3249,6 @@ static int btintel_setup_combined(struct hci_dev *hdev)
                break;
        case 0x18: /* GfP2 */
        case 0x1c: /* GaP */
-               /* Re-classify packet type for controllers with LE audio */
-               hdev->classify_pkt_type = btintel_classify_pkt_type;
-               fallthrough;
        case 0x17:
        case 0x19:
        case 0x1b:
```

https://gist.github.com/BlackIkeEagle/630e76164d9eca5f1eb617888c7f1576

This is not the real fix I guess since that reclassification of the pkt_type is
not there for no reason. But the skipping of it works around the issue

Hopefully this helps someone to find the actual issue

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux