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

483 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: 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
#
Change BSD-3 licenses to Apache 2 Change all the Intel and Wind River code license from BSD-3 to Apache 2. Change-Id: Id8be2c1c161a06ea8a0b9f38e17660e11dbb384b Signed-off-by: Javier B Perez Hernandez <javier.b.perez.hernandez@linux.intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> Signed-off-by: Allan Stephens <allan.stephens@windriver.com> Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-10-06 11:00:37 -05:00
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
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
#
Change BSD-3 licenses to Apache 2 Change all the Intel and Wind River code license from BSD-3 to Apache 2. Change-Id: Id8be2c1c161a06ea8a0b9f38e17660e11dbb384b Signed-off-by: Javier B Perez Hernandez <javier.b.perez.hernandez@linux.intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> Signed-off-by: Allan Stephens <allan.stephens@windriver.com> Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-10-06 11:00:37 -05:00
# http://www.apache.org/licenses/LICENSE-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
#
Change BSD-3 licenses to Apache 2 Change all the Intel and Wind River code license from BSD-3 to Apache 2. Change-Id: Id8be2c1c161a06ea8a0b9f38e17660e11dbb384b Signed-off-by: Javier B Perez Hernandez <javier.b.perez.hernandez@linux.intel.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com> Signed-off-by: Allan Stephens <allan.stephens@windriver.com> Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-10-06 11:00:37 -05:00
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
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: Make bt_send stack requirements a Kconfig option This allows to fine tune TX stacks size depending on selected HCI driver. If needed it can be used to tune for monitor too or other logging mechanism used. Change-Id: Ib501921da0b786e151083760d85ec58fe3c08b60 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-11-28 18:24:05 +01:00
# Stack size needed for executing bt_send with specified driver
Bluetooth: Rename SEND_STACK to TX_STACK_SIZE For consistency with RX_STACK_SIZE and the rest of stack sizes, rename to use the normal naming scheme. Change-id: Ib8d484482466fa8d629e6329e07b927abdd6f598 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-12-29 11:17:59 +01:00
config BLUETOOTH_HCI_TX_STACK_SIZE
Bluetooth: Make bt_send stack requirements a Kconfig option This allows to fine tune TX stacks size depending on selected HCI driver. If needed it can be used to tune for monitor too or other logging mechanism used. Change-Id: Ib501921da0b786e151083760d85ec58fe3c08b60 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-11-28 18:24:05 +01:00
int
# Even if no driver is selected the following default is still
# needed e.g. for unit tests.
default 256
default 256 if BLUETOOTH_H4
default 256 if BLUETOOTH_H5
bluetooth: Tune stack sizes after measuring with hci_uart The following readings were obtained after running the peripheral and central_hr apps in qemu combined with the controller (hci_uart) on nRF51 and nRF52: Main Stack 380 Idle Stack: 68 ISR stack: 532 Controller RX Stack: 388 HCI TX Stack: 516 The numbers set in this change provide a safety margin from the ones measured empirically. Change-id: Ice7ad7f081502e0ea1accf856a7937c0bf0783b2 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-12-30 12:01:05 +01:00
default 640 if BLUETOOTH_CONTROLLER
Bluetooth: Make bt_send stack requirements a Kconfig option This allows to fine tune TX stacks size depending on selected HCI driver. If needed it can be used to tune for monitor too or other logging mechanism used. Change-Id: Ib501921da0b786e151083760d85ec58fe3c08b60 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-11-28 18:24:05 +01: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
config BLUETOOTH_HCI_RAW
bool "RAW HCI access"
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
help
This option allows to access Bluetooth controller
from the application with the RAW HCI protocol.
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
# Virtual/hidden option to make the conditions more intuitive
config BLUETOOTH_HCI_HOST
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: 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
depends on !BLUETOOTH_HCI_RAW
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
select TINYCRYPT
select TINYCRYPT_SHA256
select TINYCRYPT_SHA256_HMAC
select TINYCRYPT_SHA256_HMAC_PRNG
Bluetooth: Introduce support for HCI driver-side RX thread Add support for using the context bt_recv() is called in as the RX thread, rather than having a separate host-side RX thread. Change-Id: I256bfe5dece5272c816f2292e58747553189963d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-21 21:09:27 +02:00
config BLUETOOTH_RECV_IS_RX_THREAD
# 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
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_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
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_MAX_CMD_LEN
Bluetooth: Use event/cmd lengths instead of buffer sizes in KConfig It's more intuitive to specify needed command or event lengths rather than the raw buffer size in Kconfig. The exact buffer size calculation can be done in the code itself. Change-Id: I2760cc1182a689b26405e4c2b1428f140b4aa88a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 12:44:40 +02:00
int "Maximum supported HCI command length"
default 64
Bluetooth: Set BR/EDR device name on init This adds support for setting default BR/EDR name on init. For now this is just static configuration but can be extended later on to allow runtime configuration if requested. < HCI Command: Write Local Name (0x03|0x0013) plen 248 Name: Zephyr > HCI Event: Command Complete (0x0e) plen 4 Write Local Name (0x03|0x0013) ncmd 1 Status: Success (0x00) Change-Id: I59ecfc2be8e55c6f90cdb0f12c6fed7f7ce976f8 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-08-09 10:06:41 +02:00
default 255 if BLUETOOTH_BREDR
Bluetooth: Use event/cmd lengths instead of buffer sizes in KConfig It's more intuitive to specify needed command or event lengths rather than the raw buffer size in Kconfig. The exact buffer size calculation can be done in the code itself. Change-Id: I2760cc1182a689b26405e4c2b1428f140b4aa88a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 12:44:40 +02:00
range 64 255
Bluetooth: Set BR/EDR device name on init This adds support for setting default BR/EDR name on init. For now this is just static configuration but can be extended later on to allow runtime configuration if requested. < HCI Command: Write Local Name (0x03|0x0013) plen 248 Name: Zephyr > HCI Event: Command Complete (0x0e) plen 4 Write Local Name (0x03|0x0013) ncmd 1 Status: Success (0x00) Change-Id: I59ecfc2be8e55c6f90cdb0f12c6fed7f7ce976f8 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-08-09 10:06:41 +02:00
range 255 255 if BLUETOOTH_BREDR
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
help
Bluetooth: Use event/cmd lengths instead of buffer sizes in KConfig It's more intuitive to specify needed command or event lengths rather than the raw buffer size in Kconfig. The exact buffer size calculation can be done in the code itself. Change-Id: I2760cc1182a689b26405e4c2b1428f140b4aa88a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 12:44:40 +02:00
Maximum length of each HCI command.
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
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
config BLUETOOTH_RX_BUF_COUNT
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
default 1 if BLUETOOTH_RECV_IS_RX_THREAD
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
range 1 255
help
Number of buffers available for incoming ACL packets or HCI events
from the controller.
config BLUETOOTH_RX_BUF_LEN
int "Maximum supported HCI RX buffer length"
default 70
default 253 if BLUETOOTH_BREDR
range 70 2000
help
Maximum data size for each HCI RX buffer.
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: HCI UART app to run Zephyr as a BLE Controller Add a new sample application in sample/bluetooth/hci-uart that acts as a bridge between a UART and the BLE Controller. It receives commands and ACL data in H4 format over the UART and passes them on to the BLE Controller to be processed. It also conversely forwards all events and incoming ACL data generated by the BLE Controller to the UART. The application uses the hci_raw interface to pipe the data to and from the BLE Controller and UART. Change-Id: Iff7696166a82fe363b2ad4e1abea40103899f927 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-10-15 21:19:08 +02:00
config BLUETOOTH_UART_TO_HOST_DEV_NAME
string "Device Name of UART Device to an external Bluetooth Host"
default "UART_0"
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
depends on BLUETOOTH_HCI_RAW
Bluetooth: HCI UART app to run Zephyr as a BLE Controller Add a new sample application in sample/bluetooth/hci-uart that acts as a bridge between a UART and the BLE Controller. It receives commands and ACL data in H4 format over the UART and passes them on to the BLE Controller to be processed. It also conversely forwards all events and incoming ACL data generated by the BLE Controller to the UART. The application uses the hci_raw interface to pipe the data to and from the BLE Controller and UART. Change-Id: Iff7696166a82fe363b2ad4e1abea40103899f927 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-10-15 21:19:08 +02:00
help
This option specifies the name of UART device to be used
to connect to an external Bluetooth Host when Zephyr is
acting as a Bluetooth Controller.
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
if BLUETOOTH_HCI_HOST
Bluetooth: storage: Add basic support for internal storage Add basic implementation of an internal storage handler that uses the local file system. The root directory for all Bluetooth related data is /bt. Each remote device has its own subdirectory and each key its own file. This helps keep the implementation very simple, but does come with the meta-data overhead for each file. As an example, the value of a key 0x0001 for a device with a static random address cc:11:22:33:44:55 would be stored in the following file: /bt/cc11223344551/0001. Local values such as the identity address are stored directly under /bt with a file name that matches the key the same way as remote-device files. For full functionality the implementation requires a file system that can support file/directory names of up to 13 characters in length. If the file system supports less than that (as is the case with FAT12) then only local values can be stored (in /bt/abcd). Local values include the identity address as well as the local IRK. Jira: ZEP-181 Change-Id: I7dc696af6353a154cb00dcd01a5f4ac3d7127e6b Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-04 10:47:33 +02:00
config BLUETOOTH_INTERNAL_STORAGE
bool "Use an internal persistent storage handler"
depends on FILE_SYSTEM
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: storage: Add basic support for internal storage Add basic implementation of an internal storage handler that uses the local file system. The root directory for all Bluetooth related data is /bt. Each remote device has its own subdirectory and each key its own file. This helps keep the implementation very simple, but does come with the meta-data overhead for each file. As an example, the value of a key 0x0001 for a device with a static random address cc:11:22:33:44:55 would be stored in the following file: /bt/cc11223344551/0001. Local values such as the identity address are stored directly under /bt with a file name that matches the key the same way as remote-device files. For full functionality the implementation requires a file system that can support file/directory names of up to 13 characters in length. If the file system supports less than that (as is the case with FAT12) then only local values can be stored (in /bt/abcd). Local values include the identity address as well as the local IRK. Jira: ZEP-181 Change-Id: I7dc696af6353a154cb00dcd01a5f4ac3d7127e6b Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-04 10:47:33 +02:00
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.
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_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: 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
range 1024 65536
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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_PERIPHERAL
Bluetooth: Kconfig: Move BLUETOOTH_CONN selectors to a better place It's move intuitive to have the BLUETOOTH_CONN selectors right before the section for choosing options that depend on them. Change-Id: If3d1a1fcb9c78d715b502b58fba9293ca69d0835 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:57:58 +02:00
bool "Peripheral Role support"
select BLUETOOTH_CONN
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
Select this for LE Peripheral role support.
Bluetooth: Kconfig: Move BLUETOOTH_CONN selectors to a better place It's move intuitive to have the BLUETOOTH_CONN selectors right before the section for choosing options that depend on them. Change-Id: If3d1a1fcb9c78d715b502b58fba9293ca69d0835 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:57:58 +02:00
config BLUETOOTH_CENTRAL
bool "Central Role support"
select BLUETOOTH_CONN
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
Select this for LE Central role support.
Bluetooth: Kconfig: Move BLUETOOTH_CONN selectors to a better place It's move intuitive to have the BLUETOOTH_CONN selectors right before the section for choosing options that depend on them. Change-Id: If3d1a1fcb9c78d715b502b58fba9293ca69d0835 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:57:58 +02:00
config BLUETOOTH_CONN
bool
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
if BLUETOOTH_CONN
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_ATT_MTU
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
int "Attribute Protocol (ATT) channel MTU"
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: Increase default ATT MTU when possible The 23 bytes default is quite limiting. When SMP has been enabled we can do a bit better since we know that we can fit two complete ACL packets to the buffers (23 bytes payload in the first, and 27 in the second). Change-Id: I71d9c484c962b1ff46d325f7182511f168608b8e Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 13:13:20 +02:00
default 50 if BLUETOOTH_SMP # BLUETOOTH_L2CAP_IN_MTU is big enough
# for two complete ACL packets
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
range 23 BLUETOOTH_RX_BUF_LEN
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
The MTU for the ATT channel. The minimum and default is 23,
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
whereas the maximum is limited by CONFIG_BLUETOOTH_RX_BUF_LEN.
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: 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
config BLUETOOTH_ATT_PREPARE_COUNT
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: GATT: Add queuing support This adds queueing support for requests that requires a response making it simpler to use the API. The storage is keep in the parameters of the request so it is up to the application to define how many can be queued but in case the application don't want a request to block waiting for a buffer it can use BLUETOOTH_ATT_REQ_COUNT to control the available buffers which is recommended in case the requests will be sent from the RX fiber. Change-Id: I407c3982a7ecdc4a9eff7172d9d0addd46949783 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-08-02 16:23:26 +03:00
config BLUETOOTH_ATT_REQ_COUNT
int "Number of ATT request buffers"
Bluetooth: ATT: Rework buffer pools to minimize extra data This uses net_buf_simple_{save/restore} so the same buffer can be reused if the buffer needs to be resent, also since the responses don't need to be saved a pool with 1 element is enough while it keeps the code safe from deadlocking when both request and responses use the same pool. Change-Id: Ibaa8e7ef39f4b466d5cd4d55874bd609f0a1d67c Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-10-31 12:53:43 +02:00
default BLUETOOTH_MAX_CONN
Bluetooth: GATT: Add queuing support This adds queueing support for requests that requires a response making it simpler to use the API. The storage is keep in the parameters of the request so it is up to the application to define how many can be queued but in case the application don't want a request to block waiting for a buffer it can use BLUETOOTH_ATT_REQ_COUNT to control the available buffers which is recommended in case the requests will be sent from the RX fiber. Change-Id: I407c3982a7ecdc4a9eff7172d9d0addd46949783 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-08-02 16:23:26 +03:00
range 1 64
help
Bluetooth: ATT: Rework buffer pools to minimize extra data This uses net_buf_simple_{save/restore} so the same buffer can be reused if the buffer needs to be resent, also since the responses don't need to be saved a pool with 1 element is enough while it keeps the code safe from deadlocking when both request and responses use the same pool. Change-Id: Ibaa8e7ef39f4b466d5cd4d55874bd609f0a1d67c Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-10-31 12:53:43 +02:00
Number of outgoing buffers available for ATT requests, this controls
how many requests can be queued without blocking.
Bluetooth: GATT: Add queuing support This adds queueing support for requests that requires a response making it simpler to use the API. The storage is keep in the parameters of the request so it is up to the application to define how many can be queued but in case the application don't want a request to block waiting for a buffer it can use BLUETOOTH_ATT_REQ_COUNT to control the available buffers which is recommended in case the requests will be sent from the RX fiber. Change-Id: I407c3982a7ecdc4a9eff7172d9d0addd46949783 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-08-02 16:23:26 +03:00
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
config BLUETOOTH_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: 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: 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: 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
if BLUETOOTH_SMP
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
config BLUETOOTH_PRIVACY
bool "Privacy Feature"
help
Enable local Privacy Feature support. This makes it possible
to use Resolvable Private Addresses (RPAs).
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
config BLUETOOTH_RPA_TIMEOUT
int "Resolvable Private Address timeout"
depends on BLUETOOTH_PRIVACY
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: 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
config BLUETOOTH_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
config BLUETOOTH_SMP_SC_ONLY
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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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"
depends on BLUETOOTH_TINYCRYPT_ECC
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: 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
endif # BLUETOOTH_SMP
config BLUETOOTH_L2CAP_DYNAMIC_CHANNEL
bool "L2CAP Dynamic Channel support"
Bluetooth: L2CAP: Make CoC depend on SMP This is necessary in order to properly handle security errors which are part of the testing specification thus can influence qualification. Change-Id: If444e753be9196f3d5bb36cea00e332a33aa249f Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-11-03 11:25:23 +02:00
depends on BLUETOOTH_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: Add config option for dynamic GATT db This option will be used to determine if bt_gatt_attr need to store the next attribute or if it directly accessible by index. Change-Id: I98fd43931d67d6c3be3b7a130e6fd2f97f2c4a3a Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-01-14 10:18:55 -03:00
config BLUETOOTH_GATT_DYNAMIC_DB
bool "GATT dynamic database support"
help
This option enables GATT services to be added dynamically to database.
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
config BLUETOOTH_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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: Adjust maximum connections & paired devices range The maximum allowed values in Kconfig were quite conservative. Change-Id: Icd2d09a2d52fbbaf03671147f08e08385c6776c7 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-04 10:42:08 +03:00
range 1 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: 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
endif # BLUETOOTH_CONN
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
endif # BLUETOOTH_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
config BLUETOOTH_TINYCRYPT_ECC
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: 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
depends on BLUETOOTH_HCI_RAW || BLUETOOTH_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: Expose BLUETOOTH_MAX_CONN for controller-only build The controller implementation also uses BLUETOOTH_MAX_CONN, so it needs to be available even when the host hasn't been configured to be part of the build. Change-Id: I31ab42a4f0abe21ae613f5408391446eaf72b35f Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-10-26 11:38:36 +03:00
config BLUETOOTH_MAX_CONN
int "Maximum number of simultaneous connections"
depends on BLUETOOTH_CONN || BLUETOOTH_CONTROLLER
default 1
range 1 64
help
Maximum number of simultaneous Bluetooth connections
supported. The minimum (and default) number is 1.
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_DEBUG
Bluetooth: Kconfig: Split debug selection into a choice This prepares for adding other debug types besides the printf-style logging to the console. Change-Id: Ic2ed305192491734da991c4f61fdaace03fd60f2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:46:09 +03:00
bool
choice
prompt "Bluetooth debug type"
depends on BLUETOOTH
default BLUETOOTH_DEBUG_NONE
config BLUETOOTH_DEBUG_NONE
bool "No debug log"
help
Select this to disable all Bluetooth debug logs.
Bluetooth: Kconfig: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_DEBUG_LOG
Bluetooth: Kconfig: Split debug selection into a choice This prepares for adding other debug types besides the printf-style logging to the console. Change-Id: Ic2ed305192491734da991c4f61fdaace03fd60f2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:46:09 +03:00
bool "Normal printf-style to console"
select BLUETOOTH_DEBUG
Bluetooth: Kconfig: Fix logging dependency on printk Now that all logging methods use printk as a backend the respective Kconfig options should declare the right dependencies. Change-Id: I65c759db0ec7ba6333b76d8d20aea0e374fd4947 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-09 22:46:23 +02:00
select PRINTK
Bluetooth: Add support for using SYS_LOG This add CONFIG_BLUETOOTH_DEBUG_LOG which depends on SYS_LOG since the later can actually use either CONFIG_PRINTK or CONFIG_STDOUT_CONSOLE. Change-Id: Ib2974d1331f6c91d119a218ec95e8bf01069377b Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-04-27 17:57:03 +03:00
select SYS_LOG
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
help
This option enables Bluetooth debug going to standard
serial console.
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_DEBUG_MONITOR
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:54:07 +03:00
bool "Monitor protocol over UART"
select BLUETOOTH_DEBUG
Bluetooth: Kconfig: Fix logging dependency on printk Now that all logging methods use printk as a backend the respective Kconfig options should declare the right dependencies. Change-Id: I65c759db0ec7ba6333b76d8d20aea0e374fd4947 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-12-09 22:46:23 +02:00
select PRINTK
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:54:07 +03:00
select CONSOLE_HAS_DRIVER
help
Use a custom logging protocol over the console UART
instead of plain-text output. Requires a special application
on the host side that can decode this protocol. Currently
the 'btmon' tool from BlueZ is capable of doing this.
Bluetooth: Kconfig: Split debug selection into a choice This prepares for adding other debug types besides the printf-style logging to the console. Change-Id: Ic2ed305192491734da991c4f61fdaace03fd60f2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:46:09 +03:00
doc: Fix terminology in Kconfig files for 'platform' Completing the terminology change started with change 4008 by updating the Kconfig files processed to produce the online documentation, plus header files processed by doxygen. References to 'platform' are change to 'board' Change-Id: Id0ed3dc1439a0ea0a4bd19d4904889cf79bec33e Jira: ZEP-534 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2016-08-17 16:33:08 -07:00
If the target board has two or more external UARTs it is
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:54:07 +03:00
possible to keep using UART_CONSOLE together with this option,
however if there is only a single external UART then
UART_CONSOLE needs to be disabled (in which case printk/printf
will get encoded into the monitor protocol).
Bluetooth: Kconfig: Split debug selection into a choice This prepares for adding other debug types besides the printf-style logging to the console. Change-Id: Ic2ed305192491734da991c4f61fdaace03fd60f2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:46:09 +03:00
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:54:07 +03:00
endchoice
Bluetooth: Kconfig: Split debug selection into a choice This prepares for adding other debug types besides the printf-style logging to the console. Change-Id: Ic2ed305192491734da991c4f61fdaace03fd60f2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:46:09 +03:00
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_DEBUG_COLOR
Bluetooth: Add color logging support Add basic color logging support. Error logs will be printed in red whereas warn() logs in yellow. The support is behind a Kconfig option in case someone needs to build the stack for a terminal that doesn't support the ANSI color codes. Change-Id: I080e32db68f87e81f1bb54aa4c634f7cd38f1e33 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-12-08 12:17:31 +02:00
bool "Use colored logs"
Bluetooth: Add support for using SYS_LOG This add CONFIG_BLUETOOTH_DEBUG_LOG which depends on SYS_LOG since the later can actually use either CONFIG_PRINTK or CONFIG_STDOUT_CONSOLE. Change-Id: Ib2974d1331f6c91d119a218ec95e8bf01069377b Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-04-27 17:57:03 +03:00
depends on BLUETOOTH_DEBUG_LOG
select SYS_LOG_SHOW_COLOR
Bluetooth: Add color logging support Add basic color logging support. Error logs will be printed in red whereas warn() logs in yellow. The support is behind a Kconfig option in case someone needs to build the stack for a terminal that doesn't support the ANSI color codes. Change-Id: I080e32db68f87e81f1bb54aa4c634f7cd38f1e33 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-12-08 12:17:31 +02:00
default y
help
Use color in the logs. This requires an ANSI capable terminal.
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-24 18:17:13 -05:00
config BLUETOOTH_MONITOR_ON_DEV_NAME
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:54:07 +03:00
string "Device Name of Bluetooth monitor logging UART"
depends on BLUETOOTH_DEBUG_MONITOR
default "UART_0"
help
This option specifies the name of UART device to be used
for the Bluetooth monitor logging.
Bluetooth: Kconfig: Split debug selection into a choice This prepares for adding other debug types besides the printf-style logging to the console. Change-Id: Ic2ed305192491734da991c4f61fdaace03fd60f2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 17:46:09 +03:00
if BLUETOOTH_DEBUG
Bluetooth: Kconfig: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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"
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
depends on BLUETOOTH_HCI_HOST
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
help
This option enables debug support for Bluetooth HCI
core.
Bluetooth: Kconfig: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_HCI_HOST
Bluetooth: Kconfig: Clean up and remove redundancies Clean up and remove redundancies in Kconfig. Many 'depends on' statements can be removed by moving entries behind common if-endif blocks. Change-Id: Iaa1c4e717e8353f4c09e991413588cf840281c5d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:28:39 +02:00
depends on BLUETOOTH_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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_HCI_HOST
Bluetooth: Kconfig: Clean up and remove redundancies Clean up and remove redundancies in Kconfig. Many 'depends on' statements can be removed by moving entries behind common if-endif blocks. Change-Id: Iaa1c4e717e8353f4c09e991413588cf840281c5d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:28:39 +02:00
depends on BLUETOOTH_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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_DEBUG_SMP
help
This option enables SMP self-tests executed on startup
to verify security and crypto functions.
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
config BLUETOOTH_SMP_FORCE_BREDR
bool "Force Bluetooth SMP over BR/EDR"
depends on BLUETOOTH_DEBUG_SMP
help
This option enables SMP over BR/EDR even if controller is not
supporting BR/EDR Secure Connections. This optino is solely for
testing and should never be enabled on production devices.
Bluetooth: Kconfig: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_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: Be consistent with the use of tabs vs spaces The most common convention is a space between "config" and the variable name. Change-Id: I0f97d5fee56b7db1808dcf07f21016b11f821fa3 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-08-26 12:46:14 +03:00
config BLUETOOTH_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: 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
depends on BLUETOOTH_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: 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
config BLUETOOTH_DEBUG_RFCOMM
bool "Bluetooth RFCOMM debug"
depends on BLUETOOTH_RFCOMM
help
This option enables debug support for the Bluetooth
RFCOMM layer.
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
config BLUETOOTH_DEBUG_HFP_HF
bool "Bluetooth Hands Free Profile (HFP) debug"
depends on BLUETOOTH_HFP_HF
help
This option enables debug support for the Bluetooth
Hands Free Profile (HFP).
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
config BLUETOOTH_DEBUG_AVDTP
bool "Bluetooth AVDTP debug"
depends on BLUETOOTH_AVDTP
help
This option enables debug support for the Bluetooth 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
config BLUETOOTH_DEBUG_A2DP
bool "Bluetooth A2DP debug"
depends on BLUETOOTH_A2DP
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
config BLUETOOTH_DEBUG_SDP
bool "Bluetooth Service Discovery Protocol (SDP) debug"
depends on BLUETOOTH_BREDR
help
This option enables debug support for the Bluetooth
Service Discovery Protocol (SDP).
Bluetooth: Kconfig: Clean up and remove redundancies Clean up and remove redundancies in Kconfig. Many 'depends on' statements can be removed by moving entries behind common if-endif blocks. Change-Id: Iaa1c4e717e8353f4c09e991413588cf840281c5d Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2015-11-06 21:28:39 +02:00
endif # BLUETOOTH_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: 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
config BLUETOOTH_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: 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
depends on BLUETOOTH_HCI_HOST
Bluetooth: Kconfig: Fix BR/EDR dependencies BR/EDR code should have minimal impact on LE code so to keep it simple just require peripheral and central to be enabled when selecting BR/EDR support. Fix following Kconfig warning: warning: (NETWORKING_WITH_BT && BLUETOOTH_BREDR) selects BLUETOOTH_L2CAP_DYNAMIC_CHANNEL which has unmet direct dependencies (BLUETOOTH && BLUETOOTH_HCI && BLUETOOTH_HCI_HOST && BLUETOOTH_CONN && BLUETOOTH_SMP) Change-Id: I7f7cb8794def0df6daaa4abfe4596df460f1a2b2 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-11-14 18:33:27 +01:00
select BLUETOOTH_PERIPHERAL
select BLUETOOTH_CENTRAL
select BLUETOOTH_SMP
Bluetooth: L2CAP: L2CAP_DYNAMIC_CHANNEL enabled by default when BREDR Makes Kconfig L2CAP_DYNAMIC_CHANNEL option autoselected when turns on BREDR support. Change-Id: Ib56b0e4d578c322837b79c67a7737322b04414f0 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2016-04-25 12:57:11 +02:00
select BLUETOOTH_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: Set BR/EDR device name on init This adds support for setting default BR/EDR name on init. For now this is just static configuration but can be extended later on to allow runtime configuration if requested. < HCI Command: Write Local Name (0x03|0x0013) plen 248 Name: Zephyr > HCI Event: Command Complete (0x0e) plen 4 Write Local Name (0x03|0x0013) ncmd 1 Status: Success (0x00) Change-Id: I59ecfc2be8e55c6f90cdb0f12c6fed7f7ce976f8 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-08-09 10:06:41 +02:00
if BLUETOOTH_BREDR
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
config BLUETOOTH_RFCOMM
bool "Bluetooth RFCOMM protocol support [EXPERIMENTAL]"
help
This option enables Bluetooth RFCOMM support
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
config BLUETOOTH_RFCOMM_L2CAP_MTU
int "L2CAP MTU for RFCOMM frames"
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 BLUETOOTH_RX_BUF_LEN
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
depends on BLUETOOTH_RFCOMM
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
range BLUETOOTH_RX_BUF_LEN 32767
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: 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
config BLUETOOTH_HFP_HF
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: HFP HF: Enforce Kconfig's HFP_HF relation to RFCOMM Whenever turning on HFP HF support there's a need to toggle on automatically RFCOMM support. Change-Id: I2fb75c09534d0b6e49a403a527e1caa7d6f9ffaf Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>
2016-09-23 17:04:16 +02:00
select BLUETOOTH_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: 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
config BLUETOOTH_AVDTP
bool "Bluetooth AVDTP protocol support [EXPERIMENTAL]"
help
This option enables Bluetooth AVDTP support
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
config BLUETOOTH_A2DP
bool "Bluetooth A2DP Profile [EXPERIMENTAL]"
select BLUETOOTH_AVDTP
help
This option enables the A2DP profile
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
config BLUETOOTH_PAGE_TIMEOUT
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: Set BR/EDR device name on init This adds support for setting default BR/EDR name on init. For now this is just static configuration but can be extended later on to allow runtime configuration if requested. < HCI Command: Write Local Name (0x03|0x0013) plen 248 Name: Zephyr > HCI Event: Command Complete (0x0e) plen 4 Write Local Name (0x03|0x0013) ncmd 1 Status: Success (0x00) Change-Id: I59ecfc2be8e55c6f90cdb0f12c6fed7f7ce976f8 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>
2016-08-09 10:06:41 +02:00
config BLUETOOTH_BREDR_NAME
string "Bluetooth BR/EDR device name"
default "Zephyr"
help
Bluetooth BR/EDR name. Name can be up to 248 bytes long (excluding
NULL termination). Can be empty string.
endif # BLUETOOTH_BREDR
Copy permalink