michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Bluetooth: Remove BT_HCI_RESERVE and BT_HCI_RAW_RESERVE

Browse source 
In most cases these were defined as 1. Saving one byte for the rest
doesn't really justify the added complexity that comes with these
options. Removing them also simplifies the interface between HCI
transports/drivers and the host stack, which in turn helps pave the way
for having HCI as a proper Zephyr driver API.

Fixes #71907

Signed-off-by: Johan Hedberg <johan.hedberg@gmail.com>
This commit is contained in:
Johan Hedberg 2024-04-25 09:50:10 +03:00 • committed by Carles Cufí
commit d590bcb5e0
20 changed files with 5 additions and 51 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/releases/migration-guide-3.6.rst
View file

@ -476,6 +476,9 @@ Bluetooth
* `BT_ISO_TIMESTAMP_NONE` has been removed and the `ts` parameter of :c:func:`bt_iso_chan_send` has
as well. :c:func:`bt_iso_chan_send` now always sends without timestamp. To send with a timestamp,
:c:func:`bt_iso_chan_send_ts` can be used.
* The ``CONFIG_BT_HCI_RESERVE`` and ``CONFIG_BT_HCI_RAW_RESERVE`` Kconfig options were removed. All
buffers get by default one byte of headroom now, which HCI transport implementations can rely on
(whether they need it or not).
Bluetooth Mesh
==============