From: Oliver Neukum <oneukum@suse.com>
To: Sean Rhodes <sean@starlabs.systems>, linux-bluetooth@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
Xu Yang <xu.yang_2@nxp.com>, Kees Cook <kees@kernel.org>,
linux-usb@vger.kernel.org, Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-kernel@vger.kernel.org, Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [PATCH v2 2/2] Bluetooth: btusb: restore powered-off Intel adapters
Date: Tue, 22 Sep 2026 11:55:58 +0200 [thread overview]
Message-ID: <38d2639a-d5a3-4d01-ab86-8aa7e2fe75a7@suse.com> (raw)
In-Reply-To: <479fdb2638f34ccb02f35a40a34fcdc7cc41ccdf.1789679981.git.sean@starlabs.systems>
On 17.09.26 23:19, Sean Rhodes wrote:
Hi,
> Tested on a Star Labs Lite Mk IV with Intel 8087:0aaa. Three Bluetooth
> off/on cycles reached ACPI D3cold, restored the same hci0 without a USB
> disconnect, and discovery found nearby devices after resume.
Have you tested this with a different device and S4?
> Signed-off-by: Sean Rhodes <sean@starlabs.systems>
> ---
> drivers/bluetooth/btusb_main.c | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
[..]
> #ifdef CONFIG_DEV_COREDUMP
> static void btusb_coredump(struct device *dev)
> {
> @@ -5093,6 +5125,7 @@ static struct usb_driver btusb_driver = {
> .disconnect = btusb_disconnect,
> .suspend = pm_ptr(btusb_suspend),
> .resume = pm_ptr(btusb_resume),
> + .reset_resume = pm_ptr(btusb_reset_resume),
What happens to a connection if a lot of data has been lost?
Regards
Oliver
prev parent reply other threads:[~2026-09-22 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 21:19 [PATCH v2 0/2] Bluetooth: " Sean Rhodes
2026-09-17 21:19 ` [PATCH v2 1/2] usb: core: check ACPI port power during registration Sean Rhodes
2026-09-17 21:19 ` [PATCH v2 2/2] Bluetooth: btusb: restore powered-off Intel adapters Sean Rhodes
2026-09-22 9:55 ` Oliver Neukum [this message]
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=38d2639a-d5a3-4d01-ab86-8aa7e2fe75a7@suse.com \
--to=oneukum@suse.com \
--cc=acelan.kao@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kees@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=sean@starlabs.systems \
--cc=xu.yang_2@nxp.com \
/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
all inboxes | Powered by JetHome®