public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217475] Foxconn / Hon Hai Bluetooth adapter 0489:e0cd stops working on ThinkPad T14s AMD Gen1
Date: Tue, 10 Mar 2026 11:38:45 +0000	[thread overview]
Message-ID: <bug-217475-208809-sZcSmtoYTv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217475-208809@https.bugzilla.kernel.org/>

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

--- Comment #5 from Alberto Garcia (berto@igalia.com) ---
Hi, I'm on Linux 6.12.73 now.

I found that btusb.enable_autosuspend=n seems to solve the problem.

Commit 67dba2c28fe0 ("btmtk: Fix failed to send func ctrl for MediaTek
devices.") prevents the device from suspending during btmtk_usb_shutdown() to
avoid timeout errors similar to the ones I'm experiencing:

   btmtk_usb_hci_wmt_sync() hci0: Execution of wmt command timed out
   btmtk_usb_shutdown() hci0: Failed to send wmt func ctrl (-110)

So I wonder if the same thing is happening during btmtk_usb_setup().

There's a long gap until the bluetooth driver is loaded. This computer has an
external USB-C dock that sometimes takes a long time to initialize, also the
hard drive is encrypted with LUKS so the btusb driver (and its firmware) cannot
be loaded until I enter the password and the rootfs is decrypted. All this can
take easily 20 seconds.

So maybe the bluetooth adapter suspends before the driver is loaded and that's
why the initialization fails, does that make sense?

I tried patching btmtk_usb_setup() with the same approach and so far I haven't
been able to reproduce the issue anymore.

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

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-03-10 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 18:36 [Bug 217475] New: Foxconn / Hon Hai Bluetooth adapter 0489:e0cd stops working on ThinkPad T14s AMD Gen1 bugzilla-daemon
2023-05-24  0:49 ` [Bug 217475] " bugzilla-daemon
2023-05-24  9:05 ` bugzilla-daemon
2023-05-24  9:11 ` bugzilla-daemon
2023-12-15 20:50 ` bugzilla-daemon
2026-03-10 11:38 ` bugzilla-daemon [this message]
2026-03-10 11:42 ` bugzilla-daemon
2026-03-10 18:42 ` 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-217475-208809-sZcSmtoYTv@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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