diff options
author | Ondrej Jirman <megous@megous.com> | 2019-08-23 12:31:37 +0200 |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2019-09-05 17:27:22 +0200 |
commit | 16946de5905fff243c1e4415c4565803945e8c47 (patch) | |
tree | fd2659b7ae0b5f28f45cd9b324848d5cdcfa0d29 /drivers/bluetooth | |
parent | 52c8c7a766ecc49ff2e4c1db30b0a24a019e31d4 (diff) |
bluetooth: hci_bcm: Give more time to come out of reset
Some supported devices need more time to come out of reset (eg.
BCM4345C5 in AP6256).
I don't have/found a datasheet, so the value was arrive at
experimentally with the Oprange Pi 3 board. Without increased delay,
I got intermittent failures during probe. This is a Bluetooth 5.0
device, so maybe that's why it takes longer to initialize than the
others.
Signed-off-by: Ondrej Jirman <megous@megous.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'drivers/bluetooth')
-rw-r--r-- | drivers/bluetooth/hci_bcm.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c index 95c312ae94cf..7646636f2d18 100644 --- a/drivers/bluetooth/hci_bcm.c +++ b/drivers/bluetooth/hci_bcm.c @@ -260,7 +260,7 @@ static int bcm_gpio_set_power(struct bcm_device *dev, bool powered) } /* wait for device to power on and come out of reset */ - usleep_range(10000, 20000); + usleep_range(100000, 120000); dev->res_enabled = powered; |