Help¶

This option specifies the name of SPI device to be used for Bluetooth. On the controller side, this SPI device is used to encapsulate the RAW HCI frames to send further up the stack. On the BLE stack side, this device is used to reply back with HCI frames that are sent over the air.

Direct dependencies¶

BT_SPI && !HAS_DTS_SPI_DEVICE && BT_HCI && BT && !BT_CTLR

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

Defaults¶

“SPI_0” if BT_SPI && !HAS_DTS_SPI_DEVICE && BT_HCI && BT && !BT_CTLR

Kconfig definition¶

At drivers/bluetooth/hci/Kconfig:75

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

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

config BT_SPI_DEV_NAME
    string
    prompt "Device Name of SPI Device for Bluetooth" if BT_SPI && !HAS_DTS_SPI_DEVICE && BT_HCI && BT && !BT_CTLR
    default "SPI_0" if BT_SPI && !HAS_DTS_SPI_DEVICE && BT_HCI && BT && !BT_CTLR
    depends on BT_SPI && !HAS_DTS_SPI_DEVICE && BT_HCI && BT && !BT_CTLR
    help
      This option specifies the name of SPI device to be used for Bluetooth.
      On the controller side, this SPI device is used to encapsulate the
      RAW HCI frames to send further up the stack. On the BLE stack side,
      this device is used to reply back with HCI frames that are sent over
      the air.

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