michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: migration-guide-3.7: fix rendering of Bluetooth HCI section

Browse source 
some bullet points had incorrect indent causing
the list to render as "definition list"

Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit is contained in:
Benjamin Cabé 2024-07-19 16:46:07 +02:00 • committed by Alberto Escolar
commit 2f8cfc670a
1 changed files with 17 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

34
doc/releases/migration-guide-3.7.rst
View file

@ -288,23 +288,23 @@ Bluetooth 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_NO_DRIVER`` Kconfig option was removed. HCI drivers are no-longer behind a Kconfig
choice, rather they can now be enabled and disabled independently, mostly based on their
respective devicetree node being enabled or not.
* The ``BT_HCI_VS_EXT`` Kconfig option was deleted and the feature is now included in the
:kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option.
* The ``BT_HCI_VS_EVT`` Kconfig option was removed, since vendor event support is implicit if
the :kconfig:option:`CONFIG_BT_HCI_VS` option is enabled.
* The bt_read_static_addr() API was removed. This wasn't really a completely public API, but
since it was exposed by the public hci_driver.h header file the removal is mentioned here.
Enable the :kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option instead, and use vendor specific
HCI commands API to get the Controller's Bluetooth static address when available.
* 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_NO_DRIVER`` Kconfig option was removed. HCI drivers are no-longer behind a Kconfig
choice, rather they can now be enabled and disabled independently, mostly based on their
respective devicetree node being enabled or not.
* The ``BT_HCI_VS_EXT`` Kconfig option was deleted and the feature is now included in the
:kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option.
* The ``BT_HCI_VS_EVT`` Kconfig option was removed, since vendor event support is implicit if
the :kconfig:option:`CONFIG_BT_HCI_VS` option is enabled.
* The bt_read_static_addr() API was removed. This wasn't really a completely public API, but
since it was exposed by the public hci_driver.h header file the removal is mentioned here.
Enable the :kconfig:option:`CONFIG_BT_HCI_VS` Kconfig option instead, and use vendor specific
HCI commands API to get the Controller's Bluetooth static address when available.
Charger
=======