There is no reason why the capabilities should be modified by the stack after registration, nor any reason why a the unicast client application needs to modify the reported remote capabilities, so all have been marked as const. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| boards | ||
| src | ||
| CMakeLists.txt | ||
| Kconfig | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _bluetooth_tmap_bmr: Bluetooth: TMAP BMR ################### Overview ******** Application demonstrating the LE Audio TMAP Broadcast Media Receiver functionality. Implements the BMR role. Requirements ************ * A board with Bluetooth Low Energy 5.2 support Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/tmap_bmr` in the Zephyr tree. See :ref:`bluetooth samples section <bluetooth-samples>` for details.