diff options
author | Simon Fels | 2015-09-02 12:10:12 +0200 |
---|---|---|
committer | Marcel Holtmann | 2015-09-17 13:20:02 +0200 |
commit | 6b3cc1db68ac83647d37f7d16f0261621eda24aa (patch) | |
tree | 65ecf00f7779f21157abbe0ada09f5b5427e3e35 /crypto | |
parent | 1b1975749f856946f716180ca94db52fb1ae3500 (diff) |
Bluetooth: close HCI device when user channel socket gets closed
With 9380f9eacfbbee701daa416edd6625efcd3e29e1 the order of unsetting
the HCI_USER_CHANNEL flag of the HCI device was reverted to ensure
the device is first closed before making it available again.
Due to hci_dev_close checking for HCI_USER_CHANNEL being set on the
device it was never really closed and was kept opened. We're now
calling hci_dev_do_close directly to make sure the device is correctly
closed and we keep the correct order to unset the flag on our device
object.
Signed-off-by: Simon Fels <simon.fels@canonical.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions