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

801 lines
23 KiB
Text
Raw Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 13:45:29 +01:00
# Bluetooth Controller configuration options
Bluetooth: Kconfig: Move BLUETOOTH_CONTROLLER to Controller file Move the Kconfig BLUETOOTH_CONTROLLER switch from top-level Bluetooth Kconfig to Bluetooth Controller Kconfig. Change-id: Iead760c22a0fbbda11e4558c4943b3366ecc8769 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 03:50:49 +02:00
# Copyright (c) 2016-2017 Nordic Semiconductor ASA
# SPDX-License-Identifier: Apache-2.0
Bluetooth: Controller: Hardware abstraction layer for nRF5x radio The drivers/bluetooth/controller path adds a native BLE Link Layer (controller and HCI) to the Bluetooth subsystem. This first implementation adds support for the nRF5x series of devices from Nordic Semiconductor. The hal/ folder inside the controller contains all IC-specific code to interface with the radio and baseband. Jira: ZEP-702 Origin: Original Change-Id: I4ed61d5f67af6b4735d746a38a5b55f054521075 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 12:01:06 +02:00
Bluetooth: Kconfig: Move BLUETOOTH_CONTROLLER to Controller file Move the Kconfig BLUETOOTH_CONTROLLER switch from top-level Bluetooth Kconfig to Bluetooth Controller Kconfig. Change-id: Iead760c22a0fbbda11e4558c4943b3366ecc8769 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 03:50:49 +02:00
comment "BLE Controller support"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR
Bluetooth: Kconfig: Move BLUETOOTH_CONTROLLER to Controller file Move the Kconfig BLUETOOTH_CONTROLLER switch from top-level Bluetooth Kconfig to Bluetooth Controller Kconfig. Change-id: Iead760c22a0fbbda11e4558c4943b3366ecc8769 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 03:50:49 +02:00
bool "Bluetooth Controller"
help
Enables support for SoC native controller implementations.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
if BT_CTLR
Bluetooth: Controller: Hardware abstraction layer for nRF5x radio The drivers/bluetooth/controller path adds a native BLE Link Layer (controller and HCI) to the Bluetooth subsystem. This first implementation adds support for the nRF5x series of devices from Nordic Semiconductor. The hal/ folder inside the controller contains all IC-specific code to interface with the radio and baseband. Jira: ZEP-702 Origin: Original Change-Id: I4ed61d5f67af6b4735d746a38a5b55f054521075 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 12:01:06 +02:00
Kconfig: BT: Give the LL selection option a name There is an unnamed choice for the BT link layer selection. Giving the choice a name would allow multiple declarations of the option and the ability to select out-of-tree LL's. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-09-24 17:08:04 +02:00
choice BT_LL_CHOICE
Bluetooth: controller: Introduce BLUETOOTH_LL_SW In preparation for future hardware implementations of the BLE Link Layer, this patch introduces the BLUETOOTH_LL_SW configuration option to specify that the default software LL is to be built. Change-Id: I8b9d5b5e0d2926d18f9e8c8f042a74326895bf95 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-03-14 10:48:59 +01:00
prompt "Bluetooth Link Layer Selection"
help
Select the Bluetooth Link Layer to compile.
Bluetooth: controller: Make ULL/LLL split the default Make the Upper and Lower Link Layer split architecture implementation of the controller as the default when building Zephyr Bluetooth Low Energy controller support in applications. Noticeable missing feature (porting) in comparison to old architecture implementation is, Advanced scheduling of connection events. The missing features will subsequently be submitted upstream. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:39:33 +05:30
config BT_LL_SW_SPLIT
Bluetooth: controller: Conditional compile BT_LL_SW variant Refactor Kconfig and CMakelists.txt to be able to conditionally compile in BT_LL_SW variant in the controller subsystem. This is done to support future controller with vendor specific variant implementations. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-09 15:17:15 +01:00
bool "Software-based BLE Link Layer"
Bluetooth: Reorganize Kconfig options for BLE controller Split meaning of BT_CTLR and BT_LL_SW, since they always are the same. This way BT_CTLR means that there an controller implemented, and BT_LL_SW refers to the specific implementation. This allows alternative controller implementations. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2018-06-26 14:03:34 +02:00
select BT_RECV_IS_RX_THREAD
Bluetooth: Remove rand driver and use entropy instead After porting the rand driver to drivers/entropy, replace the usage of the old, Buetooth-specific driver with the generic entropy one. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-02-21 11:48:35 +01:00
select ENTROPY_GENERATOR
Bluetooth: controller: Introduce BLUETOOTH_LL_SW In preparation for future hardware implementations of the BLE Link Layer, this patch introduces the BLUETOOTH_LL_SW configuration option to specify that the default software LL is to be built. Change-Id: I8b9d5b5e0d2926d18f9e8c8f042a74326895bf95 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-03-14 10:48:59 +01:00
help
Bluetooth: controller: Make ULL/LLL split the default Make the Upper and Lower Link Layer split architecture implementation of the controller as the default when building Zephyr Bluetooth Low Energy controller support in applications. Noticeable missing feature (porting) in comparison to old architecture implementation is, Advanced scheduling of connection events. The missing features will subsequently be submitted upstream. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:39:33 +05:30
Use Zephyr software BLE Link Layer ULL LLL split implementation.
Bluetooth: controller: Introduce BLUETOOTH_LL_SW In preparation for future hardware implementations of the BLE Link Layer, this patch introduces the BLUETOOTH_LL_SW configuration option to specify that the default software LL is to be built. Change-Id: I8b9d5b5e0d2926d18f9e8c8f042a74326895bf95 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-03-14 10:48:59 +01:00
Bluetooth: controller: Make ULL/LLL split the default Make the Upper and Lower Link Layer split architecture implementation of the controller as the default when building Zephyr Bluetooth Low Energy controller support in applications. Noticeable missing feature (porting) in comparison to old architecture implementation is, Advanced scheduling of connection events. The missing features will subsequently be submitted upstream. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:39:33 +05:30
config BT_LL_SW_LEGACY
# NOTE: This OLD architecture implementation will be deprecated, with
# no further new feature development.
bool "Software-based BLE Link Layer (deprecated)"
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
select BT_RECV_IS_RX_THREAD
Bluetooth: controller: Make ULL/LLL split the default Make the Upper and Lower Link Layer split architecture implementation of the controller as the default when building Zephyr Bluetooth Low Energy controller support in applications. Noticeable missing feature (porting) in comparison to old architecture implementation is, Advanced scheduling of connection events. The missing features will subsequently be submitted upstream. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:39:33 +05:30
select BT_HAS_HCI_VS
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
select ENTROPY_GENERATOR
Bluetooth: controller: Make ULL/LLL split the default Make the Upper and Lower Link Layer split architecture implementation of the controller as the default when building Zephyr Bluetooth Low Energy controller support in applications. Noticeable missing feature (porting) in comparison to old architecture implementation is, Advanced scheduling of connection events. The missing features will subsequently be submitted upstream. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:39:33 +05:30
select ENTROPY_NRF5_RNG if SOC_COMPATIBLE_NRF
select ENTROPY_NRF5_BIAS_CORRECTION if SOC_COMPATIBLE_NRF
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
help
Bluetooth: controller: Make ULL/LLL split the default Make the Upper and Lower Link Layer split architecture implementation of the controller as the default when building Zephyr Bluetooth Low Energy controller support in applications. Noticeable missing feature (porting) in comparison to old architecture implementation is, Advanced scheduling of connection events. The missing features will subsequently be submitted upstream. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:39:33 +05:30
Use Zephyr software BLE Link Layer implementation.
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
Bluetooth: controller: Introduce BLUETOOTH_LL_SW In preparation for future hardware implementations of the BLE Link Layer, this patch introduces the BLUETOOTH_LL_SW configuration option to specify that the default software LL is to be built. Change-Id: I8b9d5b5e0d2926d18f9e8c8f042a74326895bf95 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-03-14 10:48:59 +01:00
endchoice
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
config BT_LLL_VENDOR_NORDIC
bool "Use Nordic LLL"
depends on BT_LL_SW_SPLIT && SOC_COMPATIBLE_NRF
Bluetooth: controller: Enable Zephyr VS HCI in ULL/LLL impl. Enable the support for Zephyr HCI Vendor-Specific Commands and Event in the ULL/LLL split architecture implementation of the controller. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 10:33:00 +05:30
select BT_HAS_HCI_VS
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
select ENTROPY_NRF5_RNG
select ENTROPY_NRF5_BIAS_CORRECTION
default y
help
Use Nordic Lower Link Layer implementation.
Bluetooth: Kconfig: Move BLUETOOTH_CONTROLLER to Controller file Move the Kconfig BLUETOOTH_CONTROLLER switch from top-level Bluetooth Kconfig to Bluetooth Controller Kconfig. Change-id: Iead760c22a0fbbda11e4558c4943b3366ecc8769 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-31 03:50:49 +02:00
comment "BLE Controller configuration"
bluetooth: Make controller crypto functions optional Provide flexibility in choosing to use the host defined crypto functions or the ones provided by the controller Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2018-06-26 11:51:18 +02:00
config BT_CTLR_CRYPTO
bool "Enable crypto functions in Controller"
default y
help
Use random number generation and AES encryption support functions
provided by the controller.
Bluetooth: controller: Conditional compile BT_LL_SW variant Refactor Kconfig and CMakelists.txt to be able to conditionally compile in BT_LL_SW variant in the controller subsystem. This is done to support future controller with vendor specific variant implementations. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-09 15:17:15 +01:00
config BT_CTLR_RX_PRIO_STACK_SIZE
bluetooth: controller: Made BT_CTLR_RX_PRIO_STACK_SIZE non-hidden Added prompt to BT_CTLR_RX_PRIO_STACK_SIZE, allowing vendor specific configuration of high priority Rx thread stack size for !SOC_COMPATIBLE_NRF. Signed-off-by: Morten Priess <mtpr@oticon.com>
2019-05-03 07:33:23 +02:00
# Controller's Co-Operative high priority Rx thread stack size.
int "High priority Rx thread stack size" if !SOC_COMPATIBLE_NRF
Bluetooth: controller: Conditional compile BT_LL_SW variant Refactor Kconfig and CMakelists.txt to be able to conditionally compile in BT_LL_SW variant in the controller subsystem. This is done to support future controller with vendor specific variant implementations. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-09 15:17:15 +01:00
default 448
config BT_CTLR_RX_PRIO
# Hidden option for Controller's Co-Operative high priority Rx thread
# priority.
int
default 6
Bluetooth: controller: Implement Read Build Info cmd Implement the Read Build Information VS command. This returns a UTF-8 encoded string, which is extendable by the user via a new Kconfig option. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-09-25 14:19:18 +02:00
config BT_CTLR_HCI_VS_BUILD_INFO
string "Zephyr HCI VS Build Info string"
default ""
Bluetooth: controller: Common config for VS extensions Since the Zephyr HCI VS extensions apply to both the Host (using them for additional functionality) and the Controller (implement the commands and events), it make sense to make this a common setting in order for it to be configurable in a way that applies to both. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-10-03 14:37:06 +02:00
depends on BT_HCI_VS_EXT
Bluetooth: controller: Implement Read Build Info cmd Implement the Read Build Information VS command. This returns a UTF-8 encoded string, which is extendable by the user via a new Kconfig option. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-09-25 14:19:18 +02:00
help
User-defined string that will be returned by the Zephyr VS Read Build
Information command after the Zephyr version and build time. When
setting this to a value different from an empty string, a space
character is required at the beginning to separate it from the
already included information.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_DUP_FILTER_LEN
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Number of addresses in the scan duplicate filter"
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_OBSERVER
Bluetooth: controller: Group dup filter Kconfig with buf options Move the scan duplicate filter length option and group it along with rx/tx buffer size Kconfig options. Change-id: I3df07e667029c7d2571270db442ecb7241a417c2 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-09 05:48:15 +02:00
default 16
help
Set the number of unique BLE addresses that can be filtered as
duplicates while scanning.
Bluetooth: controller: Preliminary work in progress mesh ext. Preliminary work done towards Mesh extensions on the old LL architecture implementation. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-01-09 21:25:14 +05:30
config BT_CTLR_MESH_SCAN_FILTERS
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
int "Number of Mesh scan filters"
Bluetooth: controller: Preliminary work in progress mesh ext. Preliminary work done towards Mesh extensions on the old LL architecture implementation. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-01-09 21:25:14 +05:30
depends on BT_HCI_MESH_EXT
default 1
range 1 15
help
Set the number of unique Mesh Scan Filters available as part of
the Intel Mesh Vendor Specific Extensions.
config BT_CTLR_MESH_SF_PATTERNS
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
int "Number of Mesh scan filter patterns"
Bluetooth: controller: Preliminary work in progress mesh ext. Preliminary work done towards Mesh extensions on the old LL architecture implementation. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-01-09 21:25:14 +05:30
depends on BT_HCI_MESH_EXT
default 15
range 1 15
help
Set the number of unique Mesh Scan Filter patterns available per
Scan Filter as part of the Intel Mesh Vendor Specific Extensions.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_RX_BUFFERS
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Number of Rx 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
default 6 if BT_HCI_RAW
Kconfig: Use the first default with a satisfied condition Up until now, Zephyr has patched Kconfig to use the last 'default' with a satisfied condition, instead of the first one. I'm not sure why the patch was added (it predates Kconfiglib), but I suspect it's related to Kconfig.defconfig files. There are at least three problems with the patch: 1. It's inconsistent with how Kconfig works in other projects, which might confuse newcomers. 2. Due to oversights, earlier 'range' properties are still preferred, as well as earlier 'default' properties on choices. In addition to being inconsistent, this makes it impossible to override 'range' properties and choice 'default' properties if the base definition of the symbol/choice already has 'range'/'default' properties. I've seen errors caused by the inconsistency, and I suspect there are more. 3. A fork of Kconfiglib that adds the patch needs to be maintained. Get rid of the patch and go back to standard Kconfig behavior, as follows: 1. Include the Kconfig.defconfig files first instead of last in Kconfig.zephyr. 2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of last in arch/Kconfig. 3. Include arch/<arch>/soc/*/Kconfig first instead of last in arch/<arch>/Kconfig. 4. Swap a few other 'source's to preserve behavior for some scattered symbols with multiple definitions. Swap 'source's in some no-op cases too, where it might match the intent. 5. Reverse the defaults on symbol definitions that have more than one default. Skip defaults that are mutually exclusive, e.g. where each default has an 'if <some board>' condition. They are already safe. 6. Remove the prefer-later-defaults patch from Kconfiglib. Testing was done with a Python script that lists all Kconfig symbols/choices with multiple defaults, along with a whitelist of fixed symbols. The script also verifies that there are no "unreachable" defaults hidden by defaults without conditions As an additional test, zephyr/.config was generated before and after the change for several samples and checked to be identical (after sorting). This commit includes some default-related cleanups as well: - Simplify some symbol definitions, e.g. where a default has 'if FOO' when the symbol already has 'depends on FOO'. - Remove some redundant 'default ""' for string symbols. This is the implicit default. Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and BT_L2CAP_TX_MTU (caused by confusing inconsistency). Piggyback some fixes for style nits too, e.g. unindented help texts. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
default 1
Bluetooth: controller: Increase Rx & Tx buf cnt range in Kconfig With the support for 2M PHY added, the controller can now Rx/Tx upto 18/19 minimum sized L2CAP packets per 7.5ms connection intervals. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-15 11:10:47 +02:00
range 1 18
Bluetooth: Controller: Hardware abstraction layer for nRF5x radio The drivers/bluetooth/controller path adds a native BLE Link Layer (controller and HCI) to the Bluetooth subsystem. This first implementation adds support for the nRF5x series of devices from Nordic Semiconductor. The hal/ folder inside the controller contains all IC-specific code to interface with the radio and baseband. Jira: ZEP-702 Origin: Original Change-Id: I4ed61d5f67af6b4735d746a38a5b55f054521075 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 12:01:06 +02:00
help
Bluetooth: controller: Increase Rx & Tx buf cnt range in Kconfig With the support for 2M PHY added, the controller can now Rx/Tx upto 18/19 minimum sized L2CAP packets per 7.5ms connection intervals. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-15 11:10:47 +02:00
Set the number of Rx PDUs to be buffered in the controller. In a 7.5ms
connection interval and 2M PHY, maximum 18 packets with L2CAP payload
size of 1 byte can be received.
Bluetooth: Controller: Hardware abstraction layer for nRF5x radio The drivers/bluetooth/controller path adds a native BLE Link Layer (controller and HCI) to the Bluetooth subsystem. This first implementation adds support for the nRF5x series of devices from Nordic Semiconductor. The hal/ folder inside the controller contains all IC-specific code to interface with the radio and baseband. Jira: ZEP-702 Origin: Original Change-Id: I4ed61d5f67af6b4735d746a38a5b55f054521075 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 12:01:06 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_TX_BUFFERS
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Number of 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
default 7 if BT_HCI_RAW
Bluetooth: controller: Fix default Tx buffers Fix the default Tx buffers to 3. While the first Tx-ed buffer generates the HCI Number of Completed Packets Event, the controller needs to have 2 additional Tx buffers queued so that the second Tx PDU has the More Data (MD) bit set so as to have the connection event to continue to transmit any additional Tx buffers that the Host will enqueue in the same connection event. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-10-02 13:49:12 +02:00
default 3
Bluetooth: controller: Increase Rx & Tx buf cnt range in Kconfig With the support for 2M PHY added, the controller can now Rx/Tx upto 18/19 minimum sized L2CAP packets per 7.5ms connection intervals. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-15 11:10:47 +02:00
range 1 19
Bluetooth: Controller: Hardware abstraction layer for nRF5x radio The drivers/bluetooth/controller path adds a native BLE Link Layer (controller and HCI) to the Bluetooth subsystem. This first implementation adds support for the nRF5x series of devices from Nordic Semiconductor. The hal/ folder inside the controller contains all IC-specific code to interface with the radio and baseband. Jira: ZEP-702 Origin: Original Change-Id: I4ed61d5f67af6b4735d746a38a5b55f054521075 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 12:01:06 +02:00
help
Bluetooth: controller: Increase Rx & Tx buf cnt range in Kconfig With the support for 2M PHY added, the controller can now Rx/Tx upto 18/19 minimum sized L2CAP packets per 7.5ms connection intervals. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-15 11:10:47 +02:00
Set the number of Tx PDUs to be queued for transmission in the
controller. In a 7.5ms connection interval and 2M PHY, maximum 19
packets can be enqueued, with 18 packets with L2CAP payload size of 1
byte can be acknowledged.
Bluetooth: Controller: Hardware abstraction layer for nRF5x radio The drivers/bluetooth/controller path adds a native BLE Link Layer (controller and HCI) to the Bluetooth subsystem. This first implementation adds support for the nRF5x series of devices from Nordic Semiconductor. The hal/ folder inside the controller contains all IC-specific code to interface with the radio and baseband. Jira: ZEP-702 Origin: Original Change-Id: I4ed61d5f67af6b4735d746a38a5b55f054521075 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-08-15 12:01:06 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_TX_BUFFER_SIZE
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Tx buffer size"
Bluetooth: Controller: Kconfig Tx buffer size Add Kconfig configuration to select Tx buffer size, this value will be returned in the HCI LE Read Buffer Size command response. This configuration will allow lower Tx RAM usage when larger PDU sizes are desired in Rx direction only. Change-Id: I5106a448d78a0754c4b0f6fa61fd5dcacd87a67c Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-30 06:24:42 +01:00
range 27 16384
default 27
help
Size of the Tx buffers and the value returned in HCI LE Read Buffer
Size command response. If this size if greater than effective PDU size
then controller will perform fragmentation before transmitting on the
the packet on air.
Maximum is set to 16384 due to implementation limitations (use of
Bluetooth: convert to using newly introduced integer sized types Convert code to use u{8,16,32,64}_t and s{8,16,32,64}_t instead of C99 integer types. Jira: ZEP-2051 Change-Id: I8f57a17f78e674aca5400f005db8975c9f9e150e Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-04-20 12:00:29 -05:00
u16_t for size/length variables).
Bluetooth: Controller: Kconfig Tx buffer size Add Kconfig configuration to select Tx buffer size, this value will be returned in the HCI LE Read Buffer Size command response. This configuration will allow lower Tx RAM usage when larger PDU sizes are desired in Rx direction only. Change-Id: I5106a448d78a0754c4b0f6fa61fd5dcacd87a67c Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-30 06:24:42 +01:00
Bluetooth: controller: Add Tx Power Kconfig option Add support for changing the default Tx Power value using Kconfig option. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-06-05 00:52:10 +05:30
choice
prompt "Tx Power"
default BT_CTLR_TX_PWR_0
help
Select the supported BLE Radio transmit power level in dBm.
config BT_CTLR_TX_PWR_PLUS_8
bool "+8 dBm"
depends on SOC_NRF52840
config BT_CTLR_TX_PWR_PLUS_7
bool "+7 dBm"
depends on SOC_NRF52840
config BT_CTLR_TX_PWR_PLUS_6
bool "+6 dBm"
depends on SOC_NRF52840
config BT_CTLR_TX_PWR_PLUS_5
bool "+5 dBm"
depends on SOC_NRF52840
config BT_CTLR_TX_PWR_PLUS_4
bool "+4 dBm"
config BT_CTLR_TX_PWR_PLUS_3
bool "+3 dBm"
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
depends on SOC_COMPATIBLE_NRF52X
Bluetooth: controller: Add Tx Power Kconfig option Add support for changing the default Tx Power value using Kconfig option. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-06-05 00:52:10 +05:30
config BT_CTLR_TX_PWR_PLUS_2
bool "+2 dBm"
depends on SOC_NRF52840
config BT_CTLR_TX_PWR_0
bool "0 dBm"
config BT_CTLR_TX_PWR_MINUS_4
bool "-4 dBm"
config BT_CTLR_TX_PWR_MINUS_8
bool "-8 dBm"
config BT_CTLR_TX_PWR_MINUS_12
bool "-12 dBm"
config BT_CTLR_TX_PWR_MINUS_16
bool "-16 dBm"
config BT_CTLR_TX_PWR_MINUS_20
bool "-20 dBm"
config BT_CTLR_TX_PWR_MINUS_30
bool "-30 dBm"
depends on SOC_SERIES_NRF51X
config BT_CTLR_TX_PWR_MINUS_40
bool "-40 dBm"
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
depends on SOC_COMPATIBLE_NRF52X
Bluetooth: controller: Add Tx Power Kconfig option Add support for changing the default Tx Power value using Kconfig option. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-06-05 00:52:10 +05:30
endchoice
Bluetooth: controller: Settings for company_id and subversion_number. Enable use of settings system in controller and introduce settings for company_id and subversion_number. Signed-off-by: Wolfgang Puffitsch <wopu@demant.com>
2019-07-18 10:04:06 +02:00
config BT_CTLR_SETTINGS
bool "Settings System"
depends on BT_SETTINGS
help
Enable use of settings system in controller.
config BT_CTLR_VERSION_SETTINGS
bool "Version Settings"
depends on BT_CTLR_SETTINGS
help
Make Company Id and Subversion Number configurable through
settings system.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_COMPANY_ID
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
hex "Company Id"
Bluetooth: controller: Default to the LF Company ID The Linux Foundation has been assigned a Company Identifier, and with it a means of identifying Zephyr over the air. Default to the LF Company Identifier, which can be overridden by silicon vendors. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-03-02 12:47:09 +01:00
default 0x05F1
Bluetooth: Controller: Kconfig company id and subversion number Add Kconfig option to set the Controller's company id and subversion number. Change-id: I3508aba18bf0b79fd423c7b4142b6fc57eaf55d7 Signed-off-by: Matthias Ringwald <matthias@bluekitchen-gmbh.com> Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-10 12:16:58 +01:00
range 0x0000 0xFFFF
help
Bluetooth: controller: Default to the LF Company ID The Linux Foundation has been assigned a Company Identifier, and with it a means of identifying Zephyr over the air. Default to the LF Company Identifier, which can be overridden by silicon vendors. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-03-02 12:47:09 +01:00
Set the Bluetooth Company Identifier that will be used in
the VERSION_IND PDU. The Linux Foundation's Company Identifier
(0x05F1) is the default value for this option although silicon vendors
and hardware manufacturers can set their own. The full list of
Bluetooth Company Identifiers can be found here:
https://www.bluetooth.com/specifications/assigned-numbers/company-identifiers
Bluetooth: Controller: Kconfig company id and subversion number Add Kconfig option to set the Controller's company id and subversion number. Change-id: I3508aba18bf0b79fd423c7b4142b6fc57eaf55d7 Signed-off-by: Matthias Ringwald <matthias@bluekitchen-gmbh.com> Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-10 12:16:58 +01:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_SUBVERSION_NUMBER
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
hex "Subversion Number"
Bluetooth: Controller: Kconfig company id and subversion number Add Kconfig option to set the Controller's company id and subversion number. Change-id: I3508aba18bf0b79fd423c7b4142b6fc57eaf55d7 Signed-off-by: Matthias Ringwald <matthias@bluekitchen-gmbh.com> Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-10 12:16:58 +01:00
default 0xFFFF
range 0x0000 0xFFFF
help
Set the Subversion Number that will be used in VERSION_IND PDU.
Bluetooth: controller: Move comp id and subver to configuration Move company id and subversion number Kconfig to the Controller configuration section from the features section. Change-id: Ic4deb8b24d84d9b1817ba542705eebd612f0e020 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-28 00:37:05 +02:00
comment "BLE Controller features"
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: controller: Conditionally include conn-related options Only include connection-related options when CONFIG_BLUETOOTH_CONN is selected, since otherwise this can lead to inconsistencies between features and supported commands. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 09:58:59 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_LE_ENC
Bluetooth: controller: Fix disabling LE Encryption support Symbols without prompt cannot be configured from application configuration file. warning: BT_CTLR_LE_ENC (defined at subsys/bluetooth/controller/ Kconfig:198) was assigned the value 'n' but got the value 'y'. This symbol has no prompt, meaning assignments in configuration files have no effect on it. It can only be set indirectly, via Kconfig defaults (e.g. in a Kconfig.defconfig file) or through being 'select'ed or 'imply'd (note: try to avoid Kconfig 'select's except for trivial promptless "helper" symbols without dependencies, as it ignores dependencies and forces symbols on). Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>
2018-07-24 18:58:38 +02:00
bool "LE Encryption"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on !BT_CTLR_DATA_LENGTH_CLEAR && !BT_CTLR_PHY_2M_NRF
Bluetooth: controller: Cond. compile LE Encryption Add Kconfig option to be able to conditional compile the Bluetooth v4.0 LE Encryption procedure. This is needed in order to be able to not support encryption on nRF51 series when using Data Length Update procedure with upto 251 byte payloads until a software-based CCM support is implemented. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-30 00:12:10 +02:00
default y
Bluetooth: controller: Fix disabling LE Encryption support Symbols without prompt cannot be configured from application configuration file. warning: BT_CTLR_LE_ENC (defined at subsys/bluetooth/controller/ Kconfig:198) was assigned the value 'n' but got the value 'y'. This symbol has no prompt, meaning assignments in configuration files have no effect on it. It can only be set indirectly, via Kconfig defaults (e.g. in a Kconfig.defconfig file) or through being 'select'ed or 'imply'd (note: try to avoid Kconfig 'select's except for trivial promptless "helper" symbols without dependencies, as it ignores dependencies and forces symbols on). Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>
2018-07-24 18:58:38 +02:00
help
Enable support for Bluetooth v4.0 LE Encryption feature in the
Controller.
Bluetooth: controller: Cond. compile LE Encryption Add Kconfig option to be able to conditional compile the Bluetooth v4.0 LE Encryption procedure. This is needed in order to be able to not support encryption on nRF51 series when using Data Length Update procedure with upto 251 byte payloads until a software-based CCM support is implemented. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-30 00:12:10 +02:00
Bluetooth: controller: Refactor Conn Param Req implementation Refactor the Connection Parameter Request Procedure to be separate from and not overlap the variables of the Connection Update Procedure. Also, added missing implementations to pass all Connection Parameter Request Procedure related Conformance Tests. Jira: ZEP-1918 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-03-13 11:17:36 +01:00
config BT_CTLR_CONN_PARAM_REQ
bool "Connection Parameter Request"
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
select BT_CTLR_EXT_REJ_IND
Bluetooth: controller: Refactor Conn Param Req implementation Refactor the Connection Parameter Request Procedure to be separate from and not overlap the variables of the Connection Update Procedure. Also, added missing implementations to pass all Connection Parameter Request Procedure related Conformance Tests. Jira: ZEP-1918 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-03-13 11:17:36 +01:00
default y
help
Enable support for Bluetooth v4.1 Connection Parameter Request feature
in the Controller.
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
config BT_CTLR_EXT_REJ_IND
bool "Extended Reject Indication"
default y
help
Enable support for Bluetooth v4.1 Extended Reject Indication feature
in the Controller.
config BT_CTLR_SLAVE_FEAT_REQ
bool "Slave-initiated Features Exchange"
default y
help
Enable support for Bluetooth v4.1 Slave-initiated Features Exchange
feature in the Controller.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_LE_PING
Bluetooth: Controller: Kconfig LE Ping feature Add Kconfig configuration to conditionally enable LE Ping feature in the Controller. This will save CPU time, flash and RAM, if this feature is not desired. Change-id: I5fbbdbe8f45ac01c9b0d7b11e002a0d1db4d272e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-28 05:34:37 +01:00
bool "LE Ping"
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
depends on BT_CTLR_LE_ENC
Bluetooth: Controller: Kconfig LE Ping feature Add Kconfig configuration to conditionally enable LE Ping feature in the Controller. This will save CPU time, flash and RAM, if this feature is not desired. Change-id: I5fbbdbe8f45ac01c9b0d7b11e002a0d1db4d272e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-28 05:34:37 +01:00
default y
help
Enable support for Bluetooth v4.1 LE Ping feature in the Controller.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_PRIVACY
Bluetooth: controller: Add inital support for Controller-based privacy This initial commit adds the following: * Handling of privacy HCI commands * New Link Layer filter module for both whitelist and resolving list * Advertising RPA generation with timeouts Follow-up commits will expand the functionality. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-13 18:26:27 +02:00
bool "LE Controller-based Privacy"
Revert "Bluetooth: controller: Disable controller privacy feature" This reverts commit c629ea8a64c647a1ff1a31088d8fe15970254980. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-09 18:42:48 +05:30
depends on !SOC_SERIES_NRF51X
Bluetooth: controller: Add inital support for Controller-based privacy This initial commit adds the following: * Handling of privacy HCI commands * New Link Layer filter module for both whitelist and resolving list * Advertising RPA generation with timeouts Follow-up commits will expand the functionality. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-13 18:26:27 +02:00
default y
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
select BT_CTLR_FILTER
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: controller: Add inital support for Controller-based privacy This initial commit adds the following: * Handling of privacy HCI commands * New Link Layer filter module for both whitelist and resolving list * Advertising RPA generation with timeouts Follow-up commits will expand the functionality. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-13 18:26:27 +02:00
help
Bluetooth: controller: Split Ext Scan Filter Policies out Since Extended Scanner Filter Policies is an independent feature from Controller-based Privacy, split it out so it can be built independently and included without it. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-15 12:37:04 +02:00
Enable support for Bluetooth v4.2 LE Controller-based Privacy feature
in the Controller.
Bluetooth: controller: Add inital support for Controller-based privacy This initial commit adds the following: * Handling of privacy HCI commands * New Link Layer filter module for both whitelist and resolving list * Advertising RPA generation with timeouts Follow-up commits will expand the functionality. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-13 18:26:27 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_RL_SIZE
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "LE Controller-based Privacy Resolving List size"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on BT_CTLR_PRIVACY
Bluetooth: controller: Add inital support for Controller-based privacy This initial commit adds the following: * Handling of privacy HCI commands * New Link Layer filter module for both whitelist and resolving list * Advertising RPA generation with timeouts Follow-up commits will expand the functionality. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-13 18:26:27 +02:00
default 8
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
range 1 8 if SOC_COMPATIBLE_NRF
Bluetooth: controller: Add inital support for Controller-based privacy This initial commit adds the following: * Handling of privacy HCI commands * New Link Layer filter module for both whitelist and resolving list * Advertising RPA generation with timeouts Follow-up commits will expand the functionality. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-13 18:26:27 +02:00
help
Set the size of the Resolving List for LE Controller-based Privacy.
On nRF5x-based controllers, the hardware imposes a limit of 8 devices.
Bluetooth: controller: Split Ext Scan Filter Policies out Since Extended Scanner Filter Policies is an independent feature from Controller-based Privacy, split it out so it can be built independently and included without it. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-15 12:37:04 +02:00
config BT_CTLR_EXT_SCAN_FP
bool "LE Extended Scanner Filter Policies"
Bluetooth: controller: Fix LE Extended Scanner Filter Policy dependency This adds dependency upon Observer role. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-06-27 16:07:38 +02:00
depends on BT_OBSERVER
Bluetooth: controller: Split Ext Scan Filter Policies out Since Extended Scanner Filter Policies is an independent feature from Controller-based Privacy, split it out so it can be built independently and included without it. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-15 12:37:04 +02:00
default y
help
Enable support for Bluetooth v4.2 LE Extended Scanner Filter Policies
in the Controller.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_DATA_LENGTH
Bluetooth: Add common Kconfig option to disable LE Data Length Update This adds common option to disable support for LE Data Length Update procedure in controller and host. This will reduce flash usage by compiling out le_data_len_change event handler that will never be called if controller has been compiled with BT_CTLR_DATA_LENGTH option disabled. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-11-21 11:14:19 +01:00
# Hidden option to enable support for Bluetooth v4.2 LE Data Length
# Update procedure in the Controller.
bool
depends on BT_DATA_LEN_UPDATE
Bluetooth: controller: Fix disabled clear text DLE for nRF51 series Due to regression the option to enable Data Length Update Procedure for nRF51 series was disable. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-02-09 07:10:09 +05:30
default y if SOC_COMPATIBLE_NRF52X || BT_CTLR_DATA_LENGTH_CLEAR
Bluetooth: Controller: Kconfig Data Length Update feature Add Kconfig configuration to conditionally enable Data Length Update procedure support in the Controller. This will save CPU time, flash and RAM, if this feature is not desired. Change-id: I4515c0c7cf9aeb333a289397ae3c9bac04a08e4e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-28 06:35:05 +01:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_DATA_LENGTH_MAX
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Maximum data length supported"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on BT_CTLR_DATA_LENGTH
Bluetooth: Controller: Kconfig Data Length Update feature Add Kconfig configuration to conditionally enable Data Length Update procedure support in the Controller. This will save CPU time, flash and RAM, if this feature is not desired. Change-id: I4515c0c7cf9aeb333a289397ae3c9bac04a08e4e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-28 06:35:05 +01:00
default 27
Bluetooth: controller: Fix disabled clear text DLE for nRF51 series Due to regression the option to enable Data Length Update Procedure for nRF51 series was disable. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-02-09 07:10:09 +05:30
range 27 251
Bluetooth: Controller: Kconfig Data Length Update feature Add Kconfig configuration to conditionally enable Data Length Update procedure support in the Controller. This will save CPU time, flash and RAM, if this feature is not desired. Change-id: I4515c0c7cf9aeb333a289397ae3c9bac04a08e4e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-28 06:35:05 +01:00
help
Set the maximum data length of PDU supported in the Controller.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_PHY
Bluetooth: Add common Kconfig option to disable PHY Update This adds common option to disable support for PHY Update procedure in controller and host. This will reduce flash usage by compiling out le_phy_update_complete event handler that will never be called if controller has been compiled with BT_CTLR_PHY option disabled. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-11-21 10:52:18 +01:00
# Hidden option to enable support for Bluetooth 5.0 PHY Update
# Procedure in the Controller.
bool
depends on BT_PHY_UPDATE
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
select BT_CTLR_EXT_REJ_IND
Bluetooth: controller: Fix disabled Prop. PHY Update for nRF51 series Due to regression the option to enable PHY Update Procedure on proprietary 2M PHY for nRF51 series was disable. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-02-09 07:10:09 +05:30
default y if SOC_COMPATIBLE_NRF52X || BT_CTLR_PHY_2M_NRF
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
Bluetooth: controller: Fix Kconfig conditional optionals Fix Kconfig conditional include of Minimum Channels Used and Channel Selection Algorithm #2. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-10-01 16:10:05 +05:30
config BT_CTLR_MIN_USED_CHAN
bool "Minimum Number of Used Channels"
default y
help
Enable support for Bluetooth 5.0 Minimum Number of Used Channels
Procedure in 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
endif # BT_CONN
Bluetooth: controller: LE Advertising Extensions PDU structs Add Bluetooth v5.0 LE Advertising Extensions air interface packet structures. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-26 14:41:23 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_CHAN_SEL_2
Bluetooth: controller: Channel Selection Algorithm #2 Add Bluetooth 5.0 LE Channel Selection Algorithm #2 feature Jira: ZEP-2033 Change-id: Ic1155b4399882b89cab33cac78b08b7b39ff6f9d Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-06 05:12:44 +02:00
bool "Channel Selection Algorithm #2"
Bluetooth: controller: Fix Kconfig conditional optionals Fix Kconfig conditional include of Minimum Channels Used and Channel Selection Algorithm #2. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-10-01 16:10:05 +05:30
depends on BT_CONN || BT_CTLR_ADV_EXT
Bluetooth: controller: Channel Selection Algorithm #2 Add Bluetooth 5.0 LE Channel Selection Algorithm #2 feature Jira: ZEP-2033 Change-id: Ic1155b4399882b89cab33cac78b08b7b39ff6f9d Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-04-06 05:12:44 +02:00
default y
help
Enable support for Bluetooth 5.0 LE Channel Selection Algorithm #2 in
the Controller.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_ADV_EXT
Bluetooth: controller: LE Advertising Extensions PDU structs Add Bluetooth v5.0 LE Advertising Extensions air interface packet structures. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-26 14:41:23 +02:00
bool "LE Advertising Extensions"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
select BT_CTLR_SCAN_REQ_NOTIFY
select BT_CTLR_CHAN_SEL_2
Bluetooth: controller: LE Advertising Extensions PDU structs Add Bluetooth v5.0 LE Advertising Extensions air interface packet structures. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-26 14:41:23 +02:00
help
Enable support for Bluetooth 5.0 LE Advertising Extensions in the
Controller.
Bluetooth: controller: Conditionally include conn-related options Only include connection-related options when CONFIG_BLUETOOTH_CONN is selected, since otherwise this can lead to inconsistencies between features and supported commands. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 09:58:59 +02:00
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
config BT_ADV_SET
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
int "LE Advertising Extensions Sets"
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
depends on BT_CTLR_ADV_EXT
default 1
help
Maximum supported advertising sets.
Bluetooth: controller: Add DTM HCI commands Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-25 15:36:41 +02:00
config BT_CTLR_DTM
bool
help
Enable support for Direct Test Mode in the Controller.
config BT_CTLR_DTM_HCI
bool "Direct Test Mode over HCI"
select BT_CTLR_DTM
help
Enable support for Direct Test Mode over the HCI transport.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_ADVANCED_FEATURES
Bluetooth: controller: Hide advance features in Kconfig Added a explicit Kconfig option to show the Controller's advanced feature configurations. These feature configurations need specific in-depth Controller implementation knowledge and should not overwhelm normal users of the Controller. Change-id: Iae764f2b266b199cf180936c51c7a4ea089ee510 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-28 00:25:14 +02:00
bool "Show advanced features"
help
Makes advanced features visible to controller developers.
menu "Advanced features"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
visible if BT_CTLR_ADVANCED_FEATURES
Bluetooth: controller: Hide advance features in Kconfig Added a explicit Kconfig option to show the Controller's advanced feature configurations. These feature configurations need specific in-depth Controller implementation knowledge and should not overwhelm normal users of the Controller. Change-id: Iae764f2b266b199cf180936c51c7a4ea089ee510 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-28 00:25:14 +02:00
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
config BT_CTLR_FILTER
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
bool "Device Whitelist Support"
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
default y
help
Enable support for controller device whitelist feature
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_DATA_LENGTH_CLEAR
Bluetooth: controller: Restrict enc to 1M 27 bytes PDU on nRF51 Restrict encryption support on nRF51 series SoC to Bluetooth LE 1M PHY and max. 27 bytes PDU. If 251 bytes PDU using Data Length Update procedure is desired, then LE Encryption procedure will not be supported (until a software CCM is implemented in future). Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-30 00:44:19 +02:00
bool "Data Length Support (Cleartext only)"
Bluetooth: controller: Fix disabled clear text DLE for nRF51 series Due to regression the option to enable Data Length Update Procedure for nRF51 series was disable. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-02-09 07:10:09 +05:30
depends on SOC_SERIES_NRF51X
Bluetooth: controller: Restrict enc to 1M 27 bytes PDU on nRF51 Restrict encryption support on nRF51 series SoC to Bluetooth LE 1M PHY and max. 27 bytes PDU. If 251 bytes PDU using Data Length Update procedure is desired, then LE Encryption procedure will not be supported (until a software CCM is implemented in future). Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-30 00:44:19 +02:00
help
doc: spelling fixes in Kconfig files regular spelling check on Kconfig.* files Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-06-12 15:48:38 -07:00
Enable support for Bluetooth v4.2 LE Data Length Update procedure, up to
Bluetooth: controller: Restrict enc to 1M 27 bytes PDU on nRF51 Restrict encryption support on nRF51 series SoC to Bluetooth LE 1M PHY and max. 27 bytes PDU. If 251 bytes PDU using Data Length Update procedure is desired, then LE Encryption procedure will not be supported (until a software CCM is implemented in future). Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-30 00:44:19 +02:00
251 byte cleartext payloads in the Controller. Encrypted connections
are not supported.
Bluetooth: controller: Fix PHY bits sets with PHY disabled The 2M and Coded PHY bit should not be set when the PHY update procedure is not supported. Fixes #14658 Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2019-03-19 12:22:28 +01:00
if BT_PHY_UPDATE
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_PHY_2M_NRF
Bluetooth: controller: Restrict enc to 1M 27 bytes PDU on nRF51 Restrict encryption support on nRF51 series SoC to Bluetooth LE 1M PHY and max. 27 bytes PDU. If 251 bytes PDU using Data Length Update procedure is desired, then LE Encryption procedure will not be supported (until a software CCM is implemented in future). Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-30 00:44:19 +02:00
bool "2Mbps Nordic Semiconductor PHY Support (Cleartext only)"
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
depends on SOC_SERIES_NRF51X
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
select BT_CTLR_PHY_2M
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
help
Enable support for Nordic Semiconductor proprietary 2Mbps PHY in the
Controller. Encrypted connections are not supported.
Bluetooth: controller: Fix disabled Prop. PHY Update for nRF51 series Due to regression the option to enable PHY Update Procedure on proprietary 2M PHY for nRF51 series was disable. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-02-09 07:10:09 +05:30
config BT_CTLR_PHY_2M
bool "2Mbps PHY Support"
depends on !SOC_SERIES_NRF51X || BT_CTLR_PHY_2M_NRF
default y
help
Enable support for Bluetooth 5.0 2Mbps PHY in the Controller.
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_PHY_CODED
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
bool "Coded PHY Support"
bluetooth: controller: enable Coded PHY support for nRF52811 Nordic nRF52811 SoC has a 2.4GHx Radio which supports LE Coded PHY, so we add the option to build a BLE Controller for nRF52811 platforms with LE Coded PHY support. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2019-09-19 17:17:35 +02:00
depends on (BT_CTLR_PHY || BT_CTLR_ADV_EXT) && HAS_HW_NRF_RADIO_BLE_CODED
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
default y
help
Enable support for Bluetooth 5.0 Coded PHY in the Controller.
Bluetooth: controller: Fix PHY bits sets with PHY disabled The 2M and Coded PHY bit should not be set when the PHY update procedure is not supported. Fixes #14658 Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2019-03-19 12:22:28 +01:00
endif # BT_PHY_UPDATE
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
Bluetooth: controller: Add Zero Latency IRQ Kconfig Add a Kconfig option to enable use of Zero Latency IRQs in the controller. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-10-08 17:51:03 +05:30
config BT_CTLR_ZLI
bool "Use Zero Latency IRQs"
depends on ZERO_LATENCY_IRQS
help
Enable support for use of Zero Latency IRQ feature. Note, applications
shall not use Zero Latency IRQ themselves when this option is selected,
else will impact controller stability.
Bluetooth: controller: Rename BT_LL_SW to BT_LL_SW_LEGACY Rename the controller Kconfig option BT_LL_SW to BT_LL_SW_LEGACY in preparation towards switch to new Link Layer implementation. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-07-16 21:17:17 +05:30
if BT_LL_SW_LEGACY
Bluetooth: controller: PHY Update Procedure Added support for Bluetooth v5.0 PHY Update Procedure in the Controller. Asymmetric PHY connections do not work for now due to the Radio mode not being setup in time in the ISR during tIFS period and the Radio already ramping up in the cached previous Radio mode to meet tIFS deadline. Subsequent commits will add this feature, by either double buffering the mode in software or using fast radio ramp up which gives enough time in the ISR to change the mode. Jira: ZEP-2086 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-29 06:50:52 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_WORKER_PRIO
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Radio and Ticker's Worker IRQ priority"
Bluetooth: controller: Make worker and job priority configurable Add Controller advanced Kconfig options to select IRQ priorities of the Radio, Ticker's Worker and JOB IRQs. This will provide an opportunity to have peripheral IRQ's of higher level than Bluetooth Controller. Change-id: Iaa128c1cd64a309a77d42d485fdefe68f31e4895 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-30 10:49:34 +02:00
range 0 3 if SOC_SERIES_NRF51X
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
range 0 6 if SOC_COMPATIBLE_NRF52X
Bluetooth: controller: Make worker and job priority configurable Add Controller advanced Kconfig options to select IRQ priorities of the Radio, Ticker's Worker and JOB IRQs. This will provide an opportunity to have peripheral IRQ's of higher level than Bluetooth Controller. Change-id: Iaa128c1cd64a309a77d42d485fdefe68f31e4895 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-30 10:49:34 +02:00
default 0
help
The interrupt priority for event preparation and radio IRQ. This value
shall be less than or equal to the Ticker's Job priority value.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_JOB_PRIO
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Ticker's JOB IRQ priority"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
range BT_CTLR_WORKER_PRIO 3 if SOC_SERIES_NRF51X
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
range BT_CTLR_WORKER_PRIO 6 if SOC_COMPATIBLE_NRF52X
Bluetooth: controller: Make worker and job priority configurable Add Controller advanced Kconfig options to select IRQ priorities of the Radio, Ticker's Worker and JOB IRQs. This will provide an opportunity to have peripheral IRQ's of higher level than Bluetooth Controller. Change-id: Iaa128c1cd64a309a77d42d485fdefe68f31e4895 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-30 10:49:34 +02:00
default 0
help
The interrupt priority for Ticker's Job (SWI4) IRQ. This value shall
be greater than or equal to the Ticker's Worker IRQ priority value.
Bluetooth: controller: Rename BT_LL_SW to BT_LL_SW_LEGACY Rename the controller Kconfig option BT_LL_SW to BT_LL_SW_LEGACY in preparation towards switch to new Link Layer implementation. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-07-16 21:17:17 +05:30
endif # BT_LL_SW_LEGACY
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_XTAL_ADVANCED
Bluetooth: controller: Kconfig for advanced event preparation Added Kconfig option to enable advanced event preparation feature. Enables advanced event preparation offset ahead of radio tx/rx, taking into account predictive processing time requirements in preparation to the event, like control procedure handling and CPU execution speeds. Crystal oscillator is retained between closely spaced consecutive radio events to reduce the overall number of crystal settling current consumptions. This feature maximizes radio utilization in an average role event timeslice when they are closely spaced by using a reduced offset between preparation and radio event. By disabling this feature, the controller will use a constant offset between the preparation and radio event. The controller will toggle crystal oscillator between two closely spaced radio events leading to higher average current due to increased number of crystal settling current consumptions. Change-id: I19e640f7395ac7938873ef4bfac38acf8d6f7e0e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 11:21:56 +02:00
bool "Advanced event preparation"
default y
help
Enables advanced event preparation offset ahead of radio tx/rx, taking
into account predictive processing time requirements in preparation to
the event, like control procedure handling and CPU execution speeds.
Crystal oscillator is retained between closely spaced consecutive
radio events to reduce the overall number of crystal settling current
consumptions.
This feature maximizes radio utilization in an average role event
timeslice when they are closely spaced by using a reduced offset
between preparation and radio event.
By disabling this feature, the controller will use a constant offset
between the preparation and radio event. The controller will toggle
crystal oscillator between two closely spaced radio events leading to
higher average current due to increased number of crystal settling
current consumptions.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_XTAL_THRESHOLD
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Crystal shutdown threshold in uS"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on BT_CTLR_XTAL_ADVANCED
Bluetooth: controller: Improved continuous scanning Refactored the high frequency clock preparation advanced feature to improve radio utilization during continuous scanning. The inter-event timespace value now considers the reserved timespace while determining if the high frequency clock will be retained. This reduces the preparation time, hence increased radio use inside scan window. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-02-02 13:11:41 +01:00
default 1500
Bluetooth: controller: Kconfig for advanced event preparation Added Kconfig option to enable advanced event preparation feature. Enables advanced event preparation offset ahead of radio tx/rx, taking into account predictive processing time requirements in preparation to the event, like control procedure handling and CPU execution speeds. Crystal oscillator is retained between closely spaced consecutive radio events to reduce the overall number of crystal settling current consumptions. This feature maximizes radio utilization in an average role event timeslice when they are closely spaced by using a reduced offset between preparation and radio event. By disabling this feature, the controller will use a constant offset between the preparation and radio event. The controller will toggle crystal oscillator between two closely spaced radio events leading to higher average current due to increased number of crystal settling current consumptions. Change-id: I19e640f7395ac7938873ef4bfac38acf8d6f7e0e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 11:21:56 +02:00
help
Configure the optimal delta in micro seconds between two consecutive
Bluetooth: controller: Improved continuous scanning Refactored the high frequency clock preparation advanced feature to improve radio utilization during continuous scanning. The inter-event timespace value now considers the reserved timespace while determining if the high frequency clock will be retained. This reduces the preparation time, hence increased radio use inside scan window. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-02-02 13:11:41 +01:00
radio events, event done to next preparation, below which (active
clock) crystal will be retained. This value is board dependent.
Bluetooth: controller: Kconfig for advanced event preparation Added Kconfig option to enable advanced event preparation feature. Enables advanced event preparation offset ahead of radio tx/rx, taking into account predictive processing time requirements in preparation to the event, like control procedure handling and CPU execution speeds. Crystal oscillator is retained between closely spaced consecutive radio events to reduce the overall number of crystal settling current consumptions. This feature maximizes radio utilization in an average role event timeslice when they are closely spaced by using a reduced offset between preparation and radio event. By disabling this feature, the controller will use a constant offset between the preparation and radio event. The controller will toggle crystal oscillator between two closely spaced radio events leading to higher average current due to increased number of crystal settling current consumptions. Change-id: I19e640f7395ac7938873ef4bfac38acf8d6f7e0e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 11:21:56 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_SCHED_ADVANCED
Bluetooth: controller: Kconfig option for advanced scheduling Add Kconfig option to enable advanced scheduling in the controller. Enable non-overlapping placement of observer, initiator and master roles in timespace. Uses window offset in connection updates and uses connection parameter request in slave role to negotiate non-overlapping placement with active master roles to avoid slave roles drifting into active master roles in the local controller. This feature maximizes the average data transmission amongst active concurrent master and slave connections while other observer, initiator, master or slave roles are active in the local controller. Disabling this feature will lead to overlapping role in timespace leading to skipped events amongst active roles. Change-id: I16e4e6c3ca99f93987ab86924af0cb9d76bdbc7e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 10:44:06 +02:00
bool "Advanced scheduling"
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_MAX_CONN != 0)
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
default y if !(BT_PERIPHERAL && !BT_CENTRAL)
Bluetooth: controller: Kconfig option for advanced scheduling Add Kconfig option to enable advanced scheduling in the controller. Enable non-overlapping placement of observer, initiator and master roles in timespace. Uses window offset in connection updates and uses connection parameter request in slave role to negotiate non-overlapping placement with active master roles to avoid slave roles drifting into active master roles in the local controller. This feature maximizes the average data transmission amongst active concurrent master and slave connections while other observer, initiator, master or slave roles are active in the local controller. Disabling this feature will lead to overlapping role in timespace leading to skipped events amongst active roles. Change-id: I16e4e6c3ca99f93987ab86924af0cb9d76bdbc7e Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-27 10:44:06 +02:00
help
Enable non-overlapping placement of observer, initiator and master
roles in timespace. Uses window offset in connection updates and uses
connection parameter request in slave role to negotiate
non-overlapping placement with active master roles to avoid slave
roles drifting into active master roles in the local controller.
This feature maximizes the average data transmission amongst active
concurrent master and slave connections while other observer,
initiator, master or slave roles are active in the local controller.
Disabling this feature will lead to overlapping role in timespace
leading to skipped events amongst active roles.
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
if BT_LL_SW_SPLIT
config BT_CTLR_LLL_PRIO
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
int "Lower Link Layer (Radio) IRQ priority"
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
range 0 3 if SOC_SERIES_NRF51X
range 0 6 if SOC_SERIES_NRF52X
default 0
help
The interrupt priority for event preparation and radio IRQ.
config BT_CTLR_ULL_HIGH_PRIO
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
int "Upper Link Layer High IRQ priority"
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
range BT_CTLR_LLL_PRIO 3 if SOC_SERIES_NRF51X
range BT_CTLR_LLL_PRIO 6 if SOC_SERIES_NRF52X
Bluetooth: controller: Fix ULL LLL execution priority selection Fix Kconfig default values for ULL and LLL execution priorities that caused build warnings when ranges changes based on other priority values being selected. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 11:59:45 +05:30
default BT_CTLR_LLL_PRIO
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
help
The interrupt priority for Ticker's Worker IRQ and Upper Link Layer
higher priority functions.
config BT_CTLR_ULL_LOW_PRIO
kconfig: Use a short consistent prompt style Same change as in commit 8cf8db3a73 ("Kconfig: Use a short, consistent style for prompts"), fixing stuff that got introduced since then. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-02-26 21:12:10 +01:00
int "Upper Link Layer Low IRQ priority"
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
range BT_CTLR_ULL_HIGH_PRIO 3 if SOC_SERIES_NRF51X
range BT_CTLR_ULL_HIGH_PRIO 6 if SOC_SERIES_NRF52X
Bluetooth: controller: Fix ULL LLL execution priority selection Fix Kconfig default values for ULL and LLL execution priorities that caused build warnings when ranges changes based on other priority values being selected. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-05-01 11:59:45 +05:30
default BT_CTLR_ULL_HIGH_PRIO
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
help
The interrupt priority for Ticker's Job IRQ and Upper Link Layer
lower priority functions.
config BT_CTLR_LOW_LAT
doc: fix docs, include, and Kconfig misspellings Fix misspellings missed during regular reviews Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2019-02-27 13:55:32 -08:00
bool "Low latency non-negotiating event preemption"
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
default y if SOC_SERIES_NRF51X
help
doc: fix docs, include, and Kconfig misspellings Fix misspellings missed during regular reviews Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2019-02-27 13:55:32 -08:00
Use low latency non-negotiating event preemption. This reduces
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
Radio ISR latencies by the controller event scheduling framework.
Consequently, this reduces on-air radio utilization due to redundant
radio state switches.
Bluetooth: controller: Implement low latency ULL processing Implement a lower ISR latency ULL processing design. Instead of looping use ISR/mayfly tail-chaining to process successive ULL messages. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-02-18 19:32:08 +05:30
config BT_CTLR_LOW_LAT_ULL
prompt "Low latency ULL"
bool
depends on BT_CTLR_LOW_LAT
default y
help
Low latency ULL implementation that uses tailchaining instead of while
loop to demux rx messages from LLL.
bluetooth: controller: Connection meta property support in LLL Added support for vendor specific meta data in LLL conn object. This enables vendors to add state data to connection, for supporting specialized BLE slave features. Signed-off-by: Morten Priess <mtpr@oticon.com>
2019-09-30 10:10:45 +02:00
config BT_CTLR_CONN_META
prompt "Enable connection meta data extension"
bool
help
Enables vendor specific per-connection meta data as part of the
LLL connection object.
bluetooth: controller: RX PDU meta data support in LLL Added support for vendor specific meta data in LLL node_rx_hdr. This enables vendors to add "footer" data to the RX PDU, for supporting specialized BLE features. Signed-off-by: Morten Priess <mtpr@oticon.com>
2019-09-27 09:14:23 +02:00
config BT_CTLR_RX_PDU_META
prompt "Enable RX pdu meta data"
bool
Bluetooth: controller: Introduce ULL LLL architecture This is a squash merge of commits introducing the new split Upper Link Layer and Lower Link Layer architecture of the Bluetooth Low Energy controller. This introduces a new, improved Link Layer based on the concept of split responsibilities; The Upper Link Layer (ULL) is in charge of control procedures, inter-event scheduling and overall role management. The code for the ULL is shared among all hardware implementations. The Lower Link Layer (LLL) is responsible for the intra-event scheduling and vendor specific radio hardware access. The communication between ULL and LLL is achieved through a set of FIFOs that contain both control and data packets. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Wolfgang Puffitsch <wopu@oticon.com> Signed-off-by: Morten Priess <mtpr@oticon.com>
2018-12-18 05:48:20 +01:00
endif # BT_LL_SW_SPLIT
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_RADIO_ENABLE_FAST
Bluetooth: controller: Add radio fast ramp feature Added implementation to use nRF radio's fast ramp up mode. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-26 13:01:29 +02:00
bool "Use tTXEN/RXEN,FAST ramp-up"
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
depends on SOC_COMPATIBLE_NRF52X
Bluetooth: controller: Fix to enable Asym PHY on nRF52 Series Fix the controller Kconfig to enable use of fast radio ramp up by default, hence enabling support for Asym PHY updates by default on nRF52 Series SoCs. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-10-30 13:55:58 +01:00
default y
Bluetooth: controller: Add radio fast ramp feature Added implementation to use nRF radio's fast ramp up mode. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-26 13:01:29 +02:00
help
Enable use of fast radio ramp-up mode.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_TIFS_HW
Bluetooth: controller: Introduce s/w based TRX switching Introduce alternative TRX switching using dedicated timers and peripheral interconnect. This will enable the possibility to independently configure the Tx and Rx settings between the tIFS. Note, this will also provide the opportunity to design a soft realtime Radio ISR. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-01 05:52:57 +02:00
bool "H/w Accelerated tIFS Trx switching"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on !BT_CTLR_RADIO_ENABLE_FAST
Bluetooth: controller: Introduce s/w based TRX switching Introduce alternative TRX switching using dedicated timers and peripheral interconnect. This will enable the possibility to independently configure the Tx and Rx settings between the tIFS. Note, this will also provide the opportunity to design a soft realtime Radio ISR. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-05-01 05:52:57 +02:00
default y
help
Enable use of hardware accelerated tIFS Trx switching.
Bluetooth: controller: implement sw-switch with the event timer This commit contributes the implementation of the sw-switch for tIFS in nRF5 Radio using the EVENT_TIMER instead of a dedicated TIMER instance. A Kconfig configuration is added so the user can select whether to use the EVENT_TIMER for the tIFS switch or use a dedicated TIMER instance. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-31 14:02:19 +01:00
config BT_CTLR_SW_SWITCH_SINGLE_TIMER
bool "Single TIMER tIFS Trx SW switching"
Bluetooth: Use new nrf COMPATIBLE options To allow the BLE stack to be used both in the real nRF platforms and simulated ones, change the used macros in the code to the COMPATIBLE ones. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2018-10-03 16:37:18 +02:00
depends on (!BT_CTLR_TIFS_HW) && SOC_COMPATIBLE_NRF52X
Bluetooth: controller: implement sw-switch with the event timer This commit contributes the implementation of the sw-switch for tIFS in nRF5 Radio using the EVENT_TIMER instead of a dedicated TIMER instance. A Kconfig configuration is added so the user can select whether to use the EVENT_TIMER for the tIFS switch or use a dedicated TIMER instance. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-31 14:02:19 +01:00
help
Implement the tIFS Trx SW switch with the same TIMER
instance, as the one used for BLE event timing. Requires
SW switching be enabled. Using a single TIMER:
(+) frees up one TIMER instance
(+) removes jitter for HCTO implementation
(-) introduces drifting to the absolute time inside BLE
events, that increases linearly with the number of
bluetooth: controller: nrf5: Use pre-programmed PPI channels Several PPI channels in nRF5 family SoCs are pre-programmed with fixed settings. A few of them can be used in the bluetooth controller instead of the freely programmable ones that are used currently. This commit makes such replacements where possible so that the universal channels can be left available for other purposes. This commit also removes macros used previously in calls to functions enabling and disabling particular PPI channels (as it is sufficient to use the BIT macro to set bits corresponding to the channel numbers) to prevent such problems like the one introduces by commit 9d1ca9c3906b5cb54e2416f2f1a7fae6797246df (channel 18 changed to 17 but the related macro definition not updated). Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2018-10-01 16:00:19 +02:00
packets exchanged in the event
(-) makes it impossible to use most of the pre-programmed
PPI channels for the controller, resulting in 4 channels
less left for other uses
Bluetooth: controller: implement sw-switch with the event timer This commit contributes the implementation of the sw-switch for tIFS in nRF5 Radio using the EVENT_TIMER instead of a dedicated TIMER instance. A Kconfig configuration is added so the user can select whether to use the EVENT_TIMER for the tIFS switch or use a dedicated TIMER instance. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-31 14:02: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
if BT_CONN
Bluetooth: controller: Conditionally include conn-related options Only include connection-related options when CONFIG_BLUETOOTH_CONN is selected, since otherwise this can lead to inconsistencies between features and supported commands. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 09:58:59 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_FAST_ENC
Bluetooth: Controller: Kconfig fast encryption setup feature Enable connection encryption setup in 3 connection intervals. Peripheral will respond to Encryption Request with Encryption Response in the same connection interval, and also, will respond with Start Encryption Response PDU in the 3rd connection interval, hence completing encryption setup in 3 connection intervals. Encrypted data would be transmitted as fast as in 3rd connection interval from the connection establishment. Maximum CPU time in Radio ISR will increase if this feature is selected. Change-id: I16f2863fc2aaed624826505739519d4de1ac44c5 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-30 06:51:17 +01:00
bool "Fast Encryption Setup"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on BT_CTLR_LE_ENC
Bluetooth: controller: Enable Fast Enc and RSSI features Enable the Fast Encryption design and connection RSSI measurement when CONFIG_BT_HCI_RAW is selected. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-07-03 19:03:34 +05:30
default y if BT_HCI_RAW
Bluetooth: Controller: Kconfig fast encryption setup feature Enable connection encryption setup in 3 connection intervals. Peripheral will respond to Encryption Request with Encryption Response in the same connection interval, and also, will respond with Start Encryption Response PDU in the 3rd connection interval, hence completing encryption setup in 3 connection intervals. Encrypted data would be transmitted as fast as in 3rd connection interval from the connection establishment. Maximum CPU time in Radio ISR will increase if this feature is selected. Change-id: I16f2863fc2aaed624826505739519d4de1ac44c5 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-30 06:51:17 +01:00
help
Enable connection encryption setup in 3 connection intervals.
Peripheral will respond to Encryption Request with Encryption Response
in the same connection interval, and also, will respond with Start
Encryption Response PDU in the 3rd connection interval, hence
completing encryption setup in 3 connection intervals. Encrypted data
would be transmitted as fast as in 3rd connection interval from the
connection establishment.
Maximum CPU time in Radio ISR will increase if this feature is
selected.
Bluetooth: controller: Fix handling zero length L2CAP start frame Added a fix handling L2CAP start frame with payload length of zero which otherwise sent zero length data start PDU on air. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-06-25 17:58:29 +05:30
config BT_CTLR_LLID_DATA_START_EMPTY
bool "Handle zero length L2CAP start frame"
default y if BT_HCI_RAW
help
Handle zero length L2CAP start frame.
Bluetooth: controller: Add deferred procedure complete event Added implementation to defer procedure complete event until actual on-air connection event instant. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-07-03 19:09:44 +05:30
config BT_CTLR_RX_ENQUEUE_HOLD
bool "Procedure Complete after on-air instant"
default y if BT_HCI_RAW
help
Hold enqueue of Procedure Complete events with instant until after the
on-air instant is reached.
Bluetooth: controller: Avoid retransmission of NACK-ed Tx PDU Added implementation to avoid retransmitting NACK-ed Tx PDU, to save on current consumption in retrying to transmit in case peer device has no free buffer to receive the PDU. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-08-17 11:42:22 +02:00
config BT_CTLR_TX_RETRY_DISABLE
bool "Disable Tx Retry"
help
Avoid retransmission of a PDU if peer device Nack-ed a transmission
in the current connection event, close the connection event so as to
save current consumption on retries (in case peer has no buffers to
receive new PDUs).
Enabling this will lower power consumption, but increase transmission
latencies by one connection interval as the next attempt to send a PDU
would happen in the next connection event instead of repeated retries
in the current connection event.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_CONN_RSSI
Bluetooth: Controller: Kconfig connection RSSI measurement Add Kconfig configuration and conditional compilation of RSSI measurement during a connection. Change-id: I5a2f23f76a7cbbd9569d53d31899a472bf39d3ee Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-29 17:07:54 +01:00
bool "Connection RSSI"
Bluetooth: controller: Enable Fast Enc and RSSI features Enable the Fast Encryption design and connection RSSI measurement when CONFIG_BT_HCI_RAW is selected. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-07-03 19:03:34 +05:30
default y if BT_HCI_RAW
Bluetooth: Controller: Kconfig connection RSSI measurement Add Kconfig configuration and conditional compilation of RSSI measurement during a connection. Change-id: I5a2f23f76a7cbbd9569d53d31899a472bf39d3ee Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-29 17:07:54 +01:00
help
Enable connection RSSI measurement.
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: controller: Conditionally include conn-related options Only include connection-related options when CONFIG_BLUETOOTH_CONN is selected, since otherwise this can lead to inconsistencies between features and supported commands. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-05-29 09:58:59 +02:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_ADV_INDICATION
Bluetooth: Controller: Add advertisement event indication feature Add a Controller event that indicates everytime advertisement event has been transmitted on air. Change-id: I4722488bbfeca987e66983faf5b26467407a89c9 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-10 11:53:38 +01:00
bool "Advertisement indications"
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
depends on BT_BROADCASTER
Bluetooth: Controller: Add advertisement event indication feature Add a Controller event that indicates everytime advertisement event has been transmitted on air. Change-id: I4722488bbfeca987e66983faf5b26467407a89c9 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-10 11:53:38 +01:00
help
Generate events indicating on air advertisement events.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_SCAN_REQ_NOTIFY
Bluetooth: controller: Scan Request Notifications Implement the framework for LE Scan Request Received Event. The feature is available under the Controller's advanced features and will be selected implcitly when Bluetooth v5.0 LE Advertising Extensions feature is implemented. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-27 11:29:35 +02:00
bool "Scan Request Notifications"
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
depends on BT_BROADCASTER
Bluetooth: controller: Scan Request Notifications Implement the framework for LE Scan Request Received Event. The feature is available under the Controller's advanced features and will be selected implcitly when Bluetooth v5.0 LE Advertising Extensions feature is implemented. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-27 11:29:35 +02:00
help
Generate events notifying the on air scan requests received.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_SCAN_REQ_RSSI
Bluetooth: controller: Scan Request Notifications Implement the framework for LE Scan Request Received Event. The feature is available under the Controller's advanced features and will be selected implcitly when Bluetooth v5.0 LE Advertising Extensions feature is implemented. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-27 11:29:35 +02:00
bool "Measure Scan Request RSSI"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
depends on BT_CTLR_SCAN_REQ_NOTIFY
Bluetooth: controller: Scan Request Notifications Implement the framework for LE Scan Request Received Event. The feature is available under the Controller's advanced features and will be selected implcitly when Bluetooth v5.0 LE Advertising Extensions feature is implemented. Jira: ZEP-2073 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-04-27 11:29:35 +02:00
help
Measure RSSI of the on air scan requests received.
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 10:46:13 +01:00
config BT_CTLR_SCAN_INDICATION
bool "Scanner indications"
depends on BT_OBSERVER
help
Generate events indicating on air scanner events.
Bluetooth: controller: Moved advanced settings in Kconfig Moved some user defined Kconfig constants to advanced settings menu. Signed-off-by: Asger Munk Nielsen <asmk@oticon.com>
2019-05-28 10:53:05 +02:00
config BT_MAYFLY_YIELD_AFTER_CALL
bool "Yield from mayfly thread after first call"
default y
help
Only process one mayfly callback per invocation (legacy behavior).
If set to 'n', all pending mayflies for callee are executed before
yielding
bluetooth: controller: Revised ticker for improved conflict resolution Changed ticker behavior to resolve conflicts in ticker_worker instead of in ticker_job. This allows better real-time slot allocation, as well as allowing callbacks even if ticker node doesn't get air-time (for audio stream housekeeping). A priority property now also allows prioritizing one ticker node over others. Compatibility mode enables lagacy ticker behavior if needed. Signed-off-by: Morten Priess <mtpr@oticon.com>
2019-08-07 11:12:26 +02:00
config BT_TICKER_COMPATIBILITY_MODE
bool "Ticker compatibility mode"
Bluetooth: controller: Fix legacy for TICKER_COMPATABILITY_MODE When not using ticker compatibility mode in legacy controller, ticker job should not be disabled inside radio events. Ticker compatibility mode was introduced in commit 3a9173afe151 ("bluetooth: controller: Revised ticker for improved conflict resolution"). Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-09-12 08:37:32 +05:30
default y if SOC_SERIES_NRF51X || BT_LL_SW_LEGACY
bluetooth: controller: Revised ticker for improved conflict resolution Changed ticker behavior to resolve conflicts in ticker_worker instead of in ticker_job. This allows better real-time slot allocation, as well as allowing callbacks even if ticker node doesn't get air-time (for audio stream housekeeping). A priority property now also allows prioritizing one ticker node over others. Compatibility mode enables lagacy ticker behavior if needed. Signed-off-by: Morten Priess <mtpr@oticon.com>
2019-08-07 11:12:26 +02:00
help
This option enables legacy ticker scheduling which defers overlapping
ticker node timeouts and thereby prevents ticker interrupts during
radio RX/TX. Enabling this option disables the ticker priority- and
'must expire' features.
Bluetooth: controller: Moved advanced settings in Kconfig Moved some user defined Kconfig constants to advanced settings menu. Signed-off-by: Asger Munk Nielsen <asmk@oticon.com>
2019-05-28 10:53:05 +02:00
config BT_CTLR_USER_EXT
prompt "Enable proprietary extensions in Controller"
Bluetooth: controller: BT_CTLR_USER_EXT depends on BT_LL_SW_SPLIT Make the Kconfig option BT_CTLR_USER_EXT depend on BT_LL_SW_SPLIT. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-06-07 16:24:08 +02:00
depends on BT_LL_SW_SPLIT
Bluetooth: controller: Moved advanced settings in Kconfig Moved some user defined Kconfig constants to advanced settings menu. Signed-off-by: Asger Munk Nielsen <asmk@oticon.com>
2019-05-28 10:53:05 +02:00
bool
help
Catch-all for enabling proprietary event types in Controller behavior.
config BT_CTLR_USER_EVT_RANGE
doc: fix Kconfig misspellings Fix misspellings in Kconfig files missed during regular reviews. Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2019-06-18 10:38:23 -07:00
int "Range of event constants reserved for proprietary event types"
Bluetooth: controller: Moved advanced settings in Kconfig Moved some user defined Kconfig constants to advanced settings menu. Signed-off-by: Asger Munk Nielsen <asmk@oticon.com>
2019-05-28 10:53:05 +02:00
depends on BT_CTLR_USER_EXT
default 5
range 0 10
help
Number of event types reserved for proprietary use. The range
is typically used when BT_CTLR_USER_EXT is in use.
config BT_RX_USER_PDU_LEN
int "Maximum supported proprietary PDU buffer length"
depends on BT_CTLR_USER_EXT
default 2
range 2 255
help
Maximum data size for each proprietary PDU. This size includes link layer
header and payload. It does not account for HCI event headers as these
PDUs are assumed to not go across HCI.
Bluetooth: controller: Hide advance features in Kconfig Added a explicit Kconfig option to show the Controller's advanced feature configurations. These feature configurations need specific in-depth Controller implementation knowledge and should not overwhelm normal users of the Controller. Change-id: Iae764f2b266b199cf180936c51c7a4ea089ee510 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2017-03-28 00:25:14 +02:00
endmenu
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
comment "BLE Controller hardware configuration"
menuconfig BT_CTLR_GPIO_PA
bool "Power Amplifier GPIO interface"
Bluetooth: controller: Disable PA/LNA for nRF51x The PA/LNA feature is not functional on nRF51x series due to added interrupt latency. Disable this feature unconditionally for those ICs to avoid unexpected behavior. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-10-02 11:18:04 +02:00
depends on !SOC_SERIES_NRF51X
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
help
Enable GPIO interface to a Power Amplifier. This allows hardware
designs using PA to let the Controller toggle their state based on
radio activity.
if BT_CTLR_GPIO_PA
config BT_CTLR_GPIO_PA_PIN
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Power Amplifier GPIO pin number"
Bluetooth: controller: Add PA/LNA support on NRF_P1 GPIO pins Added support for using NRF_P1 GPIO pins on nRF52840 SoC. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-06-25 02:28:08 +02:00
range 0 47 if SOC_NRF52840
range 0 31
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
help
GPIO Pin number connected to a Power Amplifier.
config BT_CTLR_GPIO_PA_POL_INV
bool "Inverted polarity for the PA pin"
help
Enable inverted polarity (active low) for the PA pin.
config BT_CTLR_GPIO_PA_OFFSET
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Time from PA ON to Tx ready"
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
default 5
range 0 10
help
Time before Tx ready to turn on PA.
endif # BT_CTLR_GPIO_PA
menuconfig BT_CTLR_GPIO_LNA
bool "Low Noise Amplifier GPIO interface"
Bluetooth: controller: Disable PA/LNA for nRF51x The PA/LNA feature is not functional on nRF51x series due to added interrupt latency. Disable this feature unconditionally for those ICs to avoid unexpected behavior. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-10-02 11:18:04 +02:00
depends on !SOC_SERIES_NRF51X
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
help
Enable GPIO interface to a Low Noise Amplifier. This allows hardware
designs using LNAs to let the Controller toggle their state based on
radio activity.
if BT_CTLR_GPIO_LNA
config BT_CTLR_GPIO_LNA_PIN
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Low Noise Amplifier GPIO pin number"
Bluetooth: controller: Add PA/LNA support on NRF_P1 GPIO pins Added support for using NRF_P1 GPIO pins on nRF52840 SoC. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-06-25 02:28:08 +02:00
range 0 47 if SOC_NRF52840
range 0 31
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
help
GPIO Pin number connected to a Low Noise Amplifier.
config BT_CTLR_GPIO_LNA_POL_INV
bool "Inverted polarity for the LNA pin"
help
Enable inverted polarity (active low) for the LNA pin.
config BT_CTLR_GPIO_LNA_OFFSET
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
int "Time from LNA ON to Rx ready"
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
default 5
range 0 10
help
Time before Rx ready to turn on LNA.
endif # BT_CTLR_GPIO_LNA
config BT_CTLR_PA_LNA_GPIOTE_CHAN
# Hidden "nRF5 GPIO PA/LNA GPIOTE Channel"
int
subsys: kconfig: Remove 'default n' properties and clean up a bit Bool symbols implicitly default to 'n'. A 'default n' can make sense e.g. in a Kconfig.defconfig file, if you want to override a 'default y' on the base definition of the symbol. It isn't used like that on any of these symbols though. Remove some 'default ""' properties on string symbols too. Also make definitions more consistent by converting some config FOO <type> prompt "foo" definitions to a shorter form: config FOO <type> "foo" This shorthand works for int/hex/string symbols too, not just for bool symbols. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-12 13:26:29 +02:00
depends on SOC_FAMILY_NRF && (BT_CTLR_GPIO_PA || BT_CTLR_GPIO_LNA)
drivers: gpio: nrf5: Fix GPIOTE channel use overlap Fixes issues caused in GPIO driver due to overlapping GPIOTE channel use in nRF5 software PWM driver and in Bluetooth controller for implementing PA/LNA feature. The issue is solved by assigning the base and available channel count for GPIOTE considering whether PWM and/or PA/LNA feature is selected in the Kconfig. Fixes #8815. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-07-10 08:02:16 +02:00
default 3 if PWM_NRF5_SW
Kconfig: Use the first default with a satisfied condition Up until now, Zephyr has patched Kconfig to use the last 'default' with a satisfied condition, instead of the first one. I'm not sure why the patch was added (it predates Kconfiglib), but I suspect it's related to Kconfig.defconfig files. There are at least three problems with the patch: 1. It's inconsistent with how Kconfig works in other projects, which might confuse newcomers. 2. Due to oversights, earlier 'range' properties are still preferred, as well as earlier 'default' properties on choices. In addition to being inconsistent, this makes it impossible to override 'range' properties and choice 'default' properties if the base definition of the symbol/choice already has 'range'/'default' properties. I've seen errors caused by the inconsistency, and I suspect there are more. 3. A fork of Kconfiglib that adds the patch needs to be maintained. Get rid of the patch and go back to standard Kconfig behavior, as follows: 1. Include the Kconfig.defconfig files first instead of last in Kconfig.zephyr. 2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of last in arch/Kconfig. 3. Include arch/<arch>/soc/*/Kconfig first instead of last in arch/<arch>/Kconfig. 4. Swap a few other 'source's to preserve behavior for some scattered symbols with multiple definitions. Swap 'source's in some no-op cases too, where it might match the intent. 5. Reverse the defaults on symbol definitions that have more than one default. Skip defaults that are mutually exclusive, e.g. where each default has an 'if <some board>' condition. They are already safe. 6. Remove the prefer-later-defaults patch from Kconfiglib. Testing was done with a Python script that lists all Kconfig symbols/choices with multiple defaults, along with a whitelist of fixed symbols. The script also verifies that there are no "unreachable" defaults hidden by defaults without conditions As an additional test, zephyr/.config was generated before and after the change for several samples and checked to be identical (after sorting). This commit includes some default-related cleanups as well: - Simplify some symbol definitions, e.g. where a default has 'if FOO' when the symbol already has 'depends on FOO'. - Remove some redundant 'default ""' for string symbols. This is the implicit default. Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and BT_L2CAP_TX_MTU (caused by confusing inconsistency). Piggyback some fixes for style nits too, e.g. unindented help texts. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
default 0
Bluetooth: controller: Add PA/LNA GPIO Kconfig option Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-09-15 15:09:53 +02:00
help
Select the nRF5 GPIOTE channel to use for PA/LNA GPIO feature.
Bluetooth: Controller: Kconfig radio ISR profiling Add Kconfig configuration and conditional compilation of radio ISR profiling. Change-id: Ia80d6bc54810156be99b2e6a25327c30d0714697 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-27 19:23:32 +01:00
comment "BLE Controller debug configuration"
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_ASSERT_HANDLER
Bluetooth: controller: Rename assert handler Kconfig title Renames the "Blueooth Controller Assertion Handler" to "Application Defined Assertion Handler" to better fit the purpose of the Kconfig option. Signed-off-by: Thomas Stenersen <thomas.stenersen@nordicsemi.no>
2019-07-01 16:31:43 +02:00
bool "Application Defined Assertion Handler"
Bluetooth: Controller: Add ASSERT info dump on HCI builds When building Zephyr in the controller-only configuration, assertions that happen in the Link Layer code are not visible to the Host which is running on another HCI and connected via UART or USB to it. This patch allows the Controller code to output the assertion line number when in such a configuration, allowing the Host to view the event to help debugging. The event format used is temporary and will be replaced by a standardized Vendor Specific specification to come at a later time. Change-Id: I013ca6783a3fdedc47b171132919dd4798c66285 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-10-31 11:39:12 +01:00
help
This option enables an application-defined sink for the
controller assertion mechanism. This must be defined in
Bluetooth: Controller: Typo in Kconfig Changed documentation in Bluetooth Controller Kconfig for BT_CTLR_ASSERT_HANDLER Signed-off-by: Kristoffer Rist Skøien <kristoffer.skoien@nordicsemi.no>
2019-09-10 09:25:33 +02:00
application code as void \"bt_ctlr_assert_handle(char \*, int)\"
Bluetooth: Controller: Add ASSERT info dump on HCI builds When building Zephyr in the controller-only configuration, assertions that happen in the Link Layer code are not visible to the Host which is running on another HCI and connected via UART or USB to it. This patch allows the Controller code to output the assertion line number when in such a configuration, allowing the Host to view the event to help debugging. The event format used is temporary and will be replaced by a standardized Vendor Specific specification to come at a later time. Change-Id: I013ca6783a3fdedc47b171132919dd4798c66285 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-10-31 11:39:12 +01:00
and will be invoked whenever the controller code encounters
an unrecoverable error.
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_PROFILE_ISR
Bluetooth: Controller: Kconfig radio ISR profiling Add Kconfig configuration and conditional compilation of radio ISR profiling. Change-id: Ia80d6bc54810156be99b2e6a25327c30d0714697 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-12-27 19:23:32 +01:00
bool "Profile radio ISR"
help
Turn on measurement of radio ISR latency, CPU usage and generation of
controller event with these profiling data. The controller event
contains current, minimum and maximum ISR entry latencies; and
current, minimum and maximum ISR CPU use in micro-seconds.
Bluetooth: Controller: Add ASSERT info dump on HCI builds When building Zephyr in the controller-only configuration, assertions that happen in the Link Layer code are not visible to the Host which is running on another HCI and connected via UART or USB to it. This patch allows the Controller code to output the assertion line number when in such a configuration, allowing the Host to view the event to help debugging. The event format used is temporary and will be replaced by a standardized Vendor Specific specification to come at a later time. Change-Id: I013ca6783a3fdedc47b171132919dd4798c66285 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-10-31 11:39:12 +01:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
config BT_CTLR_DEBUG_PINS
Bluetooth: controller: Introduce debug pins Kconfig option A new Kconfig debug option now controls the usage of pin toggling to debug the BLE controller. Change-Id: I24c5c13ca71e3395e10f14e27ad4bca9f2e94687 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-02-21 10:29:39 +01:00
bool "Bluetooth Controller Debug Pins"
Bluetooth: controller: Add support for the nRF52810 The nRF52810 is a low-cost variant of the nRF52832, with a reduced set of peripherals and memory. This commit adds Bluetooth controller support for it. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-06-26 23:38:03 +02:00
depends on BOARD_NRF51_PCA10028 || BOARD_NRF52_PCA10040 || BOARD_NRF52810_PCA10040 || BOARD_NRF52840_PCA10056
Bluetooth: controller: Introduce debug pins Kconfig option A new Kconfig debug option now controls the usage of pin toggling to debug the BLE controller. Change-Id: I24c5c13ca71e3395e10f14e27ad4bca9f2e94687 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-02-21 10:29:39 +01:00
help
Turn on debug GPIO toggling for the BLE Controller. This is useful
when debugging with a logic analyzer or profiling certain sections of
Bluetooth: controller: Fix BT_CTLR_DEBUG_PINS Kconfig help text Help text for BT_CTLR_DEBUG_PINS incorrectly mentioned specific GPIO pins being reserved for this feature, but in reality the pins reserved vary on the SoC selected, hence any specific mention of pin details is removed from help text. Fixes: #5499 Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-01-23 23:58:41 +01:00
the code.
Bluetooth: controller: Introduce debug pins Kconfig option A new Kconfig debug option now controls the usage of pin toggling to debug the BLE controller. Change-Id: I24c5c13ca71e3395e10f14e27ad4bca9f2e94687 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-02-21 10:29:39 +01:00
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 13:45:13 +02:00
endif # BT_CTLR
Copy permalink