Lines Matching full:host
15 for portions of the BR/EDR Host. Throughout this architecture document we
26 * **Host**: This layer sits right below the application, and is comprised of
41 Host Controller Interface
44 The `Bluetooth Specification`_ describes the format in which a Host must
45 communicate with a Controller. This is called the Host Controller Interface
47 transports like UART, SPI, or USB. This protocol defines the commands that a Host
50 ensures that different Host and Controller implementations can communicate
60 it possible to implement the Host and Controller on different platforms. The two
65 system-on-chip (SoC) implementation. In this case the BLE Host and the BLE
73 one running the Application and the Host, and a second one with the Controller
77 interoperability among Host and Controller implementations, including of course
78 Zephyr's very own BLE Host and Controller, users of the Zephyr Controller can
79 choose to use whatever Host running on any platform they prefer. For example,
80 the host can be the Linux BLE Host stack (BlueZ) running on any processor
81 capable of supporting Linux. The Host processor may of course also run Zephyr
82 and the Zephyr OS BLE Host. Conversely, combining an IC running the Zephyr
83 Host with an external Controller that does not run Zephyr is also supported.
116 * **Host-only build**: A Zephyr OS Host build will contain the Application and
117 the BLE Host, along with an HCI driver (UART or SPI) to interface with an
130 used for Controller-only builds can be built as Host-only
132 * **Combined build**: This includes the Application, the Host and the
146 combined build (a build that includes both a BLE Host and a Controller in the
155 When using connectivity or dual-chip configurations, several Host and Controller
162 Host-only and Controller-only builds on dual-chip configurations
164 When using a Zephyr Host (left side of image), two instances of Zephyr OS
166 must be programmed into each of the chips respectively. The Host build image
167 contains the application, the BLE Host and the selected HCI driver (UART or
173 This configuration is not limited to using a Zephyr OS Host, as the right side
175 distributions, most of which include Linux's own BLE Host (BlueZ), to connect it
177 BlueZ as a Host supports multiple Controllers simultaneously for applications
179 same Host stack.
186 ``subsys/bluetooth/host``
187 :ref:`The host stack <bluetooth_le_host>`. This is where the HCI command and