d590bcb5e0
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> |
||
---|---|---|
.. | ||
dts/arm/nordic | ||
src | ||
CMakeLists.txt | ||
debug_overlay.conf | ||
nrf5340_cpunet_bis-bt_ll_sw_split.conf | ||
nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf | ||
nrf5340_cpunet_cis-bt_ll_sw_split.conf | ||
nrf5340_cpunet_df-bt_ll_sw_split.conf | ||
nrf5340_cpunet_df-bt_ll_sw_split.overlay | ||
nrf5340_cpunet_iso-bt_ll_sw_split.conf | ||
nrf5340_cpunet_iso_broadcast-bt_ll_sw_split.conf | ||
nrf5340_cpunet_iso_central-bt_ll_sw_split.conf | ||
nrf5340_cpunet_iso_peripheral-bt_ll_sw_split.conf | ||
nrf5340_cpunet_iso_receive-bt_ll_sw_split.conf | ||
prj.conf | ||
README.rst | ||
sample.yaml |
.. _bluetooth-hci-ipc-sample: Bluetooth: HCI IPC ################## Overview ******** This sample exposes :ref:`bluetooth_controller` support to another device or CPU using IPC subsystem. Requirements ************ * A board with IPC subsystem and Bluetooth LE support Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/hci_ipc` in the Zephyr tree. To use this application, you need a board with a Bluetooth controller and IPC support. You can then build this application and flash it onto your board in the usual way. See :ref:`boards` for board-specific building and programming information. To test this sample, you need a separate device/CPU that acts as Bluetooth HCI IPC peer. This sample is compatible with the HCI IPC driver provided by Zephyr's Bluetooth :ref:`bt_hci_drivers` core. See the :kconfig:option:`CONFIG_BT_HCI_IPC` configuration option for more information. You might need to adjust the Kconfig configuration of this sample to make it compatible with the peer application. For example, :kconfig:option:`CONFIG_BT_MAX_CONN` must be equal to the maximum number of connections supported by the peer application. Refer to :ref:`bluetooth-samples` for general information about Bluetooth samples.