Commit 4b8aa828 authored by Johan Hedberg's avatar Johan Hedberg Committed by Anas Nashif
Browse files

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: default avatarJohan Hedberg <johan.hedberg@silabs.com>
parent 0b8e5612

doc/releases/migration-guide-3.7.rst

+11 −0
Changes for doc/releases/migration-guide-3.7.rst: 11 added lines, 0 removed lines.
Original line number Diff line number Diff line
@@ -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

CRA Git | Maintained and supported by SUSTech CRA and CCSE