Bluetooth: Move handling of HCI_RUNNING flag into core

Setting and clearing of HCI_RUNNING flag in each and every driver is
just duplicating the same code all over the place. So instead of having
the driver do it in their hdev->open and hdev->close callbacks, set it
globally in the core transport handling.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>

1 files changed, 0 insertions, 8 deletions

diff --git a/drivers/bluetooth/bpa10x.c b/drivers/bluetooth/bpa10x.c
index 59b892464be5..88e004ee137e 100644
--- a/drivers/bluetooth/bpa10x.c
+++ b/drivers/bluetooth/bpa10x.c
@@ -304,9 +304,6 @@ static int bpa10x_open(struct hci_dev *hdev)
 
         BT_DBG("%s", hdev->name);
 
-        if (test_and_set_bit(HCI_RUNNING, &hdev->flags))
-                return 0;
-
         err = bpa10x_submit_intr_urb(hdev);
         if (err < 0)
                 goto error;
@@ -320,8 +317,6 @@ static int bpa10x_open(struct hci_dev *hdev)
 error:
         usb_kill_anchored_urbs(&data->rx_anchor);
 
-        clear_bit(HCI_RUNNING, &hdev->flags);
-
         return err;
 }
 
@@ -331,9 +326,6 @@ static int bpa10x_close(struct hci_dev *hdev)
 
         BT_DBG("%s", hdev->name);
 
-        if (!test_and_clear_bit(HCI_RUNNING, &hdev->flags))
-                return 0;
-
         usb_kill_anchored_urbs(&data->rx_anchor);
 
         return 0;