Searched hist:"9380 f9eacfbbee701daa416edd6625efcd3e29e1" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/net/bluetooth/ |
| H A D | hci_sock.c | diff 6b3cc1db68ac83647d37f7d16f0261621eda24aa Wed Sep 02 05:10:12 CDT 2015 Simon Fels <simon.fels@canonical.com> 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>
diff 9380f9eacfbbee701daa416edd6625efcd3e29e1 Thu May 21 09:46:41 CDT 2015 Loic Poulain <loic.poulain@intel.com> Bluetooth: Reorder HCI user channel socket release
The hci close method needs to know if we are in user channel context.
Only add the index to mgmt once close is performed.
Signed-off-by: Loic Poulain <loic.poulain@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
|
| H A D | hci_core.c | diff 6b3cc1db68ac83647d37f7d16f0261621eda24aa Wed Sep 02 05:10:12 CDT 2015 Simon Fels <simon.fels@canonical.com> 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>
|
| /openbmc/linux/include/net/bluetooth/ |
| H A D | hci_core.h | diff 6b3cc1db68ac83647d37f7d16f0261621eda24aa Wed Sep 02 05:10:12 CDT 2015 Simon Fels <simon.fels@canonical.com> 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>
|