Home
last modified time | relevance | path

Searched +full:bt +full:- +full:hci +full:- +full:name (Results 1 – 25 of 129) sorted by relevance

123456

/Zephyr-latest/dts/bindings/bluetooth/
Dzephyr,bt-hci-ipc.yaml1 description: Bluetooth HCI using the IPC subsystem
3 compatible: "zephyr,bt-hci-ipc"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-auto-dle"]
14 bt-hci-ipc-name:
17 description: IPC endpoint name
Dbt-hci.yaml1 # Common fields for Bluetooth HCI devices
6 bt-hci-name:
8 description: Name of the HCI transport
9 bt-hci-bus:
13 - "virtual"
14 - "usb"
15 - "pccard"
16 - "uart"
17 - "rs232"
18 - "pci"
[all …]
Despressif,esp32-bt-hci.yaml1 description: Bluetooth HCI for Espressif ESP32
3 compatible: "espressif,esp32-bt-hci"
5 include: bt-hci.yaml
8 bt-hci-name:
9 default: "BT ESP32"
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-auto-dle"]
Dsilabs,bt-hci-efr32.yaml1 description: Bluetooth HCI on Silabs boards
3 compatible: "silabs,bt-hci-efr32"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-reset"]
Drenesas,bt-hci-da1469x.yaml1 description: Bluetooth HCI for Renesas DA1469x
3 compatible: "renesas,bt-hci-da1469x"
5 include: bt-hci.yaml
8 bt-hci-name:
9 default: "BT DA1469x"
10 bt-hci-bus:
Dzephyr,bt-hci-ll-sw-split.yaml1 description: Bluetooth HCI provided by the native Zephyr Bluetooth Controller
3 compatible: "zephyr,bt-hci-ll-sw-split"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-auto-dle"]
Dzephyr,bt-hci-userchan.yaml1 description: Bluetooth HCI provided by a Linux HCI user channel socket
3 compatible: "zephyr,bt-hci-userchan"
5 include: bt-hci.yaml
8 bt-hci-name:
9 default: "HCI User Channel"
10 bt-hci-bus:
Dst,hci-stm32wb0.yaml1 description: Bluetooth HCI driver for ST STM32WB0 series
3 compatible: "st,hci-stm32wb0"
5 include: bt-hci.yaml
8 bt-hci-name:
9 default: "HCI over RAM"
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-reset"]
Dzephyr,bt-hci-uart.yaml1 # UART Bluetooth HCI device
3 description: Bluetooth HCI behind a UART device (H:4)
5 compatible: "zephyr,bt-hci-uart"
7 include: bt-hci.yaml
10 bt-hci-name:
12 bt-hci-bus:
Dst,hci-stm32wba.yaml1 description: Bluetooth HCI driver for ST STM32WBA
3 compatible: "st,hci-stm32wba"
5 include: bt-hci.yaml
8 bt-hci-name:
9 default: "BT IPM"
10 bt-hci-bus:
Dzephyr,bt-hci-3wire-uart.yaml1 # UART Bluetooth HCI device
3 description: Bluetooth HCI behind a 3-Wire UART device (H:5)
5 compatible: "zephyr,bt-hci-3wire-uart"
7 include: bt-hci.yaml
10 bt-hci-name:
12 bt-hci-bus:
Dnxp,hci-ble.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: NXP BLE HCI information
6 compatible: "nxp,hci-ble"
8 include: bt-hci.yaml
11 bt-hci-name:
12 default: "BT NXP"
13 bt-hci-bus:
Dinfineon,cat1-bless-hci.yaml4 # SPDX-License-Identifier: Apache-2.0
9 compatible: "infineon,cat1-bless-hci"
11 include: bt-hci.yaml
14 bt-hci-name:
16 bt-hci-bus:
18 bt-hci-quirks:
19 default: ["no-reset"]
Dst,stm32wb-ble-rf.yaml2 # SPDX-License-Identifier: Apache-2.0
7 compatible: "st,stm32wb-rf"
9 include: bt-hci.yaml
14 bt-hci-name:
15 default: "BT IPM"
16 bt-hci-bus:
Dinfineon,cyw208xx-hci.yaml4 # SPDX-License-Identifier: Apache-2.0
7 Bluetooth module that uses Infineon CYW208XX HCI bluetooth interface
13 compatible: "infineon,cyw208xx-hci"
15 include: bt-hci.yaml
18 bt-hci-name:
20 bt-hci-bus:
Dambiq,bt-hci-spi.yaml2 # SPDX-License-Identifier: Apache-2.0
8 compatible: "ambiq,bt-hci-spi"
10 include: [spi-device.yaml, bt-hci.yaml]
17 irq-gpios:
18 type: phandle-array
23 reset-gpios:
24 type: phandle-array
28 clkreq-gpios:
29 type: phandle-array
36 bt-hci-name:
[all …]
Dzephyr,bt-hci-spi.yaml1 # Copyright (c) 2018, I-SENSE group of ICCS
2 # SPDX-License-Identifier: Apache-2.0
8 compatible: "zephyr,bt-hci-spi"
10 include: [spi-device.yaml, bt-hci.yaml]
13 irq-gpios:
14 type: phandle-array
17 reset-gpios:
18 type: phandle-array
21 reset-assert-duration-ms:
24 Minimum duration to hold the reset-gpios pin low for.
[all …]
/Zephyr-latest/tests/bluetooth/hci_prop_evt/dts/bindings/
Dzephyr,bt-hci-test.yaml1 description: Bluetooth HCI for test purposes
3 compatible: "zephyr,bt-hci-test"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-reset"]
/Zephyr-latest/tests/bluetooth/host_long_adv_recv/dts/bindings/
Dzephyr,bt-hci-test.yaml1 description: Bluetooth HCI for test purposes
3 compatible: "zephyr,bt-hci-test"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
12 bt-hci-quirks:
13 default: ["no-reset"]
/Zephyr-latest/tests/bluetooth/bluetooth/dts/bindings/
Dzephyr,bt-hci-test.yaml1 description: Bluetooth HCI for test purposes
3 compatible: "zephyr,bt-hci-test"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
/Zephyr-latest/tests/bluetooth/hci_uart_async/dts/bindings/
Dzephyr,bt-hci-test.yaml1 description: Bluetooth HCI for test purposes
3 compatible: "zephyr,bt-hci-test"
5 include: bt-hci.yaml
8 bt-hci-name:
10 bt-hci-bus:
/Zephyr-latest/samples/bluetooth/hci_spi/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_spi
2 :name: HCI SPI
3 :relevant-api: hci_raw bluetooth spi_interface
11 the Zephyr SPI HCI transport protocol (similar to BlueNRG).
21 You then need to ensure that your :ref:`devicetree <dt-guide>` defines a node
22 for the HCI SPI slave device with compatible
23 :dtcompatible:`zephyr,bt-hci-spi-slave`. This node sets an interrupt line to
31 the usual way; see :ref:`boards` for board-specific building and
34 You will also need a separate chip acting as BT HCI SPI master. This
35 application is compatible with the HCI SPI master driver provided by
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart_async/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart_async
2 :name: HCI UART async
3 :relevant-api: hci_raw bluetooth uart_interface
10 Expose Bluetooth Controller support over a standard Bluetooth HCI UART interface.
12 This sample performs the same basic function as the HCI UART sample, but it uses the UART_ASYNC_API
14 of the HCI UART sample may be different.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart_async
57 .. _bluetooth-hci-uart-async-qemu-posix:
62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart_3wire/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart_3wire
2 :name: HCI 3-wire (H:5)
3 :relevant-api: hci_raw bluetooth uart_interface
5 Expose a Bluetooth controller to another device or CPU over H5:HCI transport.
11 using the H:5 HCI transport protocol.
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart_3wire
57 .. _bluetooth-hci-uart-3wire-qemu-posix:
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart
2 :name: HCI UART
3 :relevant-api: hci_raw bluetooth uart_interface
11 using the H:4 HCI transport protocol (requires HW flow control from the UART).
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart
57 .. _bluetooth-hci-uart-qemu-posix:
62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
[all …]

123456