diff options
| author | Jonas Dreßler <[email protected]> | 2024-01-07 18:02:48 +0000 |
|---|---|---|
| committer | Luiz Augusto von Dentz <[email protected]> | 2024-03-06 22:22:37 +0000 |
| commit | fee054b7579fe252f8b9e6c17b9c5bfdaa84dd7e (patch) | |
| tree | a83c6f28235fa0e3876e537e0b406299927b36a7 /net/bluetooth/hci_request.c | |
| parent | Bluetooth: Remove HCI_POWER_OFF_TIMEOUT (diff) | |
| download | kernel-fee054b7579fe252f8b9e6c17b9c5bfdaa84dd7e.tar.gz kernel-fee054b7579fe252f8b9e6c17b9c5bfdaa84dd7e.zip | |
Bluetooth: mgmt: Remove leftover queuing of power_off work
Queuing of power_off work was introduced in these functions with commits
8b064a3ad377 ("Bluetooth: Clean up HCI state when doing power off") and
c9910d0fb4fc ("Bluetooth: Fix disconnecting connections in non-connected
states") in an effort to clean up state and do things like disconnecting
devices before actually powering off the device.
After that, commit a3172b7eb4a2 ("Bluetooth: Add timer to force power off")
introduced a timeout to ensure that the device actually got powered off,
even if some of the cleanup work would never complete.
This code later got refactored with commit cf75ad8b41d2 ("Bluetooth:
hci_sync: Convert MGMT_SET_POWERED"), which made powering off the device
synchronous and removed the need for initiating the power_off work from
other places. The timeout mentioned above got removed too, because we now
also made use of the command timeout during power on/off.
These days the power_off work still exists, but it only seems to only be
used for HCI_AUTO_OFF functionality, which is why we never noticed
those two leftover places where we queue power_off work. So let's remove
that code.
Fixes: cf75ad8b41d2 ("Bluetooth: hci_sync: Convert MGMT_SET_POWERED")
Signed-off-by: Jonas Dreßler <[email protected]>
Signed-off-by: Luiz Augusto von Dentz <[email protected]>
Diffstat (limited to 'net/bluetooth/hci_request.c')
0 files changed, 0 insertions, 0 deletions