OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity

doc: migration-guide-3.7: Add information about new HCI API 

Document the changes coming with the new HCI driver API, and provide
information for how to migrate existing drivers.

Signed-off-by: Johan Hedberg <johan.hedberg@silabs.com>
This commit is contained in:
Johan Hedberg 2024-06-07 10:33:42 +03:00 committed by Anas Nashif
parent 0b8e56120c
commit 4b8aa82801
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/releases/migration-guide-3.7.rst
View File

@ -236,6 +236,17 @@ Analog-to-Digital Converter (ADC)
Bluetooth HCI
=============
* A new HCI driver API was introduced (:github:`72323`) and the old one deprecated. The new API
follows the normal Zephyr driver model, with devicetree nodes, etc. The host now
selects which driver instance to use as the controller by looking for a ``zephyr,bt-hci``
chosen property. The devicetree bindings for all HCI drivers derive from a common
``bt-hci.yaml`` base binding.
* As part of the new HCI driver API, the ``zephyr,bt-uart`` chosen property is no longer used,
rather the UART HCI drivers select their UART by looking for the parent devicetree node of the
HCI driver instance node.
* As part of the new HCI driver API, the ``zephyr,bt-hci-ipc`` chosen property is only used for
the controller side, whereas the HCI driver now relies on nodes with the compatible string
``zephyr,bt-hci-ipc``.
* The ``BT_HCI_VS_EXT`` Kconfig option was deleted and the feature is now included in the
:kconfig:option:`BT_HCI_VS` Kconfig option.
* The ``BT_HCI_VS_EVT`` Kconfig option was removed, since vendor event support is implicit if