summaryrefslogtreecommitdiff
path: root/LICENSES
diff options
context:
space:
mode:
authorJonas Dreßler <verdre@v0yd.nl>2024-01-07 21:02:48 +0300
committerLuiz Augusto von Dentz <luiz.von.dentz@intel.com>2024-03-07 01:22:37 +0300
commitfee054b7579fe252f8b9e6c17b9c5bfdaa84dd7e (patch)
treea83c6f28235fa0e3876e537e0b406299927b36a7 /LICENSES
parent968667f2e0345a67a6eea5a502f4659085666564 (diff)
downloadlinux-fee054b7579fe252f8b9e6c17b9c5bfdaa84dd7e.tar.xz
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 <verdre@v0yd.nl> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'LICENSES')
0 files changed, 0 insertions, 0 deletions