diff options
| author |   Raquel Medina <raquel.medina@konsulko.com> | 2020-07-10 10:20:44 +0200 |
|---|---|---|
| committer | Raquel Medina <raquel.medina@konsulko.com> | 2020-07-13 13:01:37 +0200 |
| commit | 542f2a95de3f08b22969d1f4899aa343da5e44ae (patch) | |
| tree | 7dd56d80b4e9b4698fb55adfaefe7090b64f8224 /test | |
| parent | d542c5ce356117a96907763c963128208105f947 (diff) | |
distinguish between no controller and no bluez service
The initialization sequence for dbus services is not
fixed, and some races have been observed between
blutoothd and agl-service-bluetooth when running on
qemu: sometimes Bluetooth-Manager can be ready before
org.bluez and this results in reporting no adapter,
even though it's not accurate.
Also, although this issue has been seen only using qemu,
the race is there and it could also manifest in
other platforms with a bluetooth controller attached.
This patch simply provides the logic to discern between
'no org.bluez service found' and 'no bluetooth
controller present':
- in the case of no org.bluez
service detected, an error is returned to allow for
retries,
- in the case of no controller present, no error is
returned and agl-service-bluetooth completes the
initialization.
Bug-AGL: SPEC-3301
Signed-off-by: Raquel Medina <raquel.medina@konsulko.com>
Change-Id: I4868803bcfbd36fb65028cea5c997c4f174675a0
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions