Help¶

Supports Bluetooth ICs using SPI as the communication protocol. HCI packets are sent and received as single Byte transfers, prepended after a known header. Headers may vary per device, so additional platform specific knowledge may need to be added as devices are.

Direct dependencies¶

SPI && <choice BT_HCI_BUS_TYPE: Bluetooth HCI driver>

(Includes any dependencies from if’s and menus.)

Symbols selected by this symbol¶

BT_RECV_IS_RX_THREAD if SPI && <choice BT_HCI_BUS_TYPE: Bluetooth HCI driver>

Kconfig definition¶

At drivers/bluetooth/hci/Kconfig:36

Included via Kconfig:10 → Kconfig.zephyr:29 → drivers/Kconfig:12 → drivers/bluetooth/Kconfig:20

Menu path: (top menu) → Device Drivers → Bluetooth Drivers → Bluetooth HCI driver

config BT_SPI
    bool
    prompt "SPI HCI" if SPI && <choice BT_HCI_BUS_TYPE: Bluetooth HCI driver>
    select BT_RECV_IS_RX_THREAD if SPI && <choice BT_HCI_BUS_TYPE: Bluetooth HCI driver>
    depends on SPI && <choice BT_HCI_BUS_TYPE: Bluetooth HCI driver>
    help
      Supports Bluetooth ICs using SPI as the communication protocol.
      HCI packets are sent and received as single Byte transfers,
      prepended after a known header.  Headers may vary per device, so
      additional platform specific knowledge may need to be added as
      devices are.

(Definitions include propagated dependencies, including from if’s and menus.)