nuttx/drivers/wireless/bluetooth/Kconfig
Dave Marples 05bbbec3e1 Add support for the BCM43438A1 Bluetooth capability. It also adds a serial 'shim' to allow any regular serial port that can support a Bluetooth H4 interface (i.e. it has RTS/CTS) to be used to drive a Bluetooth device (Get a handle to it via hci_uart_getdevice("/dev/xxx") and then pass it to the btuart_register function.
Most of the bluetooth and wifi chips appear to need external firmware, and the 43438 is no exception. Fortunately, since Cypress got involved, these are much more straightforward to obtain and are shipped as part of their SDK, which is downloadable from their website.  Those firmwares are already provided as C arrays, so their names just need updating to;

const unsigned char bt_firmware_hcd -> The bt firmware array.

const int bt_firmware_len = sizeof(bt_firmware_hcd);
2019-09-21 07:16:37 -06:00

61 lines
1.3 KiB
Plaintext

#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#
if DRIVERS_BLUETOOTH
config BLUETOOTH_UART
bool "Bluetooth UART driver"
default n
select SCHED_HPWORK
---help---
Enable Bluetooth UART driver.
config BLUETOOTH_UART_GENERIC
bool
default n
if BLUETOOTH_UART
choice
prompt "Bluetooth UART HCI device"
default BLUETOOTH_UART_OTHER
config BLUETOOTH_UART_BT860
bool "Laird BT860"
select BLUETOOTH_UART_GENERIC
config BLUETOOTH_UART_SHIM
bool "Generic shim to serial port"
config BLUETOOTH_UART_CC2564
bool "TI CC2564"
depends on EXPERIMENTAL
config BLUETOOTH_UART_OTHER
bool "Other generic HCI UART device"
select BLUETOOTH_UART_GENERIC
endchoice # Bluetooth UART HCI device
config BLUETOOTH_UART_DUMP
bool "Dump HCI UART I/O buffers"
default n
depends on DEBUG_WIRELESS_INFO
---help---
Dump the full content of all outgoing and incoming messages.
endif # BLUETOOTH_UART
config BLUETOOTH_NULL
bool "NULL Bluetooth device"
default n
---help---
A do-nothing Bluetooth device driver to permit some basic testing of
the Bluetooth stack on the simulator. This driver just "closes the
loop" and nothing more: It is a just a bit-bucket for outgoing
packets; it generates no incoming packets.
endif # DRIVERS_BLUETOOTH