rust/bt-ascs: Use preferred presentation delay A Preferred QoS request built its Config QoS from the minimum Presentation_Delay the peer supports, and ignored the preferred window the peer publishes in the Codec Configured state. BAP v1.0.2 Section 5.6.2 says the requested delay should fall inside that window. A peer that prefers a longer delay, for example to cover its rendering path, got a value it did not ask for. Request the low end of the preferred window instead. A peer with no preference gets the supported minimum, as before. A new test covers a peer whose preferred minimum is above its supported minimum. Test: cargo test -p bt-ascs Change-Id: Ica419f8279665314be7fd3ec8e980e016a6a6964 Reviewed-on: https://bluetooth-review.googlesource.com/c/bluetooth/+/4124
This is a repository for shared libraries and tools that can be useful for multiple Bluetooth stacks.
These tools and libraries are meant to be:
It has been started as a repository for developing Rust crates but can be easily expanded to include libraries and tools written in other languages.
It is not a full Bluetooth stack. Google has two officially open-source Bluetooth stacks: