michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/subsys/bluetooth/host/Kconfig

499 lines
14 KiB
Text
Raw Normal View History

Kbuild: Kconfig license headers. This commit add license headers to Kconfig files. Change-Id: I79e60263b8c7b696463ecc84b8ad411af5415117 Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com>
2015-05-20 11:40:39 -05:00
# Kconfig - Bluetooth LE stack configuration options
#
Bluetooth: Permit connectionless host-controller combined build In a host plus controller combined build, if no connection is required, deselect CONFIG_BLUETOOTH_MAX_CONN. This will reduce RAM and ROM usage in the controller. Also, make BLUETOOTH_PERIPHERAL, BLUETOOTH_CENTRAL and BLUETOOTH_CONN switches accessible by the controller kconfig to select the right roles to enable. Change-id: I164cf696ab2a6f4859086d2cb18f6d3f2b1399d3 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 16:04:42 +02:00
# Copyright (c) 2016-2017 Nordic Semiconductor ASA
Bluetooth: Update Intel copyright for files modified in 2016 Change-Id: I10a7cab9a7f911b9f64e17bf24ddce82c2f08c40 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-06-10 12:10:18 +03:00
# Copyright (c) 2015-2016 Intel Corporation
Kbuild: Kconfig license headers. This commit add license headers to Kconfig files. Change-Id: I79e60263b8c7b696463ecc84b8ad411af5415117 Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com>
2015-05-20 11:40:39 -05:00
#
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
Kbuild: Kconfig license headers. This commit add license headers to Kconfig files. Change-Id: I79e60263b8c7b696463ecc84b8ad411af5415117 Signed-off-by: Juan Manuel Cruz <juan.m.cruz.alcaraz@linux.intel.com>
2015-05-20 11:40:39 -05:00
#
Kbuild: new bluetooth options Change-Id: I0c9d964abe56bdab96a60d8164d9b5474074f846 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 18:46:02 -04:00
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 12:23:21 +02:00
comment "Host Stack Configuration"
drivers: bluetooth: nble: restructures Bluetooth Kconfig options This moves both the Bluetooth HCI and NBLE drivers under "Bluetooth Drivers" category. This also adds a selection for choosing Bluetooth stacks as the bulk of both HCI and NBLE stacks cannot be compiled together. Note that this does not move the source files. That should be done in a separate change. Change-Id: I32fa7097ada0fdc52bcc745adb78c7273f4023c6 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 13:05:56 -07: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
config BT_HCI_HOST
Bluetooth: Permit connectionless host-controller combined build In a host plus controller combined build, if no connection is required, deselect CONFIG_BLUETOOTH_MAX_CONN. This will reduce RAM and ROM usage in the controller. Also, make BLUETOOTH_PERIPHERAL, BLUETOOTH_CENTRAL and BLUETOOTH_CONN switches accessible by the controller kconfig to select the right roles to enable. Change-id: I164cf696ab2a6f4859086d2cb18f6d3f2b1399d3 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 16:04:42 +02:00
# Virtual/hidden option to make the conditions more intuitive
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 12:23:21 +02:00
bool
Bluetooth: Simplify configuration and fix warnings Fixes the warnings: ... net/bluetooth/Kconfig:48:warning: defaults for choice values not supported warning: (BLUETOOTH) selects BLUETOOTH_LE which has unmet direct dependencies (BLUETOOTH && BLUETOOTH_STACK_HCI) ... Change-Id: I039a9e0e90ce4cb1732c9c764e2db441ba59660a Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2016-08-10 16:51:20 +03:00
default y
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_HCI_RAW
Bluetooth: Merge bt_conn TX threads into a single one with k_poll Now that the k_poll API is available we can use it to have single connection TX thread instead of multiple ones, which helps reduce the per-connection memory overhead by a substantial amount. Change-Id: Icb5d4da87cf0d660bba8da43186d1e76f41c825a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-02-02 08:24:28 +02:00
select POLL
Bluetooth: Kconfig: Add option for enabling TinyCrypt Add a single option for enabling use of TinyCrypt library for crypto. This option selects all required TinyCrypt options depending on BT features enabled. Thanks to this applications only need to select single option instead of set of required TinyCrypt features. Change-Id: I2862e9ad3e204635f2ed3199433982bcfb7112f6 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-02-09 11:17:02 +01: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
config BT_HCI_CMD_COUNT
Bluetooth: Split HCI command & event buffers to two pools The HCI commands and events have slightly different requirements (e.g. max sizes, or the fact that events don't need any user data) so it makes sense to keep them separate. The total count is kept at 8 (2 + 6) but the ACL_OUT count is modified to not exceed the event count (to avoid inability of handling bursts of Number of Completed Packets events). The ACL_IN count is also modified to keep these symmetric for now. Change-Id: Ia1915a596424425525b6df67e0ddce47a7f618f3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 16:58:18 +02:00
int "Number of HCI command buffers"
default 2
Bluetooth: Introduce config options for buffer counts/sizes Introduce dedicate Kconfig options for ACL & HCI buffer counts and sizes. Change-Id: I96796058f70998e1e721849422c4bc4e950b6d93 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 14:45:02 +02:00
range 2 64
help
Bluetooth: Split HCI command & event buffers to two pools The HCI commands and events have slightly different requirements (e.g. max sizes, or the fact that events don't need any user data) so it makes sense to keep them separate. The total count is kept at 8 (2 + 6) but the ACL_OUT count is modified to not exceed the event count (to avoid inability of handling bursts of Number of Completed Packets events). The ACL_IN count is also modified to keep these symmetric for now. Change-Id: Ia1915a596424425525b6df67e0ddce47a7f618f3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 16:58:18 +02:00
Number of buffers available for HCI commands.
Bluetooth: Introduce config options for buffer counts/sizes Introduce dedicate Kconfig options for ACL & HCI buffer counts and sizes. Change-Id: I96796058f70998e1e721849422c4bc4e950b6d93 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 14:45:02 +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
config BT_RX_BUF_COUNT
Bluetooth: Kconfig: Introduce BLUETOOTH_COMBINED_RX_BUF option If the controller doesn't need ACL host flow control it may want to optimize and use a single pool for incoming data. Change-Id: Iec2a69bd2d7a127c7329d0423ab5ce6b73cb9904 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-21 17:49:39 +02:00
int "Number of HCI RX buffers"
Bluetooth: Remove support for host flow control The controller doesn't support this feature and the only driver that was needing it (h4.c) will be converted not to rely on it in the next patch. Change-Id: Ia514b79b6d05aa128768c2355353b7797e8b8977 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-22 13:45:41 +02:00
default 10
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
default 3 if BT_RECV_IS_RX_THREAD
Bluetooth: Reduce the minimum RX buf count to 2 The recent redesign of the H:4 HCI driver means that the smallest safest RX buffer count goes down to 2. Default is left at 3 however to get a bit better performance. Change-Id: I879c7bd3a769f973dfb9bd179d196ab91f9d2abe Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-31 15:09:56 +02:00
range 2 255
Bluetooth: Kconfig: Introduce BLUETOOTH_COMBINED_RX_BUF option If the controller doesn't need ACL host flow control it may want to optimize and use a single pool for incoming data. Change-Id: Iec2a69bd2d7a127c7329d0423ab5ce6b73cb9904 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-21 17:49:39 +02:00
help
Number of buffers available for incoming ACL packets or HCI events
from the controller.
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_RX_BUF_LEN
Bluetooth: Kconfig: Introduce BLUETOOTH_COMBINED_RX_BUF option If the controller doesn't need ACL host flow control it may want to optimize and use a single pool for incoming data. Change-Id: Iec2a69bd2d7a127c7329d0423ab5ce6b73cb9904 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-21 17:49:39 +02:00
int "Maximum supported HCI RX buffer length"
Bluetooth: Remove ACL details from BT_BUF_RX_SIZE BT_BUF_RX_SIZE is used for the RX buffer pool which is used for both ACL data and HCI events. It should therefore not contain any ACL-specific details. This patch removes the ACL header size from the macro and instead makes taking it into account the responsibility to the Kconfig option. Since buffer sizes are anyway rounded up to the nearest multiple of 4 the default goes up from 70 to 76. Change-Id: I41274d9131e7529d41c16bd66de95637fb150a29 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-16 18:48:31 +02:00
default 76
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
default 264 if BT_BREDR
Bluetooth: Remove ACL details from BT_BUF_RX_SIZE BT_BUF_RX_SIZE is used for the RX buffer pool which is used for both ACL data and HCI events. It should therefore not contain any ACL-specific details. This patch removes the ACL header size from the macro and instead makes taking it into account the responsibility to the Kconfig option. Since buffer sizes are anyway rounded up to the nearest multiple of 4 the default goes up from 70 to 76. Change-Id: I41274d9131e7529d41c16bd66de95637fb150a29 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-16 18:48:31 +02:00
range 73 2000
Bluetooth: Kconfig: Introduce BLUETOOTH_COMBINED_RX_BUF option If the controller doesn't need ACL host flow control it may want to optimize and use a single pool for incoming data. Change-Id: Iec2a69bd2d7a127c7329d0423ab5ce6b73cb9904 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-21 17:49:39 +02:00
help
Bluetooth: Remove ACL details from BT_BUF_RX_SIZE BT_BUF_RX_SIZE is used for the RX buffer pool which is used for both ACL data and HCI events. It should therefore not contain any ACL-specific details. This patch removes the ACL header size from the macro and instead makes taking it into account the responsibility to the Kconfig option. Since buffer sizes are anyway rounded up to the nearest multiple of 4 the default goes up from 70 to 76. Change-Id: I41274d9131e7529d41c16bd66de95637fb150a29 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-16 18:48:31 +02:00
Maximum data size for each HCI RX buffer. This size includes
everything starting with the ACL or HCI event headers. Note that
buffer sizes are always rounded up to the nearest multiple of 4,
so if this Kconfig value is something else then there will be some
wasted space. The minimum of 73 has been taken for LE SC which has
an L2CAP MTU of 65 bytes. On top of this there's the L2CAP header
(4 bytes) and the ACL header (also 4 bytes) which yields 73 bytes.
Bluetooth: Add RAW API interface to Bluetooth HCI RAW channel API is intended to expose HCI interface to the remote entity. The local Bluetooth controller gets owned by the remote entity and host Bluetooth stack is not used. RAW API provides direct access to packets which are sent and received by Bluetooth HCI drivers. Change-Id: I4ba2b7ca2c2b0d6c5de6ef1f231d1c5b82125e09 Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2016-08-09 11:13:52 +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
config BT_HCI_TX_STACK_SIZE
Bluetooth: Kconfig: Group stack size related options Group the stack size related options together to represent a better order when using menuconfig. Change-id: Id2968607e5054e30029c42987b3e70cb8cbfc74d Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 08:38:55 +02:00
# Stack size needed for executing bt_send with specified driver
int
# Even if no driver is selected the following default is still
# needed e.g. for unit tests.
default 256
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
default 256 if BT_H4
default 256 if BT_H5
default 256 if BT_SPI
default 640 if BT_CONTROLLER
Bluetooth: Kconfig: Group stack size related options Group the stack size related options together to represent a better order when using menuconfig. Change-id: Id2968607e5054e30029c42987b3e70cb8cbfc74d Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 08:38:55 +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
config BT_HCI_TX_PRIO
Bluetooth: Add BUILD_ASSERT to check Tx and Rx thread priorities Added BUILD_ASSERT check for Tx and Rx thread priorities. The Tx thread priority shall be higher than Rx thread priority in order to correctly detect transaction violations in ATT and SMP protocols. The Number of Completed Packets for a connection shall be processed before any new data is received and processed for that connection. The Controller's priority receive thread priority shall be higher than the Host's Tx and the Controller's Rx thread priority. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-07-11 09:47:08 +02:00
# Hidden option for Co-Operative Tx thread priority
int
default 7
Kconfig: Move BT_WAIT_NOP into subsys/bluetooth/host The CONFIG_BT_WAIT_NOP define is used only by zephyr/subsys/bluetooth/host/hci_core.c. It is also the only config in drivers/bluetooth that is in use when BT_CONTROLLER is enabled. Moving it into the bluetooth subsystem allows us to restructure the drivers/kconfig code such that the entire Bluetooth driver menu option is omitted when the BT_CONTROLLER is enabled. Moving it will also mean that all configs in drivers/bluetooth will now be related to configuring the source code in drivers/bluetooth. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2017-08-09 13:39:35 +02:00
config BT_WAIT_NOP
bool "Wait for \"NOP\" Command Complete event during init"
depends on BT_HCI
help
Some controllers emit a Command Complete event for the NOP
opcode to indicate that they're ready to receive commands.
This option should be selected if the controller used
exhibits such behavior.
Kconfig: Move BLUETOOTH_HCI_RESERVE into subsys/bluetooth/host There are two kinds of HCI implementations. Bluetooth drivers in drivers/bluetooth that implement HCI by using a wired serial transport layer to talk to an external controller chip. And a bluetooth controller in subsys/bluetooth/controller that directly talks to an internal on-chip controller node. Currently, when the the subsys/bluetooth/controller is used there still exists exposed to the user a bluetooth driver configuration menu, even though no external bluetooth driver is in use. This is due to a dependency on certain configs in driver/bluetooth that are needed even though no external controller is used. This patch moves one of these configs, BLUETOOTH_HCI_RESERVE, from drivers/bluetooth/hci/Kconfig to subsys/bluetooth/host/Kconfig such that eventually we can omit the entire Bluetooth driver menu option. This re-organization does not change when the config can be enabled. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2017-08-07 13:41:21 +02:00
# Headroom that the driver needs for sending and receiving buffers.
# Add a new 'default' entry for each new 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_HCI_RESERVE
Kconfig: Move BLUETOOTH_HCI_RESERVE into subsys/bluetooth/host There are two kinds of HCI implementations. Bluetooth drivers in drivers/bluetooth that implement HCI by using a wired serial transport layer to talk to an external controller chip. And a bluetooth controller in subsys/bluetooth/controller that directly talks to an internal on-chip controller node. Currently, when the the subsys/bluetooth/controller is used there still exists exposed to the user a bluetooth driver configuration menu, even though no external bluetooth driver is in use. This is due to a dependency on certain configs in driver/bluetooth that are needed even though no external controller is used. This patch moves one of these configs, BLUETOOTH_HCI_RESERVE, from drivers/bluetooth/hci/Kconfig to subsys/bluetooth/host/Kconfig such that eventually we can omit the entire Bluetooth driver menu option. This re-organization does not change when the config can be enabled. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2017-08-07 13:41:21 +02:00
int
# Even if no driver is selected the following default is still
# needed e.g. for unit tests.
default 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
default 0 if BT_H4
default 1 if BT_H5
default 1 if BT_SPI
Kconfig: Move BLUETOOTH_HCI_RESERVE into subsys/bluetooth/host There are two kinds of HCI implementations. Bluetooth drivers in drivers/bluetooth that implement HCI by using a wired serial transport layer to talk to an external controller chip. And a bluetooth controller in subsys/bluetooth/controller that directly talks to an internal on-chip controller node. Currently, when the the subsys/bluetooth/controller is used there still exists exposed to the user a bluetooth driver configuration menu, even though no external bluetooth driver is in use. This is due to a dependency on certain configs in driver/bluetooth that are needed even though no external controller is used. This patch moves one of these configs, BLUETOOTH_HCI_RESERVE, from drivers/bluetooth/hci/Kconfig to subsys/bluetooth/host/Kconfig such that eventually we can omit the entire Bluetooth driver menu option. This re-organization does not change when the config can be enabled. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2017-08-07 13:41:21 +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
config BT_RECV_IS_RX_THREAD
Bluetooth: Kconfig: Group stack size related options Group the stack size related options together to represent a better order when using menuconfig. Change-id: Id2968607e5054e30029c42987b3e70cb8cbfc74d Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 08:38:55 +02:00
# Virtual option set by the HCI driver to indicate that there's
# no need for the host to have its own RX thread, rather the
# context that bt_recv() gets called in is already good enough.
# If this is set, the driver RX thread is required as the first
# thing to make a call to bt_rx_thread_ready().
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 09:21:11 +03:00
config BT_RX_STACK_SIZE
Bluetooth: Use k_thread_spawn() instead of deprecated nano_fiber_start() Switch to using the unified kernel k_thread_spawn() API instead of nano_fiber_start(). Change-Id: I325cf467ae2a52c6aec8fc166397c323929e3013 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-10 22:01:50 +02:00
int "Size of the receiving thread stack"
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_HCI_HOST || BT_RECV_IS_RX_THREAD
Bluetooth: Kconfig: Introduce BLUETOOTH_RX_STACK_SIZE Applications may want to fine-tune the stack size of the fiber that's used to make callbacks into the application. Change-Id: I2cd3e79283fe85359389528e84d9bcc21e3e19f6 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-02-12 12:59:55 +02:00
default 1024
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
default 2048 if BT_MESH
default 512 if CONFIG_BT_HCI_RAW
Bluetooth: Kconfig: Introduce BLUETOOTH_RX_STACK_SIZE Applications may want to fine-tune the stack size of the fiber that's used to make callbacks into the application. Change-Id: I2cd3e79283fe85359389528e84d9bcc21e3e19f6 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-02-12 12:59:55 +02:00
range 1024 65536
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
range 1100 65536 if BT_MESH
range 512 65536 if CONFIG_BT_HCI_RAW
Bluetooth: Kconfig: Introduce BLUETOOTH_RX_STACK_SIZE Applications may want to fine-tune the stack size of the fiber that's used to make callbacks into the application. Change-Id: I2cd3e79283fe85359389528e84d9bcc21e3e19f6 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-02-12 12:59:55 +02:00
help
Bluetooth: Use k_thread_spawn() instead of deprecated nano_fiber_start() Switch to using the unified kernel k_thread_spawn() API instead of nano_fiber_start(). Change-Id: I325cf467ae2a52c6aec8fc166397c323929e3013 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-10 22:01:50 +02:00
Size of the receiving thread stack. This is the context from
Bluetooth: Kconfig: Introduce BLUETOOTH_RX_STACK_SIZE Applications may want to fine-tune the stack size of the fiber that's used to make callbacks into the application. Change-Id: I2cd3e79283fe85359389528e84d9bcc21e3e19f6 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-02-12 12:59:55 +02:00
which all event callbacks to the application occur. The
default value is sufficient for basic operation, but if the
application needs to do advanced things in its callbacks that
require extra stack space, this value can be increased to
Bluetooth: Fix Kconfig typo Fix typo found at net/bluetooth/Kconfig. Change-Id: If606f9911681246162c8ccacd86aa2262883e584 Signed-off-by: Flavio Santes <flavio.santes@intel.com>
2016-10-05 10:00:41 -05:00
accommodate for that.
Bluetooth: Kconfig: Introduce BLUETOOTH_RX_STACK_SIZE Applications may want to fine-tune the stack size of the fiber that's used to make callbacks into the application. Change-Id: I2cd3e79283fe85359389528e84d9bcc21e3e19f6 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-02-12 12:59:55 +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
config BT_RX_PRIO
Bluetooth: Add BUILD_ASSERT to check Tx and Rx thread priorities Added BUILD_ASSERT check for Tx and Rx thread priorities. The Tx thread priority shall be higher than Rx thread priority in order to correctly detect transaction violations in ATT and SMP protocols. The Number of Completed Packets for a connection shall be processed before any new data is received and processed for that connection. The Controller's priority receive thread priority shall be higher than the Host's Tx and the Controller's Rx thread priority. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-07-11 09:47:08 +02:00
# Hidden option for Co-Operative Rx thread priority
int
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_HCI_HOST || BT_RECV_IS_RX_THREAD
Bluetooth: Add BUILD_ASSERT to check Tx and Rx thread priorities Added BUILD_ASSERT check for Tx and Rx thread priorities. The Tx thread priority shall be higher than Rx thread priority in order to correctly detect transaction violations in ATT and SMP protocols. The Number of Completed Packets for a connection shall be processed before any new data is received and processed for that connection. The Controller's priority receive thread priority shall be higher than the Host's Tx and the Controller's Rx thread priority. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-07-11 09:47:08 +02:00
default 8
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_HCI_HOST
Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 12:30:54 +03:00
source "subsys/bluetooth/host/mesh/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 09:21:11 +03:00
config BT_HOST_CRYPTO
Bluetooth: Make LE Encrypt helpers public Expose LE Encrypt helpers to applications. If software- based controller is compiled-in, then controller's AES hardware will be used by the exposed helper interface. Change-id: I2bac9dfa5ccb3dd50447079affb52d920ae5bd81 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>.
2017-03-15 11:19:27 +01:00
# Hidden option that compiles in random number generation and AES
# encryption support using TinyCrypt library if software-based
# controller is disabled.
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 09:21:11 +03:00
default y if !BT_CONTROLLER
Bluetooth: Make LE Encrypt helpers public Expose LE Encrypt helpers to applications. If software- based controller is compiled-in, then controller's AES hardware will be used by the exposed helper interface. Change-id: I2bac9dfa5ccb3dd50447079affb52d920ae5bd81 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>.
2017-03-15 11:19:27 +01:00
select TINYCRYPT
select TINYCRYPT_AES
select TINYCRYPT_SHA256
select TINYCRYPT_SHA256_HMAC
select TINYCRYPT_SHA256_HMAC_PRNG
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_INTERNAL_STORAGE
Bluetooth: Kconfig: Fine tune options for RECV_IS_RX_THREAD Give more sensible values when RECV_IS_RX_THREAD is configured. Change-Id: I40b5bd88213d224cc29f63fccef6cecee5868f77 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-25 15:17:50 +02:00
bool "Use an internal persistent storage handler"
depends on FILE_SYSTEM
depends on PRINTK
help
When selected the application doesn't need to register its own
persistent storage handlers through the bt_storage API, rather
an internal default handler is used for this.
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_CONN
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +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_HCI_ACL_FLOW_CONTROL
config BT_ACL_RX_COUNT
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +03:00
int "Number of incoming ACL data buffers"
default 6
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
default BT_CONTROLLER_RX_BUFFERS if BT_CONTROLLER
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +03:00
range 2 64
help
Number of buffers available for incoming ACL data.
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_L2CAP_RX_MTU
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +03:00
int "Maximum supported L2CAP MTU for incoming data"
default 23
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
default 65 if BT_SMP
default 200 if BT_BREDR
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +03:00
range 23 1300
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
range 65 1300 if BT_SMP
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +03:00
help
Maximum size of each incoming L2CAP PDU.
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_HCI_ACL_FLOW_CONTROL
Bluetooth: (Re)introduce ACL host flow control This feature was removed some time ago, but turns out it's important to have it available for split host-controller setups. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-05-04 14:09:10 +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
config BT_L2CAP_TX_BUF_COUNT
Bluetooth: Consolidate most outgoing ACL TX buffers into a single pool Having TX buffers split into numerous pools has the downside of increased memory consumption. This patch takes the initial step to consolidate these pools into a single one, saving about 248 bytes of RAM for a basic configuration. Change-Id: I449ba18b44a9a6af68e9a2c44f19a9286eb88b14 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-07 17:05:58 +02:00
int "Number of L2CAP TX buffers"
default 3
range 2 255
help
Number of buffers available for outgoing L2CAP packets.
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_L2CAP_TX_MTU
Bluetooth: Consolidate most outgoing ACL TX buffers into a single pool Having TX buffers split into numerous pools has the downside of increased memory consumption. This patch takes the initial step to consolidate these pools into a single one, saving about 248 bytes of RAM for a basic configuration. Change-Id: I449ba18b44a9a6af68e9a2c44f19a9286eb88b14 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-07 17:05:58 +02:00
int "Maximum supported L2CAP MTU for L2CAP TX buffers"
Bluetooth: Kconfig: Remove unnecessary default conditionals There should always be one unconditional default and then a conditional for each exception. Change-Id: If1043c70eaae631c0a46c0af065a77199eb8e91b Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-25 13:49:13 +03:00
default 23
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
default 65 if BT_SMP
default 253 if BT_BREDR
Bluetooth: Consolidate most outgoing ACL TX buffers into a single pool Having TX buffers split into numerous pools has the downside of increased memory consumption. This patch takes the initial step to consolidate these pools into a single one, saving about 248 bytes of RAM for a basic configuration. Change-Id: I449ba18b44a9a6af68e9a2c44f19a9286eb88b14 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-07 17:05:58 +02:00
range 23 2000
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
range 65 2000 if BT_SMP
Bluetooth: Make Kconfig buffer sizes follow MTU sizes It's more intuitive to specify needed MTU sizes instead of raw buffer sizes. The exact buffer size calculations can instead be made internally in the code (using the BT_L2CAP_BUF_SIZE helper macro). Change-Id: I0637340a7d99e04020f57f49ecd8e6dcfcc4bcf4 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 12:19:26 +02:00
help
Bluetooth: Consolidate most outgoing ACL TX buffers into a single pool Having TX buffers split into numerous pools has the downside of increased memory consumption. This patch takes the initial step to consolidate these pools into a single one, saving about 248 bytes of RAM for a basic configuration. Change-Id: I449ba18b44a9a6af68e9a2c44f19a9286eb88b14 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-07 17:05:58 +02:00
Maximum L2CAP MTU for L2CAP TX 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 09:21:11 +03:00
config BT_CONN_TX_MAX
Bluetooth: Add support for tracking transmitted packets Protocols/profiles may want to know when exactly their PDU has been transmitted over the air. To make this possible, introduce support for a callback that will get called when the controller reports that a packet has been transmitted (through the Number of Completed Packets HCI event). Change-Id: Ia3a19b93c5b2111f144bfabe5861187c41525f30 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-03-17 08:02:57 +02:00
int "Maximum number of pending TX buffers"
default 7
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
default BT_CONTROLLER_TX_BUFFERS if BT_CONTROLLER
Bluetooth: Add support for tracking transmitted packets Protocols/profiles may want to know when exactly their PDU has been transmitted over the air. To make this possible, introduce support for a callback that will get called when the controller reports that a packet has been transmitted (through the Number of Completed Packets HCI event). Change-Id: Ia3a19b93c5b2111f144bfabe5861187c41525f30 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-03-17 08:02:57 +02:00
range 1 128
help
Maximum number of pending TX buffers that have not yet
been acknowledged by the controller.
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_L2CAP_TX_USER_DATA_SIZE
Bluetooth: Consolidate most outgoing ACL TX buffers into a single pool Having TX buffers split into numerous pools has the downside of increased memory consumption. This patch takes the initial step to consolidate these pools into a single one, saving about 248 bytes of RAM for a basic configuration. Change-Id: I449ba18b44a9a6af68e9a2c44f19a9286eb88b14 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-07 17:05:58 +02:00
int "Maximum supported user data size for L2CAP TX buffers"
default 4
range 4 65535
help
Maximum supported user data size for L2CAP TX buffers.
Bluetooth: Introduce config options for buffer counts/sizes Introduce dedicate Kconfig options for ACL & HCI buffer counts and sizes. Change-Id: I96796058f70998e1e721849422c4bc4e950b6d93 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 14:45:02 +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
config BT_ATT_ENFORCE_FLOW
Bluetooth: ATT: Enforce flow for incoming requests & indications It's not valid for a peer to send another request before getting the response to a previous one, or to send another indication without getting the confirmation to a previous one. Take advantage of the recently introduced TX callback to track when it's ok to accept these ATT PDUs again. The HCI USB transport has a potential issue here since a race condition can occur between the ACL data and HCI event endpoints, leading to dropping data when in fact both peers were behaving correctly. To avoid hitting this issue, disable the flow enforcement by default on the qemu targets that commonly use a USB-based controller on the host OS. Change-Id: I2791aaec6f6c0f8fd78a9a809a25e3ce129106c7 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-03-19 12:12:06 +02:00
bool "Enforce strict flow control semantics for incoming PDUs"
default y
default n if BOARD_QEMU_CORTEX_M3 || BOARD_QEMU_X86
help
Enforce flow control rules on incoming PDUs, preventing a peer
from sending new requests until a previous one has been responded
or sending a new indication until a previous one has been
confirmed. This may need to be disabled to avoid potential race
conditions arising from a USB based HCI transport that splits
HCI events and ACL data to separate endpoints.
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_ATT_PREPARE_COUNT
Bluetooth: ATT: Add incoming buffer pool This adds a buffer for incoming prepare writes which can be tunned using BLUETOOTH_ATT_PREPARE_COUNT, these buffers are then used in execute write to commit the data thus making flush callback obsolete: [bt] [DBG] bt_att_recv: (0x001159c0)Received ATT code 0x16 len 50 [bt] [DBG] att_prepare_write_req: (0x001159c0)handle 0x0022 offset 0 [bt] [DBG] prep_write_cb: (0x001159c0)handle 0x0022 offset 0 [bt] [DBG] bt_att_recv: (0x001159c0)Received ATT code 0x16 len 34 [bt] [DBG] att_prepare_write_req: (0x001159c0)handle 0x0022 offset 45 [bt] [DBG] prep_write_cb: (0x001159c0)handle 0x0022 offset 45 [bt] [DBG] bt_att_recv: (0x001159c0)Received ATT code 0x18 len 2 [bt] [DBG] att_exec_write_req: (0x001159c0)flags 0x01 [bt] [DBG] write_cb: (0x001159c0)handle 0x0022 offset 0 [bt] [DBG] write_cb: (0x001159c0)handle 0x0022 offset 45 Change-Id: Iae071d7b4b5b042285952da57e3f7a853cf58afb Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-06-01 12:05:37 +03:00
int "Number of ATT prepare write buffers"
default 0
range 0 64
help
Number of buffers available for ATT prepare write, setting
this to 0 disables GATT long/reliable writes.
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_ATT_TX_MAX
Bluetooth: Introduce flow control for outgoing ATT packets In order to not overload the TX buffer pool and potentially run out of them, enforce flow control for outgoing ATT packets so that the send functions block until the PDU has actually been transmitted over the air. Change-Id: Ic065bb88aec8c2d0ac2def8ef62131a427f7051f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-03-30 18:45:01 +03:00
int "Maximum number of queued outgoing ATT PDUs"
default 2
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
range 1 BT_L2CAP_TX_BUF_COUNT
Bluetooth: Introduce flow control for outgoing ATT packets In order to not overload the TX buffer pool and potentially run out of them, enforce flow control for outgoing ATT packets so that the send functions block until the PDU has actually been transmitted over the air. Change-Id: Ic065bb88aec8c2d0ac2def8ef62131a427f7051f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-03-30 18:45:01 +03:00
help
Number of ATT PDUs that can be at a single moment queued for
transmission. If the application tries to send more than this
amount the calls will block until an existing queued PDU gets
sent.
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_SMP
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Security Manager Protocol support"
Bluetooth: Don't select TinyCrypt RNG for combined builds For combined builds with Controller+Host the Controller's HW RNG is used instead of TinyCrypts PRNG. Change-Id: I4dbe85e547c057cf57ae0934b10866f2bb9f610d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-18 17:05:01 +02:00
select TINYCRYPT
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 12:23:21 +02:00
select TINYCRYPT_AES
select TINYCRYPT_AES_CMAC
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_RPA
Bluetooth: Kconfig: Add missing help texts All user visible options should have at least some help text to them. Change-Id: I97db035f2a4939b4d3c26b7260ad1a39351664b2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 22:22:33 +02:00
help
This option enables support for the Security Manager Protocol
(SMP), making it possible to pair devices over LE.
Bluetooth: Add option for disabling SMP support This allows to not compile SMP support for devices that don't require pairing. It is required to support SMP channel and reply with error for any command received even if pairing is not supported. To handle this cleanly a null smp implementation is used that case. Change-Id: I656a52dac882839db904eee65f25a4e29ea2d8c2 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-09 17:27:16 +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
if BT_SMP
config BT_PRIVACY
Bluetooth: Add Privacy Feature support Add initial support for the Privacy Feature, including the ability to manage a local IRK and to use Resolvable Random Addresses. Change-Id: I1c70aea67078dd2a5d07f3b797c37746ebe9ab61 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-04 12:55:11 +03:00
bool "Privacy Feature"
help
Enable local Privacy Feature support. This makes it possible
to use Resolvable Private Addresses (RPAs).
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_RPA_TIMEOUT
Bluetooth: Add support for rotating RPA If privacy is enabled we always use RPA, even for active scan. This makes single point of controlling current random address making code simple and not prone to subtle bugs with concurent advertising, scanning and connecting. Currently used RPA is rotated to improve privacy. Timeout value is controlled by Kconfig and by default is 900 seconds (15 minutes). Change-Id: I27a15666a4f2e2962cf6eb20c7cd06f90b7f2bb1 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-07-19 11:55:21 +02:00
int "Resolvable Private Address timeout"
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_PRIVACY
Bluetooth: Add support for rotating RPA If privacy is enabled we always use RPA, even for active scan. This makes single point of controlling current random address making code simple and not prone to subtle bugs with concurent advertising, scanning and connecting. Currently used RPA is rotated to improve privacy. Timeout value is controlled by Kconfig and by default is 900 seconds (15 minutes). Change-Id: I27a15666a4f2e2962cf6eb20c7cd06f90b7f2bb1 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-07-19 11:55:21 +02:00
default 900
range 1 65535
help
This option defines how often resolvable private address is rotated.
Value is provided in seconds and defaults to 900 seconds (15 minutes).
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_SIGNING
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Data signing support"
Bluetooth: Add option for disabling data signing support This allows to not compile data signing support if it is not required. Reduces image size of peripheral sample app from 45772 to 44436 bytes. Change-Id: I2cd3515973d1a70f478cbd68426ec84fd1645d19 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-08 14:10:31 +02:00
help
This option enables data signing which is used for transferring
authenticated data in an unencrypted connection.
Bluetooth: SMP: Add support for Secure Connection Only Mode This patch introduce new Kconfig option that is used to indicate if device should operate in Secure Connection Only Mode. Enabling this option removes support for LE Legacy Pairing. Change-Id: If224b6786f4c840959fe87a31f0224bc1e21f90e Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-12-08 16:59:19 +01: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
config BT_SMP_SC_ONLY
Bluetooth: SMP: Add support for Secure Connection Only Mode This patch introduce new Kconfig option that is used to indicate if device should operate in Secure Connection Only Mode. Enabling this option removes support for LE Legacy Pairing. Change-Id: If224b6786f4c840959fe87a31f0224bc1e21f90e Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-12-08 16:59:19 +01:00
bool "Secure Connections Only Mode"
help
This option enables support for Secure Connection Only Mode. In this
mode device shall only use Security Mode 1 Level 4 with exception
for services that only require Security Mode 1 Level 1 (no security).
Security Mode 1 Level 4 stands for authenticated LE Secure Connections
pairing with encryption. Enabling this option disables legacy pairing.
Bluetooth: Kconfig: Move TinyCrypt ECDH under SMP This is used only for LE SC. Change-Id: I60e5ac391fec1cf1f8648f16021a2956072f2d50 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-02-11 18:27:06 +01: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
config BT_USE_DEBUG_KEYS
Bluetooth: SMP: Add support for debug ECDH keys This add following handling of LE SC debug keys: - if debug keys are disabled locally generated public/private keys is checked to not match debug keys by accident - if debug keys are enabled those are used as local public/private keys pair allowing sniffing of encrypted air traffic - tracking of remote device using debug keys - debug keys are discarded after disconnection regardless of bonding flag being set or not - due to HCI interface limitation debug keys are not supported for HCI based ECDH and compilation error will be rised for such configuration Change-Id: Ie147b1893c4a6b9542b4d2c261973a7acbd8de96 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-03-01 10:57:53 +01:00
bool "Enable Security Manager Debug Mode"
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_TINYCRYPT_ECC
Bluetooth: SMP: Add support for debug ECDH keys This add following handling of LE SC debug keys: - if debug keys are disabled locally generated public/private keys is checked to not match debug keys by accident - if debug keys are enabled those are used as local public/private keys pair allowing sniffing of encrypted air traffic - tracking of remote device using debug keys - debug keys are discarded after disconnection regardless of bonding flag being set or not - due to HCI interface limitation debug keys are not supported for HCI based ECDH and compilation error will be rised for such configuration Change-Id: Ie147b1893c4a6b9542b4d2c261973a7acbd8de96 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-03-01 10:57:53 +01:00
help
This option places Security Manager in a Debug Mode. In this mode
predefined Diffie-Hellman private/public key pair is used as described
in Core Specification Vol. 3, Part H, 2.3.5.6.1. This option should
only be enabled for debugging and should never be used in production.
If this option is enabled anyone is able to decipher encrypted air
traffic.
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_SMP
Bluetooth: Kconfig: Move SMP related option under BLUETOOTH_SMP This makes menuconfig easier to navigate. Change-Id: Ica49bbbde73c785f218846380fd46d5463424890 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-12-08 16:31:45 +01: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
config BT_L2CAP_DYNAMIC_CHANNEL
Bluetooth: Kconfig: Move SMP related option under BLUETOOTH_SMP This makes menuconfig easier to navigate. Change-Id: Ica49bbbde73c785f218846380fd46d5463424890 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-12-08 16:31:45 +01:00
bool "L2CAP Dynamic Channel 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 09:21:11 +03:00
depends on BT_SMP
Bluetooth: Kconfig: Move SMP related option under BLUETOOTH_SMP This makes menuconfig easier to navigate. Change-Id: Ica49bbbde73c785f218846380fd46d5463424890 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-12-08 16:31:45 +01:00
help
This option enables support for LE Connection oriented Channels,
allowing the creation of dynamic L2CAP Channels.
Bluetooth: Add option for disabling data signing support This allows to not compile data signing support if it is not required. Reduces image size of peripheral sample app from 45772 to 44436 bytes. Change-Id: I2cd3515973d1a70f478cbd68426ec84fd1645d19 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-08 14:10:31 +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
config BT_GATT_CLIENT
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "GATT client support"
Bluetooth: Kconfig: Add missing help texts All user visible options should have at least some help text to them. Change-Id: I97db035f2a4939b4d3c26b7260ad1a39351664b2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 22:22:33 +02:00
help
This option enables support for the GATT Client role.
Bluetooth: Add support for disabling GATT client support Binary size reduction of sample peripheral app: 45940 -> 45772 Change-Id: Ia8c463c9642a2928c2cb2ec48d9e9c4eeef20fe7 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2015-09-08 12:47:33 +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
config BT_MAX_PAIRED
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
int "Maximum number of paired devices"
Update Bluetooth options Change-Id: If01bf6b7cc1d195932b5a153b7aa9b96241b2311 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-26 17:20:05 -04:00
default 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 09:21:11 +03:00
default 0 if !BT_SMP
Bluetooth: Kconfig: let MAX_PAIRED be 0 if SMP is not supported Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-07-04 14:56:40 +03:00
range 0 128
Update Bluetooth options Change-Id: If01bf6b7cc1d195932b5a153b7aa9b96241b2311 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-26 17:20:05 -04:00
help
Maximum number of paired Bluetooth devices. The minimum (and
default) number is 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 09:21:11 +03:00
endif # BT_CONN
Bluetooth: Kconfig: Move debug options into separate section This makes it easier to visualize all debug options under a single sub-menu. Change-Id: If69a71138450a4cae24ede2c110f42ced9ee762f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:49:51 +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
config BT_DEVICE_NAME
Bluetooth: Kconfig: Make device name variable generic Change BREDR_NAME to DEVICE_NAME so it can also be used as the LE device name. Change-Id: I9ef55d9dff098372d47d9d5754ad7a7163a65bc0 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-01-27 15:20:32 +02:00
string "Bluetooth device name"
default "Zephyr"
help
Bluetooth device name. Name can be up to 248 bytes long (excluding
NULL termination). Can be empty string.
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_DEVICE_APPEARANCE
Bluetooth: Kconfig: Add CONFIG_BLUETOOTH_DEVICE_APPEARANCE This makes applications able to select the value used for the GAP appearance attribute. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2017-06-02 15:36:08 +03:00
int "Bluetooth device appearance"
range 0 65535
default 0
help
Bluetooth device appearance. For the list of possible values please
consult the following link:
https://www.bluetooth.com/specifications/assigned-numbers
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_HCI_HOST
Bluetooth: Controller: Implement ECC commands Implement the 2 HCI commands that provide ECC public key and shared secret generation: - LE Read Local P-256 Public Key - LE Generate DHKey Jira: ZEP-1246 Change-Id: I79388bfdb9f2e28b9377b4bb6ee2caca25f33f3e Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-11-16 16:24:27 +01: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
config BT_TINYCRYPT_ECC
Bluetooth: Remove conn & SMP dependency from BLUETOOTH_TINYCRYPT_ECC Ever since we expose ECDH as a more generic API that's not bound to SMP we shouldn't be requiring selcting SMP in the configuration for it to be available. Move it outside of the BLUETOOTH_SMP and BLUETOOTH_CONN dependencies. Change-Id: I4ac15ff92b1d4fcf3061a487718d364aa7d43bc8 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-07-22 09:54:12 +03:00
bool "Use TinyCrypt library for ECDH"
Bluetooth: Controller: Implement ECC commands Implement the 2 HCI commands that provide ECC public key and shared secret generation: - LE Read Local P-256 Public Key - LE Generate DHKey Jira: ZEP-1246 Change-Id: I79388bfdb9f2e28b9377b4bb6ee2caca25f33f3e Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-11-16 16:24:27 +01:00
select TINYCRYPT
Bluetooth: Remove conn & SMP dependency from BLUETOOTH_TINYCRYPT_ECC Ever since we expose ECDH as a more generic API that's not bound to SMP we shouldn't be requiring selcting SMP in the configuration for it to be available. Move it outside of the BLUETOOTH_SMP and BLUETOOTH_CONN dependencies. Change-Id: I4ac15ff92b1d4fcf3061a487718d364aa7d43bc8 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-07-22 09:54:12 +03:00
select TINYCRYPT_ECC_DH
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_HCI_RAW || BT_HCI_HOST
Bluetooth: Remove conn & SMP dependency from BLUETOOTH_TINYCRYPT_ECC Ever since we expose ECDH as a more generic API that's not bound to SMP we shouldn't be requiring selcting SMP in the configuration for it to be available. Move it outside of the BLUETOOTH_SMP and BLUETOOTH_CONN dependencies. Change-Id: I4ac15ff92b1d4fcf3061a487718d364aa7d43bc8 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-07-22 09:54:12 +03:00
help
If this option is set TinyCrypt library is used for emulating the
ECDH HCI commands and events needed by e.g. LE Secure Connections.
Bluetooth: Controller: Implement ECC commands Implement the 2 HCI commands that provide ECC public key and shared secret generation: - LE Read Local P-256 Public Key - LE Generate DHKey Jira: ZEP-1246 Change-Id: I79388bfdb9f2e28b9377b4bb6ee2caca25f33f3e Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-11-16 16:24:27 +01:00
In builds including the BLE Host, if not set the controller crypto is
used for ECDH and if the controller doesn't support the required HCI
commands the LE Secure Connections support will be disabled.
In builds including the HCI Raw interface and the BLE Controller, this
option injects support for the 2 HCI commands required for LE Secure
Connections so that Hosts can make use of those.
Bluetooth: Kconfig: Make BLUETOOTH_DEBUG as common for LE & BR/EDR Indicate to the user that the debug support is no longer LE-specific but generic for Bluetooth subsystem. Change-Id: I1a1c39fd03bf857ba673fbb5d15fa50ffba02afa Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2015-11-16 15:16:52 +01: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_DEBUG
config BT_DEBUG_HCI_CORE
Bluetooth: Kconfig: Move debug options into separate section This makes it easier to visualize all debug options under a single sub-menu. Change-Id: If69a71138450a4cae24ede2c110f42ced9ee762f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:49:51 +02:00
bool "Bluetooth HCI core debug"
help
This option enables debug support for Bluetooth HCI
core.
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_DEBUG_CONN
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth connection debug"
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_CONN
Kbuild: new bluetooth options Change-Id: I0c9d964abe56bdab96a60d8164d9b5474074f846 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 18:46:02 -04:00
help
This option enables debug support for Bluetooth
connection handling.
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_DEBUG_KEYS
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth security keys debug"
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_HCI_HOST
depends on BT_SMP
Bluetooth: Add config option for security keys handling This makes sure that keys.c doesn't always have its BT_DBG logs enabled. Change-Id: Ia97149f08a448f55a15c3282f72afb23c495b715 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-06-30 10:47:53 +03:00
help
This option enables debug support for the handling of
Bluetooth security keys.
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_DEBUG_L2CAP
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth L2CAP debug"
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_CONN
Kbuild: new bluetooth options Change-Id: I0c9d964abe56bdab96a60d8164d9b5474074f846 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 18:46:02 -04:00
help
This option enables debug support for the Bluetooth
L2ACP 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_DEBUG_SMP
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth Security Manager Protocol (SMP) debug"
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_HCI_HOST
depends on BT_SMP
Kbuild: new bluetooth options Change-Id: I0c9d964abe56bdab96a60d8164d9b5474074f846 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 18:46:02 -04:00
help
This option enables debug support for the Bluetooth
Security Manager Protocol (SMP).
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_SMP_SELFTEST
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth SMP self tests executed on init"
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_DEBUG_SMP
Bluetooth: Make self-test option relevant to SMP debug Make menuconfig screen more logical placing self-tests option inside Bluetooth block. Currently self-tests looks not belonging to Bluetooth. Change-Id: I1ad2826b1dd09fb7c9b67aace1ad5f280543104d Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2015-08-12 14:55:09 +03:00
help
This option enables SMP self-tests executed on startup
to verify security and crypto functions.
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_SMP_FORCE_BREDR
Bluetooth: SMP: Allow to force BR/EDR without SC support This option allows to register BR/EDR SMP channel without required Secure Connections support in controller. This is solely for testing and should never be enabled in production. Jira: ZEP-605 Change-Id: I1909c900e323f61acef9fa2b46f22e853beeda75 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-09-07 17:30:37 +02:00
bool "Force Bluetooth SMP over BR/EDR"
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_DEBUG_SMP
Bluetooth: SMP: Allow to force BR/EDR without SC support This option allows to register BR/EDR SMP channel without required Secure Connections support in controller. This is solely for testing and should never be enabled in production. Jira: ZEP-605 Change-Id: I1909c900e323f61acef9fa2b46f22e853beeda75 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-09-07 17:30:37 +02:00
help
This option enables SMP over BR/EDR even if controller is not
spell: Kconfig help typos: /kernel /misc /subsys Fix misspellings in Kconfig help text Change-Id: I6eda081c7b6f38287ace8c0a741e65df92d6817b Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-04-21 10:55:27 -07:00
supporting BR/EDR Secure Connections. This option is solely for
Bluetooth: SMP: Allow to force BR/EDR without SC support This option allows to register BR/EDR SMP channel without required Secure Connections support in controller. This is solely for testing and should never be enabled in production. Jira: ZEP-605 Change-Id: I1909c900e323f61acef9fa2b46f22e853beeda75 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-09-07 17:30:37 +02:00
testing and should never be enabled on production devices.
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_DEBUG_ATT
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth Attribute Protocol (ATT) debug"
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_CONN
Kbuild: new bluetooth options Change-Id: I0c9d964abe56bdab96a60d8164d9b5474074f846 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 18:46:02 -04:00
help
This option enables debug support for the Bluetooth
Attribute Protocol (ATT).
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_DEBUG_GATT
Bluetooth: Clean up Kconfig Clean up Kconfig conventions. Change-Id: I06df0b6363cd2dab72e93456455aaef219340e4d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-10-29 13:59:54 +02:00
bool "Bluetooth Generic Attribute Profile (GATT) debug"
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_CONN
Update Bluetooth options Change-Id: If01bf6b7cc1d195932b5a153b7aa9b96241b2311 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-26 17:20:05 -04:00
help
This option enables debug support for the Bluetooth
Generic Attribute Profile (GATT).
Bluetooth: Kconfig: Add missing help texts All user visible options should have at least some help text to them. Change-Id: I97db035f2a4939b4d3c26b7260ad1a39351664b2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 22:22:33 +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
config BT_DEBUG_RFCOMM
Bluetooth: RFCOMM: Initialize and register to L2CAP Initialize RFCOMM layer and register PSM to L2CAP. RFCOMM session which represents the signalling context is also defined. Only one signalling context will be there per ACL connection and hence l2cap chan object is embedded into session. Change-Id: I9b0931b51753571f5da40c76f4b8a7d5f93546fb Origin: Original Signed-off-by: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
2016-08-17 23:25:09 +05:30
bool "Bluetooth RFCOMM debug"
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_RFCOMM
Bluetooth: RFCOMM: Initialize and register to L2CAP Initialize RFCOMM layer and register PSM to L2CAP. RFCOMM session which represents the signalling context is also defined. Only one signalling context will be there per ACL connection and hence l2cap chan object is embedded into session. Change-Id: I9b0931b51753571f5da40c76f4b8a7d5f93546fb Origin: Original Signed-off-by: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
2016-08-17 23:25:09 +05:30
help
This option enables debug support for the Bluetooth
RFCOMM 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_DEBUG_HFP_HF
Bluetooth: HFP HF: Initialize Handsfree profile Initialize Handsfree profile for HF Role and register RFCOMM server channel number to the RFCOMM. And also exposes some basic callbacks which is required for the application. Change-Id: Ic79cbd66ef9529c4eb134cc21efcdbc388bb707d Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
2016-08-26 14:47:27 +05:30
bool "Bluetooth Hands Free Profile (HFP) debug"
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_HFP_HF
Bluetooth: HFP HF: Initialize Handsfree profile Initialize Handsfree profile for HF Role and register RFCOMM server channel number to the RFCOMM. And also exposes some basic callbacks which is required for the application. Change-Id: Ic79cbd66ef9529c4eb134cc21efcdbc388bb707d Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
2016-08-26 14:47:27 +05:30
help
This option enables debug support for the Bluetooth
Hands Free Profile (HFP).
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_DEBUG_AVDTP
Bluetooth: AVDTP: Add missing BLUETOOTH_DEBUG_AVDTP Change-Id: Ib2243f85bb06df9d98d258bce11d4e7ac87f212d Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-09-19 18:19:12 +03:00
bool "Bluetooth AVDTP debug"
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_AVDTP
Bluetooth: AVDTP: Add missing BLUETOOTH_DEBUG_AVDTP Change-Id: Ib2243f85bb06df9d98d258bce11d4e7ac87f212d Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-09-19 18:19:12 +03:00
help
This option enables debug support for the Bluetooth AVDTP.
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_DEBUG_A2DP
Bluetooth: A2DP: Initialization of A2DP A2DP Initialization, registers callback functions with AVDTP. Change-Id: I6b24ca5e7906c08774a173f35da28b1711f34577 Signed-off-by: Itankar, Piyush T <piyush.t.itankar@intel.com>
2016-09-15 16:21:57 +05:30
bool "Bluetooth A2DP debug"
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_A2DP
Bluetooth: A2DP: Initialization of A2DP A2DP Initialization, registers callback functions with AVDTP. Change-Id: I6b24ca5e7906c08774a173f35da28b1711f34577 Signed-off-by: Itankar, Piyush T <piyush.t.itankar@intel.com>
2016-09-15 16:21:57 +05:30
help
This option enables debug support for the Bluetooth
A2DP profile.
Bluetooth: SDP: Server: Initialize and accept incoming connections Initialize SDP, register to L2CAP and accept incoming connections Change-Id: I568db63910d9e6ff418581b9943d528d4260b859 Signed-off-by: Kaustav Dey Biswas <kaustav.d.biswas@intel.com>
2016-09-15 19:27:25 +05:30
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_DEBUG_SDP
Bluetooth: SDP: Server: Initialize and accept incoming connections Initialize SDP, register to L2CAP and accept incoming connections Change-Id: I568db63910d9e6ff418581b9943d528d4260b859 Signed-off-by: Kaustav Dey Biswas <kaustav.d.biswas@intel.com>
2016-09-15 19:27:25 +05:30
bool "Bluetooth Service Discovery Protocol (SDP) debug"
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_BREDR
Bluetooth: SDP: Server: Initialize and accept incoming connections Initialize SDP, register to L2CAP and accept incoming connections Change-Id: I568db63910d9e6ff418581b9943d528d4260b859 Signed-off-by: Kaustav Dey Biswas <kaustav.d.biswas@intel.com>
2016-09-15 19:27:25 +05:30
help
This option enables debug support for the Bluetooth
Service Discovery Protocol (SDP).
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_DEBUG
Bluetooth: Kconfig: Move debug options into separate section This makes it easier to visualize all debug options under a single sub-menu. Change-Id: If69a71138450a4cae24ede2c110f42ced9ee762f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:49:51 +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
config BT_BREDR
Bluetooth: Kconfig: Be consistent with terminology We don't use "Bluetooth Smart" anywhere, so we shouldn't use "Bluetooth Classic" either. Instead, stick to the more technical "LE" and "BR/EDR" terms. Change-Id: Iadfc1c090205e0f417081d63ebe43172c5708a18 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-17 10:26:45 +02:00
bool "Bluetooth BR/EDR support [EXPERIMENTAL]"
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_HCI_HOST
select BT_PERIPHERAL
select BT_CENTRAL
select BT_SMP
select BT_L2CAP_DYNAMIC_CHANNEL
Bluetooth: Kconfig: Add BR/EDR option Enables turn on classic BR/EDR core support in the stack. Change-Id: If078a23e38857081538c52e24689bfa423db2307 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2015-11-12 08:04:13 +01:00
help
Bluetooth: Kconfig: Be consistent with terminology We don't use "Bluetooth Smart" anywhere, so we shouldn't use "Bluetooth Classic" either. Instead, stick to the more technical "LE" and "BR/EDR" terms. Change-Id: Iadfc1c090205e0f417081d63ebe43172c5708a18 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-17 10:26:45 +02:00
This option enables Bluetooth BR/EDR support"
Bluetooth: Kconfig: Add BR/EDR option Enables turn on classic BR/EDR core support in the stack. Change-Id: If078a23e38857081538c52e24689bfa423db2307 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2015-11-12 08:04:13 +01: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_BREDR
config BT_MAX_SCO_CONN
Bluetooth: Kconfig: Move BLUETOOTH_MAX_SCO_CONN to BR/EDR Move the Kconfig option BLUETOOTH_MAX_SCO_CONN to BR/EDR if clause. Change-id: Iead2bc5a70a9499125f9edf22e85ade4dda8f5ac Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 11:39:41 +02:00
int "Maximum number of simultaneous SCO connections"
default 1
range 1 3
help
Maximum number of simultaneous Bluetooth synchronous connections
supported. The minimum (and default) number is 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 09:21:11 +03:00
config BT_RFCOMM
Bluetooth: RFCOMM: Initialize and register to L2CAP Initialize RFCOMM layer and register PSM to L2CAP. RFCOMM session which represents the signalling context is also defined. Only one signalling context will be there per ACL connection and hence l2cap chan object is embedded into session. Change-Id: I9b0931b51753571f5da40c76f4b8a7d5f93546fb Origin: Original Signed-off-by: Jaganath Kanakkassery <jaganathx.kanakkassery@intel.com>
2016-08-17 23:25:09 +05:30
bool "Bluetooth RFCOMM protocol support [EXPERIMENTAL]"
help
This option enables Bluetooth RFCOMM 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 09:21:11 +03:00
config BT_RFCOMM_L2CAP_MTU
Bluetooth: RFCOMM: Shuffle up Kconfig's RFCOMM_L2CAP_MTU Moves RFCOMM frames max length settings directly under the main RFCOMM selector for better relations readability. It uses 'depends on' clause for RFCOMM dependency and proper indentation. Change-Id: Ic4dc0ffddaf8b438ace1f455191b7a707c0e9ed6 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2016-09-23 14:57:25 +02:00
int "L2CAP MTU for RFCOMM frames"
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
default BT_RX_BUF_LEN
default BT_L2CAP_RX_MTU if BT_HCI_ACL_FLOW_CONTROL
depends on BT_RFCOMM
range BT_RX_BUF_LEN 32767
range BT_L2CAP_RX_MTU 32767 if BT_HCI_ACL_FLOW_CONTROL
Bluetooth: RFCOMM: Shuffle up Kconfig's RFCOMM_L2CAP_MTU Moves RFCOMM frames max length settings directly under the main RFCOMM selector for better relations readability. It uses 'depends on' clause for RFCOMM dependency and proper indentation. Change-Id: Ic4dc0ffddaf8b438ace1f455191b7a707c0e9ed6 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2016-09-23 14:57:25 +02:00
help
Maximum size of L2CAP PDU for RFCOMM frames.
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_HFP_HF
Bluetooth: HFP HF: Initialize Handsfree profile Initialize Handsfree profile for HF Role and register RFCOMM server channel number to the RFCOMM. And also exposes some basic callbacks which is required for the application. Change-Id: Ic79cbd66ef9529c4eb134cc21efcdbc388bb707d Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
2016-08-26 14:47:27 +05:30
bool "Bluetooth Handsfree profile HF Role support [EXPERIMENTAL]"
Bluetooth: Switch from printf to printk functions There's now snprintk available that's more light-weight on the stack than snprintf. Change-Id: I6b3e4409703ca92fe6b8f4146ff47c490ab826cb Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-06 21:46:10 +02:00
depends on PRINTK
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_RFCOMM
Bluetooth: HFP HF: Initialize Handsfree profile Initialize Handsfree profile for HF Role and register RFCOMM server channel number to the RFCOMM. And also exposes some basic callbacks which is required for the application. Change-Id: Ic79cbd66ef9529c4eb134cc21efcdbc388bb707d Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
2016-08-26 14:47:27 +05:30
help
This option enables Bluetooth HF 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 09:21:11 +03:00
config BT_AVDTP
Bluetooth: AVDTP: Module Initialization - Data Structure Definition - Registration and Initialization Change-Id: Icca95ccbd2692a7d41fd41ef2c99e34761e864b3 Signed-off-by: Arun Jagadish <arun.jagadish@intel.com>
2016-09-13 15:14:21 +05:30
bool "Bluetooth AVDTP protocol support [EXPERIMENTAL]"
help
This option enables Bluetooth AVDTP 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 09:21:11 +03:00
config BT_A2DP
Bluetooth: A2DP: Initialization of A2DP A2DP Initialization, registers callback functions with AVDTP. Change-Id: I6b24ca5e7906c08774a173f35da28b1711f34577 Signed-off-by: Itankar, Piyush T <piyush.t.itankar@intel.com>
2016-09-15 16:21:57 +05:30
bool "Bluetooth A2DP Profile [EXPERIMENTAL]"
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_AVDTP
Bluetooth: A2DP: Initialization of A2DP A2DP Initialization, registers callback functions with AVDTP. Change-Id: I6b24ca5e7906c08774a173f35da28b1711f34577 Signed-off-by: Itankar, Piyush T <piyush.t.itankar@intel.com>
2016-09-15 16:21:57 +05:30
help
This option enables the A2DP profile
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_PAGE_TIMEOUT
Bluetooth: Kconfig: Option to set page timeout value Added an option to set the page timeout value. Default the timeout is set to 5.12 sec. Change-Id: I196b59f18b9cbf0aaa226ffd85e0bb1699667af2 Signed-off-by: Itankar, Piyush T <piyush.t.itankar@intel.com>
2016-10-12 09:39:19 +05:30
hex "Bluetooth Page Timeout"
default 0x2000
range 0x0001 0xffff
help
This option sets the page timeout value. Value is selected as
(N * 0.625) 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
endif # BT_BREDR
Copy permalink