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 <[email protected]>
zephyrproject-rtos · Jun 11, 2024 · 09114f4 · 09114f4
1 parent fd995f1
commit 09114f4
Showing 1 changed file with 11 additions and 0 deletions.
diff --git a/doc/releases/migration-guide-3.7.rst b/doc/releases/migration-guide-3.7.rst
@@ -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