Tune Chameleon Bluetooth Kit Detection Polling |
||||
Issue descriptionAs part of adding Bluetooth kit detection to Chameleon, every Bluetooth kit waits a few seconds for detection. When we added more kits, the first detection after enabling the driver would fail with a 2 sec timeout (1 sec interval), so we're bumping this to 5 sec (1 sec interval). This may make Chameleon startup slower because it will always wait ~10 sec for Bluetooth kits, so let's track tuning this value as a bug. Ideas: - Reduce interval - Tweak timeout to 2-3 seconds - Only wait longer after the first time we enable the driver, instead of universally bumping the timeout. See: https://chromium-review.googlesource.com/c/chromiumos/platform/chameleon/+/636218
,
Sep 11 2017
,
Sep 11 2017
Without enabling the driver, does the Bluetooth kit show up in lsusb?
,
Sep 12 2017
As discussed in person, it does not, and it takes approximately 2 seconds (which was likely less before we added more dongles, hence the bug appearing) after enabling the driver for everything to be ready. We might go as low as 3 seconds, and we could lower the interval, which might make detect faster, but for future-proofing as we add more dongles, I'd suggest a lower interval if possible and keeping the timeout at 5 seconds. We might also want to check if the driver is already ready, in which case no polling is necessary.
,
Sep 15 2017
,
Sep 20 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by rjahagir@chromium.org
, Sep 8 2017