From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219553] Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) not able to connnect to Logitech MX Master 3S
Date: Mon, 24 Mar 2025 14:17:17 +0000 [thread overview]
Message-ID: <bug-219553-62941-kXBiFFbVqD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219553-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219553
--- Comment #4 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Ike Devolder from comment #2)
> 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@gmail.com>
> 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
These are not the same controller as the bug description suggests, so if you
are having something with GfP2/GaP that is probably something different.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-03-24 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 17:44 [Bug 219553] New: Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) not able to connnect to Logitech MX Master 3S bugzilla-daemon
2025-03-16 19:45 ` [Bug 219553] " bugzilla-daemon
2025-03-24 13:32 ` bugzilla-daemon
2025-03-24 13:45 ` [Bug,219553] " bluez.test.bot
2025-03-24 13:53 ` [Bug 219553] " bugzilla-daemon
2025-03-24 14:17 ` bugzilla-daemon [this message]
2025-03-24 14:32 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-219553-62941-kXBiFFbVqD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).