Release the adapter to BlueZ on HCI User Channel close - #1
Open
AloisKlingler wants to merge 1 commit into
Open
Conversation
Closing the HCI User Channel leaves the controller down and invisible to BlueZ over D-Bus, so no other BlueZ client can use the adapter until the process that opened the channel exits. Store the device id on the Socket and issue an HCIDEVUP ioctl in Close() so BlueZ re-acquires the adapter as soon as the channel is released.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the HCI User Channel socket is closed, the controller is left down and disappears from BlueZ (D-Bus /
btmgmtshows no controller), so other BlueZ clients cannot use the adapter until the owning process exits.This stores the device
idon theSocketand issues anHCIDEVUPioctl inClose()on a fresh raw HCI socket, so BlueZ re-acquires the adapter immediately when the channel is released. Mirrors the existing HCIDEVUP already done inopen().This makes it possible for TeslaBleHttpProxy to share a single adapter with other BlueZ-based tools between command sessions (context: wimaha/TeslaBleHttpProxy#158).