sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
bcb4409756
nuttx/drivers/wireless/bluetooth/Kconfig

61 lines
1.3 KiB
Plaintext
Raw Normal View History

Adds re-architected Bluetooth UART driver from the Intel/Zephyr arduino101_firmware_source-v1.tar package. Squashed commit of the following: drivers/bluetooth: Re-architect Bluetooth UART driver to follow upper/lower half model. Completely untested. drivers/bluetooth: Grr.. Another band-aid commit to stay in sync with master. Why is this so difficult drivers/bluetooth: Band-aid commit to stay in sync with master. Lost it somehow. drivers/wireless/bluetooth: A few changes, mostly thought experiments. drivers/wireless/bluetooth: UART-based Bluetooth driver ported from the Intel/Zephyr arduino101_firmware_source-v1.tar package. This initial commit is the original files in the NuttX build environment with changes to conform with the coding standard. It should not even build.
2018-03-30 02:36:03 +02:00
#
drivers/wireless/bluetooth: Partition bt_uart.c adding bt_uart.h and bt_uart_generic.c. This will now permit adding HCI UART drivers that have custom initialization requirements.. such as parts the need to download a configuration file to the HCI UART before they are usable.
2018-04-20 01:48:04 +02:00
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
Adds re-architected Bluetooth UART driver from the Intel/Zephyr arduino101_firmware_source-v1.tar package. Squashed commit of the following: drivers/bluetooth: Re-architect Bluetooth UART driver to follow upper/lower half model. Completely untested. drivers/bluetooth: Grr.. Another band-aid commit to stay in sync with master. Why is this so difficult drivers/bluetooth: Band-aid commit to stay in sync with master. Lost it somehow. drivers/wireless/bluetooth: A few changes, mostly thought experiments. drivers/wireless/bluetooth: UART-based Bluetooth driver ported from the Intel/Zephyr arduino101_firmware_source-v1.tar package. This initial commit is the original files in the NuttX build environment with changes to conform with the coding standard. It should not even build.
2018-03-30 02:36:03 +02:00
#
if DRIVERS_BLUETOOTH
config BLUETOOTH_UART
bool "Bluetooth UART driver"
default n
drivers/wireless/bluetooth: Default BAUD must be 115200, Fix logic in Rx callback, Rx callback must execute on work queue. Now sends and receives one command and response. But hangs on the next.
2018-04-17 21:07:28 +02:00
select SCHED_HPWORK
Adds re-architected Bluetooth UART driver from the Intel/Zephyr arduino101_firmware_source-v1.tar package. Squashed commit of the following: drivers/bluetooth: Re-architect Bluetooth UART driver to follow upper/lower half model. Completely untested. drivers/bluetooth: Grr.. Another band-aid commit to stay in sync with master. Why is this so difficult drivers/bluetooth: Band-aid commit to stay in sync with master. Lost it somehow. drivers/wireless/bluetooth: A few changes, mostly thought experiments. drivers/wireless/bluetooth: UART-based Bluetooth driver ported from the Intel/Zephyr arduino101_firmware_source-v1.tar package. This initial commit is the original files in the NuttX build environment with changes to conform with the coding standard. It should not even build.
2018-03-30 02:36:03 +02:00
---help---
Enable Bluetooth UART driver.
drivers/wireless/bluetooth: Partition bt_uart.c adding bt_uart.h and bt_uart_generic.c. This will now permit adding HCI UART drivers that have custom initialization requirements.. such as parts the need to download a configuration file to the HCI UART before they are usable.
2018-04-20 01:48:04 +02:00
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
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 15:16:37 +02:00
config BLUETOOTH_UART_SHIM
bool "Generic shim to serial port"
drivers/wireless/bluetooth: Partition bt_uart.c adding bt_uart.h and bt_uart_generic.c. This will now permit adding HCI UART drivers that have custom initialization requirements.. such as parts the need to download a configuration file to the HCI UART before they are usable.
2018-04-20 01:48:04 +02:00
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
drivers/wireless: Add option to dump I/O buffers. Fix calculation of response length.
2018-04-18 20:46:47 +02:00
config BLUETOOTH_UART_DUMP
bool "Dump HCI UART I/O buffers"
default n
drivers/wireless/bluetooth: Partition bt_uart.c adding bt_uart.h and bt_uart_generic.c. This will now permit adding HCI UART drivers that have custom initialization requirements.. such as parts the need to download a configuration file to the HCI UART before they are usable.
2018-04-20 01:48:04 +02:00
depends on DEBUG_WIRELESS_INFO
drivers/wireless: Add option to dump I/O buffers. Fix calculation of response length.
2018-04-18 20:46:47 +02:00
---help---
Dump the full content of all outgoing and incoming messages.
drivers/wireless/bluetooth: Partition bt_uart.c adding bt_uart.h and bt_uart_generic.c. This will now permit adding HCI UART drivers that have custom initialization requirements.. such as parts the need to download a configuration file to the HCI UART before they are usable.
2018-04-20 01:48:04 +02:00
endif # BLUETOOTH_UART
drivers/wireless/bluetooth: Add a NULL device to support some very low level testing on the Simulator.
2018-04-03 17:00:18 +02:00
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.
Adds re-architected Bluetooth UART driver from the Intel/Zephyr arduino101_firmware_source-v1.tar package. Squashed commit of the following: drivers/bluetooth: Re-architect Bluetooth UART driver to follow upper/lower half model. Completely untested. drivers/bluetooth: Grr.. Another band-aid commit to stay in sync with master. Why is this so difficult drivers/bluetooth: Band-aid commit to stay in sync with master. Lost it somehow. drivers/wireless/bluetooth: A few changes, mostly thought experiments. drivers/wireless/bluetooth: UART-based Bluetooth driver ported from the Intel/Zephyr arduino101_firmware_source-v1.tar package. This initial commit is the original files in the NuttX build environment with changes to conform with the coding standard. It should not even build.
2018-03-30 02:36:03 +02:00
endif # DRIVERS_BLUETOOTH
Reference in New Issue Copy Permalink