OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/bluetooth/Kconfig

177 lines
4.1 KiB
Plaintext
Raw Normal View History

Bluetooth: Move Bluetooth host stack to subsys Move the Bluetooth host stack from net/bluetooth to subsys/bluetooth/host. This is preparation for having both host and controller under the same root, i.e. subsys/bluetooth/. Change-Id: I3bc796f7e331fca0c485f3890d62b9c03e027b96 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-02 17:06:56 +08:00
# Kconfig - Bluetooth 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-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
Bluetooth: Move Bluetooth host stack to subsys Move the Bluetooth host stack from net/bluetooth to subsys/bluetooth/host. This is preparation for having both host and controller under the same root, i.e. subsys/bluetooth/. Change-Id: I3bc796f7e331fca0c485f3890d62b9c03e027b96 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-02 17:06:56 +08:00
#
Bluetooth: kconfig: Use menu instead of menuconfig To be consistent with other subsystem menu, use menu for Bluetooth support in Kconfig instead of menuconfig which showed up as checkbox. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-13 11:46:59 +08:00
menu "Bluetooth"
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 14:21:11 +08:00
config BT
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 18:23:21 +08:00
bool "Bluetooth support"
select NET_BUF
help
This option enables Bluetooth support.
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 14:21:11 +08:00
if BT
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 18:23:21 +08:00
choice
prompt "Bluetooth Stack Selection"
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 14:21:11 +08:00
default BT_HCI
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 18:23:21 +08:00
help
Select the Bluetooth stack to compile.
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 14:21:11 +08:00
config BT_HCI
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 18:23:21 +08:00
bool "HCI-based"
help
HCI-based stack with optional host & controller parts and an
HCI driver in between.
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 14:21:11 +08:00
config BT_CUSTOM
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 18:23:21 +08:00
bool "Custom"
help
Select a custom, non-HCI based stack. If you're not sure what
this is, you probably want the HCI-based stack instead.
endchoice
kconfig: Change how BT affects SYSTEM_WORKQUEUE_PRIORITY Invalid configurations should be detected during configuration instead of during compilation whenever possible. This patch replaces a BUILD_ASSERT on CONFIG_SYSTEM_WORKQUEUE_PRIORITY with what is intended to be an equivalent Kconfig restriction. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-06-14 15:53:00 +08:00
# The Bluetooth subsystem requires the system workqueue to execute at
# a cooperative priority.
config SYSTEM_WORKQUEUE_PRIORITY
range -256 -1
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 14:21:11 +08:00
if BT_HCI
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08: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 14:21:11 +08:00
config BT_HCI_RAW
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
bool "RAW HCI access"
help
This option allows to access Bluetooth controller
from the application with the RAW HCI protocol.
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 14:21:11 +08:00
config BT_PERIPHERAL
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
bool "Peripheral Role support"
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 14:21:11 +08:00
select BT_BROADCASTER
select BT_CONN
default y if BT_HCI_RAW
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
help
Select this for LE Peripheral role support.
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 14:21:11 +08:00
config BT_CENTRAL
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
bool "Central Role support"
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 14:21:11 +08:00
select BT_OBSERVER
select BT_CONN
default y if BT_HCI_RAW
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
help
Select this for LE Central role support.
Bluetooth: Consolidate all role configuration Since role support is fundamental to both the Host and the Controller, move the role configuration options to the top-level file and rename them to fit the GAP specification, avoiding confusion between GAP and LL names. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 16:40:27 +08:00
menu "Broadcaster"
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 14:21:11 +08:00
visible if !BT_PERIPHERAL
Bluetooth: Consolidate all role configuration Since role support is fundamental to both the Host and the Controller, move the role configuration options to the top-level file and rename them to fit the GAP specification, avoiding confusion between GAP and LL names. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 16:40:27 +08: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 14:21:11 +08:00
config BT_BROADCASTER
Bluetooth: Consolidate all role configuration Since role support is fundamental to both the Host and the Controller, move the role configuration options to the top-level file and rename them to fit the GAP specification, avoiding confusion between GAP and LL names. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 16:40:27 +08:00
bool "Broadcaster Role support"
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 14:21:11 +08:00
default y if !BT_OBSERVER
Bluetooth: Consolidate all role configuration Since role support is fundamental to both the Host and the Controller, move the role configuration options to the top-level file and rename them to fit the GAP specification, avoiding confusion between GAP and LL names. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 16:40:27 +08:00
help
Select this for LE Broadcaster role support.
endmenu
menu "Observer"
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 14:21:11 +08:00
visible if !BT_CENTRAL
Bluetooth: Consolidate all role configuration Since role support is fundamental to both the Host and the Controller, move the role configuration options to the top-level file and rename them to fit the GAP specification, avoiding confusion between GAP and LL names. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 16:40:27 +08: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 14:21:11 +08:00
config BT_OBSERVER
Bluetooth: Consolidate all role configuration Since role support is fundamental to both the Host and the Controller, move the role configuration options to the top-level file and rename them to fit the GAP specification, avoiding confusion between GAP and LL names. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 16:40:27 +08:00
bool "Observer Role support"
help
Select this for LE Observer role support.
endmenu
Bluetooth: Add common Kconfig option to disable PHY Update This adds common option to disable support for PHY Update procedure in controller and host. This will reduce flash usage by compiling out le_phy_update_complete event handler that will never be called if controller has been compiled with BT_CTLR_PHY option disabled. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-11-21 17:52:18 +08:00
config BT_PHY_UPDATE
bool "PHY Update"
default y
help
Enable support for Bluetooth 5.0 PHY Update Procedure.
Bluetooth: Add common Kconfig option to disable LE Data Length Update This adds common option to disable support for LE Data Length Update procedure in controller and host. This will reduce flash usage by compiling out le_data_len_change event handler that will never be called if controller has been compiled with BT_CTLR_DATA_LENGTH option disabled. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-11-21 18:14:19 +08:00
config BT_DATA_LEN_UPDATE
bool "Data Length Update"
default y
help
Enable support for Bluetooth v4.2 LE Data Length Update procedure.
subsys: bluetooth: services: dev. information service enhancements This commit moves the BLE GATT Device Information service from /samples/bluetooth/gatt to /subsys/bluetooth/services and adds a Kconfig entry to enable and configure the service; when enabled, it will register itself automatically. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no> Signed-off-by: Radoslaw Koppel <radoslaw.koppel@nordicsemi.no>
2018-11-01 23:44:52 +08:00
source "subsys/bluetooth/services/Kconfig"
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 14:21:11 +08:00
config BT_CONN
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
# Virtual/hidden option
bool
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 14:21:11 +08:00
config BT_MAX_CONN
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
int "Maximum number of simultaneous connections"
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 14:21:11 +08:00
depends on BT_CONN
Bluetooth: Reshuffle Kconfig options In order to achieve proper sharing of configuration options, everything that is common to both the Host and the Controller should now be placed in the top-level Kconfig file, and Controller-only options are in the controller/ Kconfig one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-03 21:42:59 +08:00
range 1 64
default 1
help
Maximum number of simultaneous Bluetooth connections
supported.
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 14:21:11 +08:00
if BT_CONN
config BT_HCI_ACL_FLOW_CONTROL
Bluetooth: Consolidate flow control Kconfig Since Controller to Host flow control is a feature that affects both sides equally, move it to the top-level Kconfig file and consolidate its use in both Controller and Host. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-04 22:09:53 +08:00
bool "Controller to Host ACL flow control support"
# Enable if building a Host-only build
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 19:45:13 +08:00
default y if !BT_CTLR
Bluetooth: Consolidate flow control Kconfig Since Controller to Host flow control is a feature that affects both sides equally, move it to the top-level Kconfig file and consolidate its use in both Controller and Host. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-04 22:09:53 +08:00
# Enable if building a Controller-only build
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 14:21:11 +08:00
default y if BT_HCI_RAW
Bluetooth: Consolidate flow control Kconfig Since Controller to Host flow control is a feature that affects both sides equally, move it to the top-level Kconfig file and consolidate its use in both Controller and Host. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-04 22:09:53 +08:00
select POLL
help
Enable support for throttling ACL buffers from the controller
to the host. This is particularly useful when the host and
controller are on separate cores since it ensures that we do
not run out of incoming ACL buffers.
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 14:21:11 +08:00
endif # BT_CONN
Bluetooth: Consolidate flow control Kconfig Since Controller to Host flow control is a feature that affects both sides equally, move it to the top-level Kconfig file and consolidate its use in both Controller and Host. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-04 22:09:53 +08:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 19:45:13 +08:00
config BT_CTLR_TO_HOST_UART_DEV_NAME
Bluetooth: Move hci_uart UART Kconfig to the top-level file To allow for hci_uart builds that do not include the controller code, move the UART Kconfig option used by the sample up one level so that it is shared by all configurations using Bluetooth: Jira: ZEP-2132 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-12 18:41:23 +08:00
string "Device Name of UART Device to an external Bluetooth Host"
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 14:21:11 +08:00
depends on BT_HCI_RAW
Bluetooth: Move hci_uart UART Kconfig to the top-level file To allow for hci_uart builds that do not include the controller code, move the UART Kconfig option used by the sample up one level so that it is shared by all configurations using Bluetooth: Jira: ZEP-2132 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-12 18:41:23 +08:00
help
This option specifies the name of UART device to be used
to connect to an external Bluetooth Host when Zephyr is
acting as a Bluetooth Controller.
samples: Bluetooth: add HCI SPI raw handler sample Add a sample application that allows a Zephyr-based Bluetooth controller to interface with an HCI driver via SPI. This sample implements the same BT SPI protocol already as Zephyr's HCI SPI driver. Currently, the sample only supports the legacy SPI API. Provide a single configuration file, avoiding board-specific files. Some board-specific configuration information must be provided via other means: - CONFIG_BT_CONTROLLER_TO_HOST_SPI_DEV_NAME - CONFIG_BT_CONTROLLER_TO_HOST_SPI_IRQ_DEV_NAME - CONFIG_BT_CONTROLLER_TO_HOST_SPI_IRQ_PIN Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org> Signed-off-by: Michael Scott <michael.scott@linaro.org>
2016-09-20 18:44:16 +08:00
# TODO add DTS support, once SPI node definitions are available.
config BT_CTLR_TO_HOST_SPI_DEV_NAME
string "Device Name of SPI Device to an external Bluetooth Host"
default "SPI_0"
depends on SPI && BT_HCI_RAW
help
This option specifies the name of SPI device to be used to connect
to an external Bluetooth Host when Zephyr is acting as a Bluetooth
Controller.
config BT_CTLR_TO_HOST_SPI_IRQ_DEV_NAME
string "Device Name of SPI IRQ to an external Bluetooth Host"
default "GPIO_0"
depends on SPI && BT_HCI_RAW
help
This option specifies the name of SPI IRQ device to be used to
notify an external Bluetooth Host when Zephyr is acting as a
Bluetooth Controller.
config BT_CTLR_TO_HOST_SPI_IRQ_PIN
int "SPI IRQ line number to an external Bluetooth Host"
default 0
depends on SPI && BT_HCI_RAW
help
This option specifies the IRQ line number to be used to notify
an external Bluetooth Host when Zephyr is acting as a Bluetooth
Controller.
Bluetooth: Move common code to common/ Since more and more code is going to be reused by both the Host and the Controller, this commit introduces a common/ folder that will contain everything that is not tied to one of the two components but shared by them. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-10 22:27:16 +08:00
source "subsys/bluetooth/common/Kconfig"
Bluetooth: Move Bluetooth host stack to subsys Move the Bluetooth host stack from net/bluetooth to subsys/bluetooth/host. This is preparation for having both host and controller under the same root, i.e. subsys/bluetooth/. Change-Id: I3bc796f7e331fca0c485f3890d62b9c03e027b96 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-02 17:06:56 +08:00
source "subsys/bluetooth/host/Kconfig"
Bluetooth: Move controller code to subsys/bluetooth Move controller code from drivers/controller to subsys/bluetooth/controller. Change-Id: I73f675188485aa3267507bad7647796e593a3da0 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-02 19:07:55 +08:00
source "subsys/bluetooth/controller/Kconfig"
Shell: Add initial code for bt shell module This adds the config option and files of the bt shell module. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2017-05-22 15:17:22 +08:00
source "subsys/bluetooth/shell/Kconfig"
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 14:21:11 +08:00
endif # BT_HCI
Bluetooth: Kconfig: Move BLUETOOTH_CONTROLLER to Controller file Move the Kconfig BLUETOOTH_CONTROLLER switch from top-level Bluetooth Kconfig to Bluetooth Controller Kconfig. Change-id: Iead760c22a0fbbda11e4558c4943b3366ecc8769 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 09:50:49 +08: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 14:21:11 +08:00
endif # BT
Bluetooth: kconfig: Use menu instead of menuconfig To be consistent with other subsystem menu, use menu for Bluetooth support in Kconfig instead of menuconfig which showed up as checkbox. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-13 11:46:59 +08:00
endmenu