michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/drivers/bluetooth/hci/Kconfig

90 lines
2.2 KiB
Text
Raw Normal View History

Bluetooth: drivers/Kconfig: Fix inconsistency issues Fix issues with tab vs space as well as missing license/copyright header in hci/Kconfig. Change-Id: Id766308dc8eda2d598ea749e5e0d2166014db929 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 20:30:52 +03:00
# Kconfig - Bluetooth drivers configuration options
#
# Copyright (c) 2016 Intel Corporation
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-18 17:01:01 -08:00
# SPDX-License-Identifier: Apache-2.0
Bluetooth: drivers/Kconfig: Fix inconsistency issues Fix issues with tab vs space as well as missing license/copyright header in hci/Kconfig. Change-Id: Id766308dc8eda2d598ea749e5e0d2166014db929 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 20:30:52 +03:00
#
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
comment "Bluetooth HCI Driver Options"
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_UART
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
bool
drivers/bluetooth/hci: Name the choice of BT HCI driver bus Name the choice of BT HCI driver bus in order to config it in the board's Kconfig.defconfig file. Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-05-15 12:55:50 +03:00
choice BT_HCI_BUS_TYPE
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
prompt "Bluetooth HCI driver"
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_H4
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
bool "H:4 UART"
select UART_INTERRUPT_DRIVEN
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
select BT_UART
select BT_RECV_IS_RX_THREAD
Bluetooth: Use depends on SERIAL instead of selects This suppresses warnings for platforms where SERIAL can't be provided. All the platforms that these drivers are interesting for already default to SERIAL=y. Change-Id: Id692f99e018009b30903db8a2c046a6086be01c2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-08 14:25:36 +02:00
depends on SERIAL
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
help
Bluetooth H:4 UART driver. Requires hardware flow control
lines to be available.
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_H5
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
bool "H:5 UART [EXPERIMENTAL]"
select UART_INTERRUPT_DRIVEN
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
select BT_UART
Bluetooth: Use depends on SERIAL instead of selects This suppresses warnings for platforms where SERIAL can't be provided. All the platforms that these drivers are interesting for already default to SERIAL=y. Change-Id: Id692f99e018009b30903db8a2c046a6086be01c2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-08 14:25:36 +02:00
depends on SERIAL
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
help
Bluetooth three-wire (H:5) UART driver. Implementation of HCI
Three-Wire UART Transport Layer.
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_SPI
Bluetooth: Add HCI SPI driver This driver acts as a pass-through, taking raw HCI data, converting it to SPI comms and vice versa. It works in the same way as the existing H:4 and H:5 drivers, only it uses SPI instead of UART. In this first release, the only BLE board which has been tested is the X-NUCLEO-IDB05A1: http://www.st.com/en/ecosystems/x-nucleo-idb05a1.html Although the current supported SPI format works like the one below, it should be trivial to adapt it to support other chips with a different format. SANITY CHECK = 0x02 SPI WRITE = 0x0A SPI READ = 0x0B Tx Format: [HOST] {SPI WRITE} 0x00 0x00 0x00 0x00 {HCI MESSAGE ...} [CHIP] {SANITY CHECK} {FLASH SIZE} 0x00 0x00 0x00 {0xFF * MESSAGE LEN} Rx Format: {IRQ LINE GOES HIGH} [HOST] {SPI READ} 0x00 0x00 0x00 0x00 {0xFF * BYTES TO READ} [CHIP] 0x02 {FLASH SIZE} 0x00 {BYTES TO READ} 0x00 {HCI MESSAGE ...} Change-Id: I4a00711c922d9ea02c5e2afb0d16715e413b1ed5 Signed-off-by: Lee Jones <lee.jones@linaro.org>
2017-01-09 14:16:07 +00:00
bool "SPI HCI"
Bluetooth: hci: spi: Select BT_RECV_IS_RX_THREAD SPI driver has its own rx thread, select BT_RECV_IS_RX_THREAD. This fixes build issue because of undefined CONFIG_BT_RX_PRIO. Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
2018-05-29 12:44:35 +02:00
select BT_RECV_IS_RX_THREAD
bluetooth: hci: Kconfig: Fix dependency This patch changes the BLUETOOTH_SPI to depend on SPI. Signed-off-by: Andy Gross <andy.gross@linaro.org>
2017-06-06 21:26:14 -05:00
depends on SPI
Bluetooth: Add HCI SPI driver This driver acts as a pass-through, taking raw HCI data, converting it to SPI comms and vice versa. It works in the same way as the existing H:4 and H:5 drivers, only it uses SPI instead of UART. In this first release, the only BLE board which has been tested is the X-NUCLEO-IDB05A1: http://www.st.com/en/ecosystems/x-nucleo-idb05a1.html Although the current supported SPI format works like the one below, it should be trivial to adapt it to support other chips with a different format. SANITY CHECK = 0x02 SPI WRITE = 0x0A SPI READ = 0x0B Tx Format: [HOST] {SPI WRITE} 0x00 0x00 0x00 0x00 {HCI MESSAGE ...} [CHIP] {SANITY CHECK} {FLASH SIZE} 0x00 0x00 0x00 {0xFF * MESSAGE LEN} Rx Format: {IRQ LINE GOES HIGH} [HOST] {SPI READ} 0x00 0x00 0x00 0x00 {0xFF * BYTES TO READ} [CHIP] 0x02 {FLASH SIZE} 0x00 {BYTES TO READ} 0x00 {HCI MESSAGE ...} Change-Id: I4a00711c922d9ea02c5e2afb0d16715e413b1ed5 Signed-off-by: Lee Jones <lee.jones@linaro.org>
2017-01-09 14:16:07 +00:00
help
Supports Bluetooth ICs using SPI as the communication protocol.
spell: fix Kconfig help typos: /boards /drivers Fix misspellings in Kconfig help text Change-Id: I3ae28a5d23d8e266612114bc0eb8a6e158129dc7 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-04-21 10:29:51 -07:00
HCI packets are sent and received as single Byte transfers,
Bluetooth: Add HCI SPI driver This driver acts as a pass-through, taking raw HCI data, converting it to SPI comms and vice versa. It works in the same way as the existing H:4 and H:5 drivers, only it uses SPI instead of UART. In this first release, the only BLE board which has been tested is the X-NUCLEO-IDB05A1: http://www.st.com/en/ecosystems/x-nucleo-idb05a1.html Although the current supported SPI format works like the one below, it should be trivial to adapt it to support other chips with a different format. SANITY CHECK = 0x02 SPI WRITE = 0x0A SPI READ = 0x0B Tx Format: [HOST] {SPI WRITE} 0x00 0x00 0x00 0x00 {HCI MESSAGE ...} [CHIP] {SANITY CHECK} {FLASH SIZE} 0x00 0x00 0x00 {0xFF * MESSAGE LEN} Rx Format: {IRQ LINE GOES HIGH} [HOST] {SPI READ} 0x00 0x00 0x00 0x00 {0xFF * BYTES TO READ} [CHIP] 0x02 {FLASH SIZE} 0x00 {BYTES TO READ} 0x00 {HCI MESSAGE ...} Change-Id: I4a00711c922d9ea02c5e2afb0d16715e413b1ed5 Signed-off-by: Lee Jones <lee.jones@linaro.org>
2017-01-09 14:16:07 +00:00
prepended after a known header. Headers may vary per device, so
spell: fix Kconfig help typos: /boards /drivers Fix misspellings in Kconfig help text Change-Id: I3ae28a5d23d8e266612114bc0eb8a6e158129dc7 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-04-21 10:29:51 -07:00
additional platform specific knowledge may need to be added as
Bluetooth: SPI: introduce CONFIG_BLUETOOTH_SPI_BLUENRG This new option is used to encapsulate the logic specific to devices implementing the BlueNRG Bluetooth stack (e.g. X-NUCLEO-IDB05A1). The current BlueNRG specific logic covers the HCI Reset handling and the manual control of the SPI Chip Select line (normally not needed since spi_transceive is also responsible for controlling the SPI CS line). Change-Id: I5db4addf873eee0af2d957e2181c50aac53ab656 Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
2017-01-25 22:24:45 -02:00
devices are.
Bluetooth: Add HCI SPI driver This driver acts as a pass-through, taking raw HCI data, converting it to SPI comms and vice versa. It works in the same way as the existing H:4 and H:5 drivers, only it uses SPI instead of UART. In this first release, the only BLE board which has been tested is the X-NUCLEO-IDB05A1: http://www.st.com/en/ecosystems/x-nucleo-idb05a1.html Although the current supported SPI format works like the one below, it should be trivial to adapt it to support other chips with a different format. SANITY CHECK = 0x02 SPI WRITE = 0x0A SPI READ = 0x0B Tx Format: [HOST] {SPI WRITE} 0x00 0x00 0x00 0x00 {HCI MESSAGE ...} [CHIP] {SANITY CHECK} {FLASH SIZE} 0x00 0x00 0x00 {0xFF * MESSAGE LEN} Rx Format: {IRQ LINE GOES HIGH} [HOST] {SPI READ} 0x00 0x00 0x00 0x00 {0xFF * BYTES TO READ} [CHIP] 0x02 {FLASH SIZE} 0x00 {BYTES TO READ} 0x00 {HCI MESSAGE ...} Change-Id: I4a00711c922d9ea02c5e2afb0d16715e413b1ed5 Signed-off-by: Lee Jones <lee.jones@linaro.org>
2017-01-09 14:16:07 +00:00
Bluetooth: Add HCI User Channel driver for native POSIX port Introduce a custom HCI driver for the native POSIX port, which opens a HCI User Channel socket to the Linux kernel to gain access to a local Bluetooth controller. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-05-25 13:32:34 +03:00
config BT_USERCHAN
bool "HCI User Channel based driver"
depends on BOARD_NATIVE_POSIX
help
This driver provides access to the local Linux host's Bluetooth
adapter using a User Channel HCI socket to the Linux kernel. It
is only intended to be used with the native POSIX build of Zephyr.
The Bluetooth adapter must be powered off in order for Zephyr to
be able to use it.
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_NO_DRIVER
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
bool "No default HCI driver"
help
This is intended for unit tests where no internal driver
should be selected.
endchoice
devicetree: Generate BLUETOOTH_UART,UART_PIPE etc config from dt patch uses chosen property zephyr,bt-uart, zephyr,uart-pipe and zephyr,bt-mon-uart to determine the uart instance to be used for bluetooth,uart_pipe and bluetooth_monitor and generate appropriate configs. Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
2017-07-12 19:52:00 +05:30
if !HAS_DTS
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_UART_ON_DEV_NAME
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
string "Device Name of UART Device for Bluetooth"
default "UART_0"
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
depends on BT_UART
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
help
This option specifies the name of UART device to be used
for Bluetooth.
devicetree: Generate BLUETOOTH_UART,UART_PIPE etc config from dt patch uses chosen property zephyr,bt-uart, zephyr,uart-pipe and zephyr,bt-mon-uart to determine the uart instance to be used for bluetooth,uart_pipe and bluetooth_monitor and generate appropriate configs. Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
2017-07-12 19:52:00 +05:30
endif
Bluetooth: Rename bt_driver to bt_hci_driver The bt_driver API was created when Zephyr only had a Bluetooth host stack, but no controller-side functionality. The only "driver" that was needed for the host was the HCI driver, and hence "HCI" was omitted from the name. With support both for host and controller Zephyr will be getting more Bluetooth driver types, in particular radio drivers. To prepare for this, move all HCI drivers to drivers/bluetooth/hci/ and rename the bt_driver API bt_hci_driver. Change-Id: I82829da80aa61f26c2bb2005380f1e88d069ac7d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-27 16:55:01 +03:00
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
if BT_SPI
Bluetooth: Add HCI SPI driver This driver acts as a pass-through, taking raw HCI data, converting it to SPI comms and vice versa. It works in the same way as the existing H:4 and H:5 drivers, only it uses SPI instead of UART. In this first release, the only BLE board which has been tested is the X-NUCLEO-IDB05A1: http://www.st.com/en/ecosystems/x-nucleo-idb05a1.html Although the current supported SPI format works like the one below, it should be trivial to adapt it to support other chips with a different format. SANITY CHECK = 0x02 SPI WRITE = 0x0A SPI READ = 0x0B Tx Format: [HOST] {SPI WRITE} 0x00 0x00 0x00 0x00 {HCI MESSAGE ...} [CHIP] {SANITY CHECK} {FLASH SIZE} 0x00 0x00 0x00 {0xFF * MESSAGE LEN} Rx Format: {IRQ LINE GOES HIGH} [HOST] {SPI READ} 0x00 0x00 0x00 0x00 {0xFF * BYTES TO READ} [CHIP] 0x02 {FLASH SIZE} 0x00 {BYTES TO READ} 0x00 {HCI MESSAGE ...} Change-Id: I4a00711c922d9ea02c5e2afb0d16715e413b1ed5 Signed-off-by: Lee Jones <lee.jones@linaro.org>
2017-01-09 14:16:07 +00:00
bt: hci driver over spi: Configure BlueNRG-MS in controller mode Configure BlueNRG in controller w/o host. By disabling 'HCI_reset' via the quirk, we can request to BluesNRG hardware to be on controller mode just after it is ready. By the way it's no necessary to manage a 'HCI_reset' when BluesNRG are initialised (and on controler mode). Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com> Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2018-06-26 12:07:23 +02:00
config BT_BLUENRG_ACI
bool "Enable ACI message with with BlueNRG-based devices"
help
Enable support for devices compatible with the BlueNRG Bluetooth
Stack. Current driver supports: ST BLUENRG-MS.
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
config BT_SPI_BLUENRG
Bluetooth: SPI: introduce CONFIG_BLUETOOTH_SPI_BLUENRG This new option is used to encapsulate the logic specific to devices implementing the BlueNRG Bluetooth stack (e.g. X-NUCLEO-IDB05A1). The current BlueNRG specific logic covers the HCI Reset handling and the manual control of the SPI Chip Select line (normally not needed since spi_transceive is also responsible for controlling the SPI CS line). Change-Id: I5db4addf873eee0af2d957e2181c50aac53ab656 Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
2017-01-25 22:24:45 -02:00
bool "Enable compatibility with BlueNRG-based devices"
help
Enable support for devices compatible with the BlueNRG Bluetooth
bt: hci driver over spi: Configure BlueNRG-MS in controller mode Configure BlueNRG in controller w/o host. By disabling 'HCI_reset' via the quirk, we can request to BluesNRG hardware to be on controller mode just after it is ready. By the way it's no necessary to manage a 'HCI_reset' when BluesNRG are initialised (and on controler mode). Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com> Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2018-06-26 12:07:23 +02:00
Stack. Current driver supports: ST BLUENRG-MS.
Bluetooth: SPI: introduce CONFIG_BLUETOOTH_SPI_BLUENRG This new option is used to encapsulate the logic specific to devices implementing the BlueNRG Bluetooth stack (e.g. X-NUCLEO-IDB05A1). The current BlueNRG specific logic covers the HCI Reset handling and the manual control of the SPI Chip Select line (normally not needed since spi_transceive is also responsible for controlling the SPI CS line). Change-Id: I5db4addf873eee0af2d957e2181c50aac53ab656 Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org>
2017-01-25 22:24:45 -02:00
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 09:21:11 +03:00
endif # BT_SPI
Copy permalink