| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/ll/edtt/tests_scripts/ |
| D | hci.llcp.test_list | 4 HCI/CCO/BV-07-C
5 HCI/CCO/BV-09-C # [Handling LE Set Data Length Command]
6 HCI/CCO/BV-10-C
7 HCI/CCO/BV-11-C
8 HCI/CCO/BV-12-C
9 HCI/CCO/BV-13-C
10 HCI/CCO/BV-14-C
11 HCI/CCO/BV-15-C
12 HCI/CCO/BV-18-C
13 HCI/CFC/BV-02-C
[all …]
|
| /Zephyr-Core-3.6.0/drivers/bluetooth/hci/ |
| D | Kconfig | 6 comment "Bluetooth HCI Driver Options"
15 prompt "Bluetooth HCI driver"
29 Bluetooth three-wire (H:5) UART driver. Implementation of HCI
35 bool "[REMOVED] HCI using RPMsg"
40 bool "HCI using the IPC subsystem"
45 Bluetooth HCI driver for communication with another CPU
49 bool "SPI HCI"
53 HCI packets are sent and received as single Byte transfers,
59 bool "IPM HCI"
66 bool "STM32WBA HCI driver"
[all …]
|
| D | userchan.c | 1 /* userchan.c - HCI User Channel based Bluetooth driver */
32 #include <zephyr/bluetooth/hci.h>
99 * @brief Decode the length of an HCI H4 packet
101 * @param buf Pointer to a HCI packet buffer
102 * @return Length of the HCI packet in bytes, zero if no valid packet found.
210 LOG_ERR("HCI Packet type is invalid, length could not be decoded"); in rx_thread()
215 LOG_ERR("Decoded HCI packet length (%d bytes) is greater " in rx_thread()
338 LOG_DBG("hci%d", bt_dev_index); in uc_open()
340 LOG_DBG("hci %s:%d", ip_addr, port); in uc_open()
363 .name = "HCI User Channel",
[all …]
|
| D | CMakeLists.txt | 10 dt_chosen(chosen_hci_rpmsg PROPERTY "zephyr,bt-hci-rpmsg-ipc")
12 message(FATAL_ERROR "zephyr,bt-hci-rpmsg-ipc has been renamed to zephyr,bt-hci-ipc")
|
| /Zephyr-Core-3.6.0/dts/bindings/bluetooth/ |
| D | infineon,cyw43xxx-bt-hci.yaml | 16 /* HCI-UART pins*/
21 bt-hci {
23 compatible = "infineon,cyw43xxx-bt-hci";
33 NOTE2: Use fw-download-speed and hci-operation-speed properties to configure UART
34 speeds for firmware download (fw-download-speed) and HCI operation
35 (hci-operation-speed).
36 If hci-operation-speed or fw-download-speed are not defined in bt-hci node,
42 compatible: "infineon,cyw43xxx-bt-hci"
65 hci-operation-speed:
68 HCI UART boudrate for feature operation. If not defined
[all …]
|
| D | zephyr,bt-hci-spi-slave.yaml | 6 Zephyr's Bluetooth Host Controller Interface SPI (HCI SPI) driver.
11 bt-hci@0 {
12 compatible = "zephyr,bt-hci-spi-slave";
18 The bt-hci@0 node configures an HCI SPI slave on SPI slave
25 compatible: "zephyr,bt-hci-spi-slave"
|
| /Zephyr-Core-3.6.0/include/zephyr/drivers/bluetooth/ |
| D | hci_driver.h | 2 * @brief Bluetooth HCI driver API.
14 * @brief HCI drivers
15 * @defgroup bt_hci_driver HCI drivers
42 /* @brief The HCI event shall be given to bt_recv_prio */
44 /* @brief The HCI event shall be given to bt_recv. */
47 /** @brief Get HCI event flags.
49 * Helper for the HCI driver to get HCI event flags that describes rules that.
56 * @param evt HCI event code.
58 * @return HCI event flags for the specified event.
82 * @brief Receive data from the controller/HCI driver.
[all …]
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/common/ |
| D | Kconfig | 16 Controller. This value does not include the HCI ACL header.
26 The Controller will return this value in the HCI LE Read Buffer
47 The Controller will return this value in the HCI LE Read Buffer Size
62 the Host. This value does not include the HCI ACL header.
113 int "Maximum supported HCI Event buffer length"
119 Maximum supported HCI event buffer size. This value does not include
120 the HCI Event header.
122 sizes that include HCI events. It should be set according to the
123 expected HCI events that can be generated from the configuration.
124 If the subset of possible HCI events is unknown, this should be set to
[all …]
|
| /Zephyr-Core-3.6.0/subsys/usb/device_next/class/ |
| D | Kconfig.bt | 5 bool "Bluetooth HCI USB Transport Layer"
9 Bluetooth HCI USB Transport Layer
17 Bluetooth HCI USB Transport Layer TX thread priority.
23 Bluetooth HCI USB Transport Layer TX thread stack size.
29 Bluetooth HCI USB Transport Layer RX thread priority.
32 module-str = usbd bt hci
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/controller/ |
| D | Kconfig.dtm | 15 bool "Direct Test Mode over HCI"
19 Enable support for Direct Test Mode over the HCI transport.
24 bool "HCI LE Receiver Test v3"
30 bool "HCI LE Transmitter Test v3"
36 bool "HCI LE Transmitter Test v4"
42 bool "Connectionless IQ report HCI event [EXPERIMENTAL]"
46 Enable generation of the HCI LE Connectionless IQ Report event
|
| /Zephyr-Core-3.6.0/include/zephyr/bluetooth/ |
| D | buf.h | 24 #include <zephyr/bluetooth/hci.h>
33 /** HCI command */
35 /** HCI event */
60 /** Helper to include reserved HCI data in buffer calculations */
63 /** Helper to calculate needed buffer size for HCI ACL packets */
66 /** Helper to calculate needed buffer size for HCI Event packets. */
69 /** Helper to calculate needed buffer size for HCI Command packets. */
72 /** Helper to calculate needed buffer size for HCI ISO packets. */
77 /** Data size needed for HCI ACL RX buffers */
80 /** Data size needed for HCI Event RX buffers */
[all …]
|
| D | hci.h | 1 /* hci.h - Bluetooth Host Control Interface definitions */
23 /** Allocate a HCI command buffer.
25 * This function allocates a new buffer for a HCI command. It is given
37 /** Send a HCI command asynchronously.
39 * This function is used for sending a HCI command asynchronously. It can
56 /** Send a HCI command synchronously.
58 * This function is used for sending a HCI command synchronously. It can
103 * the HCI Read Local Version Information command.
114 * @brief Callback type for vendor handling of HCI Vendor-Specific Events.
117 * and will be called for any HCI Vendor-Specific Event.
[all …]
|
| D | hci_raw.h | 2 * @brief Bluetooth HCI RAW channel handling
14 * @brief HCI RAW channel
15 * @defgroup hci_raw HCI RAW channel
100 * @return HCI Status code or BT_HCI_ERR_EXT_HANDLED if command has
120 * Enable Bluetooth RAW HCI channel.
122 * @param rx_queue netbuf queue where HCI packets received from the Bluetooth
|
| /Zephyr-Core-3.6.0/samples/bluetooth/hci_spi/ |
| D | README.rst | 1 .. _bluetooth-hci-spi-sample:
3 Bluetooth: HCI SPI
10 the Zephyr SPI HCI transport protocol (similar to BlueNRG).
21 for the HCI SPI slave device with compatible
22 :dtcompatible:`zephyr,bt-hci-spi-slave`. This node sets an interrupt line to
33 You will also need a separate chip acting as BT HCI SPI master. This
34 application is compatible with the HCI SPI master driver provided by
35 Zephyr's Bluetooth HCI driver core; see the help associated with the
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/ |
| D | Kconfig | 25 bool "HCI-based"
27 HCI-based stack with optional host & controller parts and an
28 HCI driver in between.
33 Select a custom, non-HCI based stack. If you're not sure what
34 this is, you probably want the HCI-based stack instead.
46 bool "RAW HCI access"
49 from the application with the RAW HCI protocol.
52 bool "RAW HCI H:4 transport"
54 This option enables HCI RAW access to work over an H:4
58 bool "RAW HCI H:4 transport enable"
[all …]
|
| /Zephyr-Core-3.6.0/drivers/bluetooth/ |
| D | Kconfig | 10 # Controller support is an HCI driver in itself, so these HCI driver
20 source "drivers/bluetooth/hci/Kconfig"
24 # Insert here any custom (non-HCI) offload drives
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/ |
| D | hci_raw.rst | 4 HCI RAW channel
10 HCI RAW channel API is intended to expose HCI interface to the remote entity.
13 are sent and received by the Bluetooth HCI driver.
|
| /Zephyr-Core-3.6.0/drivers/entropy/ |
| D | Kconfig.bt_hci | 6 bool "Bluetooth HCI RNG driver"
12 Enable Random Number Generator from a Bluetooth HCI device.
14 # Don't use use Bluetooth HCI as a random source since it will be slow.
|
| /Zephyr-Core-3.6.0/samples/bluetooth/hci_uart_async/ |
| D | sample.yaml | 2 name: Bluetooth HCI UART Async
4 This sample is a batteries-included example of a Bluetooth HCI UART
7 It demonstrates a possible implementation of an HCI UART (H4)
|
| D | README.rst | 1 .. _bluetooth-hci-uart-async-sample:
3 Bluetooth: HCI UART based on ASYNC UART
6 Expose a Zephyr Bluetooth Controller over a standard Bluetooth HCI UART interface.
8 This sample performs the same basic function as the HCI UART sample, but it uses the UART_ASYNC_API
10 of the HCI UART sample may be different.
53 .. _bluetooth-hci-uart-async-qemu-posix:
58 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
82 .. _bluetooth-hci-uart-async-bluez:
87 In order to use the HCI UART controller with BlueZ you will need to attach it
126 keep the console logs, we can keep console on uart0 and the HCI on uart1 like
|
| /Zephyr-Core-3.6.0/samples/bluetooth/hci_ipc/ |
| D | CMakeLists.txt | 11 dt_chosen(chosen_hci_rpmsg PROPERTY "zephyr,bt-hci-rpmsg-ipc")
13 message(FATAL_ERROR "zephyr,bt-hci-rpmsg-ipc has been renamed to zephyr,bt-hci-ipc")
|
| D | README.rst | 1 .. _bluetooth-hci-ipc-sample:
3 Bluetooth: HCI IPC
30 HCI IPC peer.
31 This sample is compatible with the HCI IPC driver provided by
|
| /Zephyr-Core-3.6.0/boards/arm/cy8cproto_062_4343w/ |
| D | cy8cproto_062_4343w.dts | 54 /* HCI-UART pins */
58 bt-hci {
60 compatible = "infineon,cyw43xxx-bt-hci";
64 * HCI operation (hci-operation-speed).
65 * If hci-operation-speed or fw-download-speed are not defined in bt-hci{...}
|
| /Zephyr-Core-3.6.0/tests/bluetooth/hci_uart_async/src/ |
| D | test_hci_uart_async.c | 157 * the HCI messages, other than the HCI type/endpoint and the in ZTEST()
158 * size. This allows the test to cheat and skip the HCI Reset, in ZTEST()
169 /* At this point, the HCI flow control limit for the cmd in ZTEST()
171 * controller mock has sent a 'HCI Command Complete' event. in ZTEST()
173 * But the 'HCI Host Number of Completed Packets' command is in ZTEST()
174 * exempt from HCI flow control. (It's like it has its own in ZTEST()
177 * We now send several 'HCI Host Number of Completed Packets' in ZTEST()
207 /* The controller sends a HCI Command Complete response. */ in ZTEST()
220 /* Expect all the 'HCI Host Number of Completed Packets'. */ in ZTEST()
222 /* The mock controller processes a 'HCI Host Number of Completed Packets'. */ in ZTEST()
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/ |
| D | bluetooth-arch.rst | 39 .. _bluetooth-hci:
46 (HCI) protocol. HCI can be implemented over a range of different physical
49 the format for user and protocol data that needs to go over the air. The HCI
67 Bluetooth specification does not specify how HCI is implemented in this
68 single-chip configuration and so how HCI commands, events, and data flows between
76 Hosts when using the Zephyr OS as a Controller. Since HCI ensures
98 depending on the physical transport chosen for HCI:
100 * :ref:`hci_uart <bluetooth-hci-uart-sample>`
101 * :ref:`hci_usb <bluetooth-hci-usb-sample>`
102 * :ref:`hci_spi <bluetooth-hci-spi-sample>`
[all …]
|
