From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219514] PC does not resume from suspend, bisect points to btusb/mediatek
Date: Sun, 15 Dec 2024 21:06:05 +0000 [thread overview]
Message-ID: <bug-219514-62941-ESnLv8F142@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219514-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219514
--- Comment #2 from Tony Houghton (h@realh.co.uk) ---
I've copied btusb.c and btmtk.c from 6dc22ab9f085 to a checkout of 6.13-rc2 and
changed a few lines to make it compatible with some things that have changed
since then:
diff --git a/drivers/bluetooth/btmtk.c b/drivers/bluetooth/btmtk.c
index fe3b892f6c6e..9eeddbb7d991 100644
--- a/drivers/bluetooth/btmtk.c
+++ b/drivers/bluetooth/btmtk.c
@@ -6,7 +6,7 @@
#include <linux/firmware.h>
#include <linux/usb.h>
#include <linux/iopoll.h>
-#include <asm/unaligned.h>
+#include <linux/unaligned.h>
#include <net/bluetooth/bluetooth.h>
#include <net/bluetooth/hci_core.h>
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 034256c399dd..0e5cc454e2f9 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -17,7 +17,7 @@
#include <linux/suspend.h>
#include <linux/gpio/consumer.h>
#include <linux/debugfs.h>
-#include <asm/unaligned.h>
+#include <linux/unaligned.h>
#include <net/bluetooth/bluetooth.h>
#include <net/bluetooth/hci_core.h>
@@ -3887,8 +3887,8 @@ static int btusb_probe(struct usb_interface *intf,
if (id->driver_info & BTUSB_WIDEBAND_SPEECH)
set_bit(HCI_QUIRK_WIDEBAND_SPEECH_SUPPORTED, &hdev->quirks);
- if (id->driver_info & BTUSB_VALID_LE_STATES)
- set_bit(HCI_QUIRK_VALID_LE_STATES, &hdev->quirks);
+ if (!(id->driver_info & BTUSB_VALID_LE_STATES))
+ set_bit(HCI_QUIRK_BROKEN_LE_STATES, &hdev->quirks);
if (id->driver_info & BTUSB_DIGIANSWER) {
data->cmdreq_type = USB_TYPE_VENDOR;
Some guesswork was involved, but it seems to work for me. I'd like to try to
get to the bottom of the issue so I don't have to keep patching my kernel. Are
there any options I could try?
I've got plenty of experience with C, but not with the kernel, so if you could
give me some guidance such as a summary of what changed in ceac1cb0259d, what
code paths are taken during suspend/resume and any code tweaks I can try, it
would be much appreciated.
--
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:[~2024-12-15 21:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 19:43 [Bug 219514] New: PC does not resume from suspend, bisect points to btusb/mediatek bugzilla-daemon
2024-11-19 19:45 ` [Bug 219514] " bugzilla-daemon
2024-12-15 21:06 ` bugzilla-daemon [this message]
2024-12-15 21:14 ` [Bug,219514] " bluez.test.bot
2024-12-30 19:22 ` [Bug 219514] " bugzilla-daemon
2025-01-02 23:55 ` bugzilla-daemon
2025-01-04 5:36 ` bugzilla-daemon
2025-01-04 6:48 ` bugzilla-daemon
2025-01-04 15:27 ` bugzilla-daemon
2025-01-06 8:53 ` bugzilla-daemon
2025-01-06 10:18 ` bugzilla-daemon
2025-01-06 13:09 ` bugzilla-daemon
2025-01-06 14:41 ` bugzilla-daemon
2025-01-07 9:05 ` bugzilla-daemon
2025-01-07 21:02 ` bugzilla-daemon
2025-01-09 18:15 ` bugzilla-daemon
2025-02-07 21:22 ` bugzilla-daemon
2025-02-07 21:24 ` bugzilla-daemon
2025-02-17 15:22 ` bugzilla-daemon
2025-02-17 15:27 ` 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-219514-62941-ESnLv8F142@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.