* [PATCH] Bluetooth: btusb: clear remote wake on idle Intel ACPI paths
@ 2026-03-18 19:51 Sean Rhodes
2026-03-18 21:03 ` bluez.test.bot
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Sean Rhodes @ 2026-03-18 19:51 UTC (permalink / raw)
To: linux-kernel; +Cc: Marcel Holtmann, Luiz Augusto von Dentz, linux-bluetooth
Commit 6953217d9f44 ("usb: core: allow ACPI-managed hard-wired ports
to power off") allows internal USB devices on ACPI-managed hard-wired
ports to use the existing runtime power-off path. For Intel combined USB
Bluetooth controllers, btusb still keeps runtime remote wake enabled for
as long as the adapter is open, which prevents the USB PM core from
dropping the last child reference and powering the port off while idle.
Only keep runtime remote wake enabled while the controller is expected
to signal activity on its own: established links, discovery, LE scan,
LE advertising, or BR/EDR page/inquiry scan. When those are idle, clear
needs_remote_wakeup so autosuspend can power-manage the port and a later
host-initiated command can resume the device again.
Signed-off-by: Sean Rhodes <sean@starlabs.systems>
---
drivers/bluetooth/btusb.c | 50 +++++++++++++++++++++++++++++++++++++--
1 file changed, 48 insertions(+), 2 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 5e9ebf0c5312..9df8a7c3254b 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -901,6 +901,7 @@ struct btusb_data {
unsigned long flags;
bool poll_sync;
+ bool intel_combined;
int intr_interval;
struct work_struct work;
struct work_struct waker;
@@ -958,6 +959,9 @@ struct btusb_data {
struct qca_dump_info qca_dump;
};
+static bool btusb_intel_idle_power_manageable(struct btusb_data *data);
+static bool btusb_needs_runtime_remote_wakeup(struct btusb_data *data);
+
static void btusb_reset(struct hci_dev *hdev)
{
struct btusb_data *data;
@@ -1151,12 +1155,19 @@ static inline void btusb_free_frags(struct btusb_data *data)
static int btusb_recv_event(struct btusb_data *data, struct sk_buff *skb)
{
+ int err;
+
if (data->intr_interval) {
/* Trigger dequeue immediately if an event is received */
schedule_delayed_work(&data->rx_work, 0);
}
- return data->recv_event(data->hdev, skb);
+ err = data->recv_event(data->hdev, skb);
+ if (!err)
+ data->intf->needs_remote_wakeup =
+ btusb_needs_runtime_remote_wakeup(data);
+
+ return err;
}
static int btusb_recv_intr(struct btusb_data *data, void *buffer, int count)
@@ -1924,7 +1935,8 @@ static int btusb_open(struct hci_dev *hdev)
goto setup_fail;
}
- data->intf->needs_remote_wakeup = 1;
+ data->intf->needs_remote_wakeup =
+ btusb_needs_runtime_remote_wakeup(data);
if (test_and_set_bit(BTUSB_INTR_RUNNING, &data->flags))
goto done;
@@ -1967,6 +1979,38 @@ static void btusb_stop_traffic(struct btusb_data *data)
usb_kill_anchored_urbs(&data->ctrl_anchor);
}
+static bool btusb_intel_idle_power_manageable(struct btusb_data *data)
+{
+ struct usb_device *udev = data->udev;
+
+ return data->intel_combined && udev->parent &&
+ usb_acpi_power_manageable(udev->parent, udev->portnum - 1);
+}
+
+static bool btusb_needs_runtime_remote_wakeup(struct btusb_data *data)
+{
+ struct hci_dev *hdev = data->hdev;
+
+ if (!btusb_intel_idle_power_manageable(data))
+ return true;
+
+ if (hci_conn_count(hdev))
+ return true;
+
+ if (hdev->discovery.state == DISCOVERY_FINDING ||
+ hdev->discovery.state == DISCOVERY_RESOLVING)
+ return true;
+
+ if (hci_dev_test_flag(hdev, HCI_LE_SCAN) ||
+ hci_dev_test_flag(hdev, HCI_LE_ADV) ||
+ hci_dev_test_flag(hdev, HCI_ADVERTISING) ||
+ test_bit(HCI_PSCAN, &hdev->flags) ||
+ test_bit(HCI_ISCAN, &hdev->flags))
+ return true;
+
+ return false;
+}
+
static int btusb_close(struct hci_dev *hdev)
{
struct btusb_data *data = hci_get_drvdata(hdev);
@@ -4041,6 +4085,8 @@ static int btusb_probe(struct usb_interface *intf,
data->recv_bulk = btusb_recv_bulk;
if (id->driver_info & BTUSB_INTEL_COMBINED) {
+ data->intel_combined = true;
+
/* Allocate extra space for Intel device */
priv_size += sizeof(struct btintel_data);
^ permalink raw reply related [flat|nested] 4+ messages in thread* RE: Bluetooth: btusb: clear remote wake on idle Intel ACPI paths
2026-03-18 19:51 [PATCH] Bluetooth: btusb: clear remote wake on idle Intel ACPI paths Sean Rhodes
@ 2026-03-18 21:03 ` bluez.test.bot
2026-03-19 7:34 ` [PATCH] " Paul Menzel
2026-04-09 20:02 ` bluez.test.bot
2 siblings, 0 replies; 4+ messages in thread
From: bluez.test.bot @ 2026-03-18 21:03 UTC (permalink / raw)
To: linux-bluetooth, sean
[-- Attachment #1: Type: text/plain, Size: 2833 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1068865
---Test result---
Test Summary:
CheckPatch PENDING 0.61 seconds
GitLint PENDING 0.38 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 26.88 seconds
CheckAllWarning PASS 29.82 seconds
CheckSparse PASS 28.22 seconds
BuildKernel32 PASS 26.09 seconds
TestRunnerSetup PASS 576.58 seconds
TestRunner_l2cap-tester PASS 27.73 seconds
TestRunner_iso-tester FAIL 31.08 seconds
TestRunner_bnep-tester PASS 6.33 seconds
TestRunner_mgmt-tester FAIL 113.55 seconds
TestRunner_rfcomm-tester PASS 9.48 seconds
TestRunner_sco-tester FAIL 14.67 seconds
TestRunner_ioctl-tester PASS 10.34 seconds
TestRunner_mesh-tester FAIL 12.53 seconds
TestRunner_smp-tester PASS 8.52 seconds
TestRunner_userchan-tester PASS 6.61 seconds
IncrementalBuild PENDING 1.08 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in le_read_features_complete+0x7e/0x2b0
Total: 141, Passed: 141 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.106 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.708 seconds
Mesh - Send cancel - 2 Timed out 1.996 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] Bluetooth: btusb: clear remote wake on idle Intel ACPI paths
2026-03-18 19:51 [PATCH] Bluetooth: btusb: clear remote wake on idle Intel ACPI paths Sean Rhodes
2026-03-18 21:03 ` bluez.test.bot
@ 2026-03-19 7:34 ` Paul Menzel
2026-04-09 20:02 ` bluez.test.bot
2 siblings, 0 replies; 4+ messages in thread
From: Paul Menzel @ 2026-03-19 7:34 UTC (permalink / raw)
To: Sean Rhodes
Cc: Marcel Holtmann, Luiz Augusto von Dentz, linux-bluetooth,
linux-kernel
Dear Sean,
Thank you for your patch.
Am 18.03.26 um 20:51 schrieb Sean Rhodes:
> Commit 6953217d9f44 ("usb: core: allow ACPI-managed hard-wired ports
> to power off") allows internal USB devices on ACPI-managed hard-wired
I am unable to find the commit [1] besides on the Linux kernel list [2].
> ports to use the existing runtime power-off path. For Intel combined USB
> Bluetooth controllers, btusb still keeps runtime remote wake enabled for
> as long as the adapter is open, which prevents the USB PM core from
> dropping the last child reference and powering the port off while idle.
>
> Only keep runtime remote wake enabled while the controller is expected
> to signal activity on its own: established links, discovery, LE scan,
> LE advertising, or BR/EDR page/inquiry scan. When those are idle, clear
> needs_remote_wakeup so autosuspend can power-manage the port and a later
> host-initiated command can resume the device again.
Could you add a test case and the device you tested with, and possible
measurement numbers?
> Signed-off-by: Sean Rhodes <sean@starlabs.systems>
> ---
> drivers/bluetooth/btusb.c | 50 +++++++++++++++++++++++++++++++++++++--
> 1 file changed, 48 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index 5e9ebf0c5312..9df8a7c3254b 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -901,6 +901,7 @@ struct btusb_data {
> unsigned long flags;
>
> bool poll_sync;
> + bool intel_combined;
> int intr_interval;
> struct work_struct work;
> struct work_struct waker;
> @@ -958,6 +959,9 @@ struct btusb_data {
> struct qca_dump_info qca_dump;
> };
>
> +static bool btusb_intel_idle_power_manageable(struct btusb_data *data);
> +static bool btusb_needs_runtime_remote_wakeup(struct btusb_data *data);
> +
> static void btusb_reset(struct hci_dev *hdev)
> {
> struct btusb_data *data;
> @@ -1151,12 +1155,19 @@ static inline void btusb_free_frags(struct btusb_data *data)
>
> static int btusb_recv_event(struct btusb_data *data, struct sk_buff *skb)
> {
> + int err;
> +
> if (data->intr_interval) {
> /* Trigger dequeue immediately if an event is received */
> schedule_delayed_work(&data->rx_work, 0);
> }
>
> - return data->recv_event(data->hdev, skb);
> + err = data->recv_event(data->hdev, skb);
> + if (!err)
> + data->intf->needs_remote_wakeup =
> + btusb_needs_runtime_remote_wakeup(data);
> +
> + return err;
> }
>
> static int btusb_recv_intr(struct btusb_data *data, void *buffer, int count)
> @@ -1924,7 +1935,8 @@ static int btusb_open(struct hci_dev *hdev)
> goto setup_fail;
> }
>
> - data->intf->needs_remote_wakeup = 1;
> + data->intf->needs_remote_wakeup =
> + btusb_needs_runtime_remote_wakeup(data);
>
> if (test_and_set_bit(BTUSB_INTR_RUNNING, &data->flags))
> goto done;
> @@ -1967,6 +1979,38 @@ static void btusb_stop_traffic(struct btusb_data *data)
> usb_kill_anchored_urbs(&data->ctrl_anchor);
> }
>
> +static bool btusb_intel_idle_power_manageable(struct btusb_data *data)
> +{
> + struct usb_device *udev = data->udev;
> +
> + return data->intel_combined && udev->parent &&
> + usb_acpi_power_manageable(udev->parent, udev->portnum - 1);
> +}
> +
> +static bool btusb_needs_runtime_remote_wakeup(struct btusb_data *data)
> +{
> + struct hci_dev *hdev = data->hdev;
> +
> + if (!btusb_intel_idle_power_manageable(data))
> + return true;
> +
> + if (hci_conn_count(hdev))
> + return true;
> +
> + if (hdev->discovery.state == DISCOVERY_FINDING ||
> + hdev->discovery.state == DISCOVERY_RESOLVING)
> + return true;
> +
> + if (hci_dev_test_flag(hdev, HCI_LE_SCAN) ||
> + hci_dev_test_flag(hdev, HCI_LE_ADV) ||
> + hci_dev_test_flag(hdev, HCI_ADVERTISING) ||
> + test_bit(HCI_PSCAN, &hdev->flags) ||
> + test_bit(HCI_ISCAN, &hdev->flags))
> + return true;
> +
> + return false;
> +}
> +
> static int btusb_close(struct hci_dev *hdev)
> {
> struct btusb_data *data = hci_get_drvdata(hdev);
> @@ -4041,6 +4085,8 @@ static int btusb_probe(struct usb_interface *intf,
> data->recv_bulk = btusb_recv_bulk;
>
> if (id->driver_info & BTUSB_INTEL_COMBINED) {
> + data->intel_combined = true;
> +
I am not clear about this hunk. Could you please elaborate?
> /* Allocate extra space for Intel device */
> priv_size += sizeof(struct btintel_data);
Kind regards,
Paul
PS: Thank you so much for working on such details! Do you know, if this
is also a problem on Google Chromebooks/-boxes?
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/log/?h=usb-next&qt=author&q=rhodes
[2]:
https://lore.kernel.org/all/20260315223433.23452-1-sean@starlabs.systems/
^ permalink raw reply [flat|nested] 4+ messages in thread* RE: Bluetooth: btusb: clear remote wake on idle Intel ACPI paths
2026-03-18 19:51 [PATCH] Bluetooth: btusb: clear remote wake on idle Intel ACPI paths Sean Rhodes
2026-03-18 21:03 ` bluez.test.bot
2026-03-19 7:34 ` [PATCH] " Paul Menzel
@ 2026-04-09 20:02 ` bluez.test.bot
2 siblings, 0 replies; 4+ messages in thread
From: bluez.test.bot @ 2026-04-09 20:02 UTC (permalink / raw)
To: linux-bluetooth, sean
[-- Attachment #1: Type: text/plain, Size: 6877 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1068865
---Test result---
Test Summary:
CheckPatch PENDING 0.44 seconds
GitLint PENDING 0.31 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 26.95 seconds
CheckAllWarning PASS 29.21 seconds
CheckSparse PASS 27.83 seconds
BuildKernel32 PASS 25.82 seconds
TestRunnerSetup PASS 574.90 seconds
TestRunner_l2cap-tester PASS 27.97 seconds
TestRunner_iso-tester PASS 40.39 seconds
TestRunner_bnep-tester PASS 6.34 seconds
TestRunner_mgmt-tester FAIL 116.37 seconds
TestRunner_rfcomm-tester PASS 9.46 seconds
TestRunner_sco-tester FAIL 14.32 seconds
TestRunner_ioctl-tester PASS 10.12 seconds
TestRunner_mesh-tester FAIL 11.50 seconds
TestRunner_smp-tester PASS 8.51 seconds
TestRunner_userchan-tester PASS 6.65 seconds
TestRunner_6lowpan-tester FAIL 8.56 seconds
IncrementalBuild PENDING 0.36 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.112 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-gb89f44c2faaf #1 Not tainted
------------------------------------------------------
kworker/u5:2/117 is trying to acquire lock:
ffff888002075240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0
but task is already holding lock:
ffff888002604220 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&conn->lock){+.+.}-{3:3}:
lock_acquire+0xf7/0x2c0
_raw_spin_lock+0x2a/0x40
sco_sock_connect+0x4d7/0x1280
__sys_connect+0x1a3/0x260
__x64_sys_connect+0x6e/0xb0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
check_prev_add+0xe9/0xc70
__lock_acquire+0x1457/0x1df0
lock_acquire+0xf7/0x2c0
lock_sock_nested+0x36/0xd0
sco_connect_cfm+0x358/0x8d0
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
other info that might help us debug this:
...
BUG: sleeping function called from invalid context at net/core/sock.c:3782
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-gb89f44c2faaf #1 PREEMPT(lazy)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
<TASK>
dump_stack_lvl+0x49/0x60
__might_resched+0x2ea/0x500
lock_sock_nested+0x47/0xd0
? sco_connect_cfm+0x358/0x8d0
sco_connect_cfm+0x358/0x8d0
? hci_debugfs_create_conn+0x190/0x210
? __pfx_sco_connect_cfm+0x10/0x10
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
? __pfx_hci_sync_conn_complete_evt+0x10/0x10
? __pfx_hci_event_packet+0x10/0x10
? mark_held_locks+0x49/0x80
? lockdep_hardirqs_on_prepare+0xd4/0x180
? _raw_spin_unlock_irqrestore+0x2c/0x50
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
? __pfx_process_scheduled_works+0x10/0x10
? lock_acquire+0xf7/0x2c0
? lock_is_held_type+0x9b/0x110
? __pfx_hci_rx_work+0x10/0x10
worker_thread+0x4ff/0xba0
? _raw_spin_unlock_irqrestore+0x2c/0x50
? __pfx_worker_thread+0x10/0x10
kthread+0x368/0x490
? _raw_spin_unlock_irq+0x23/0x40
? __pfx_kthread+0x10/0x10
ret_from_fork+0x498/0x7e0
? __pfx_ret_from_fork+0x10/0x10
? __switch_to+0x9e4/0xe50
? __switch_to_asm+0x32/0x60
...
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.854 seconds
Mesh - Send cancel - 2 Timed out 1.993 seconds
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-gb89f44c2faaf #1 Not tainted
------------------------------------------------------
kworker/0:1/11 is trying to acquire lock:
ffff8880026e1140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180
but task is already holding lock:
ffffffffabe4d720 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #4 (rtnl_mutex){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
lowpan_register_netdev+0x11/0x30
chan_ready_cb+0x836/0xd00
l2cap_recv_frame+0x6a06/0x8920
l2cap_recv_acldata+0x790/0xdf0
hci_rx_work+0x500/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
-> #3 (&chan->lock#3/1){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
l2cap_chan_connect+0x74e/0x1980
lowpan_control_write+0x523/0x660
full_proxy_write+0x10b/0x190
vfs_write+0x1c0/0xf60
ksys_write+0xf1/0x1d0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #2 (&conn->lock){+.+.}-{4:4}:
...
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluetooth-next/pull/21/checks
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-04-09 20:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-18 19:51 [PATCH] Bluetooth: btusb: clear remote wake on idle Intel ACPI paths Sean Rhodes
2026-03-18 21:03 ` bluez.test.bot
2026-03-19 7:34 ` [PATCH] " Paul Menzel
2026-04-09 20:02 ` bluez.test.bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox