2017-03-31 03:50:49 +02:00
|
|
|
# Kconfig - Bluetooth Controller configuration options
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2016-2017 Nordic Semiconductor ASA
|
|
|
|
|
#
|
|
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
#
|
2016-08-15 12:01:06 +02:00
|
|
|
|
2017-03-31 03:50:49 +02:00
|
|
|
comment "BLE Controller support"
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR
|
2017-03-31 03:50:49 +02:00
|
|
|
bool "Bluetooth Controller"
|
|
|
|
|
help
|
|
|
|
|
Enables support for SoC native controller implementations.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
if BT_CTLR
|
2016-08-15 12:01:06 +02:00
|
|
|
|
2018-09-24 17:08:04 +02:00
|
|
|
choice BT_LL_CHOICE
|
2017-03-14 10:48:59 +01:00
|
|
|
prompt "Bluetooth Link Layer Selection"
|
2017-08-09 09:21:11 +03:00
|
|
|
default BT_LL_SW
|
2017-03-14 10:48:59 +01:00
|
|
|
help
|
|
|
|
|
Select the Bluetooth Link Layer to compile.
|
|
|
|
|
|
2017-08-09 09:21:11 +03:00
|
|
|
config BT_LL_SW
|
2018-01-09 15:17:15 +01:00
|
|
|
bool "Software-based BLE Link Layer"
|
2018-06-26 14:03:34 +02:00
|
|
|
select BT_RECV_IS_RX_THREAD
|
2018-02-21 11:48:35 +01:00
|
|
|
select ENTROPY_GENERATOR
|
2018-03-19 13:51:25 +01:00
|
|
|
select ENTROPY_NRF5_RNG if SOC_FAMILY_NRF
|
|
|
|
|
select ENTROPY_NRF5_BIAS_CORRECTION if SOC_FAMILY_NRF
|
2017-03-14 10:48:59 +01:00
|
|
|
help
|
2017-04-21 10:55:27 -07:00
|
|
|
Use Zephyr software BLE Link Layer implementation.
|
2017-03-14 10:48:59 +01:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2017-03-31 03:50:49 +02:00
|
|
|
comment "BLE Controller configuration"
|
|
|
|
|
|
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.
|
|
|
|
|
|
2018-01-09 15:17:15 +01:00
|
|
|
config BT_CTLR_RX_PRIO_STACK_SIZE
|
|
|
|
|
# Hidden option for Controller's Co-Operative high priority Rx thread
|
|
|
|
|
# stack size.
|
|
|
|
|
int
|
|
|
|
|
default 448
|
|
|
|
|
|
|
|
|
|
config BT_CTLR_RX_PRIO
|
|
|
|
|
# Hidden option for Controller's Co-Operative high priority Rx thread
|
|
|
|
|
# priority.
|
|
|
|
|
int
|
|
|
|
|
default 6
|
|
|
|
|
|
|
|
|
|
config BT_CTLR_FILTER
|
|
|
|
|
# Hidden option to enable controller whitelist feature
|
|
|
|
|
depends on BT_LL_SW
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
2017-09-25 14:19:18 +02:00
|
|
|
config BT_CTLR_HCI_VS_BUILD_INFO
|
|
|
|
|
string "Zephyr HCI VS Build Info string"
|
|
|
|
|
default ""
|
2017-10-03 14:37:06 +02:00
|
|
|
depends on BT_HCI_VS_EXT
|
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.
|
|
|
|
|
|
2018-01-09 15:17:15 +01:00
|
|
|
if BT_LL_SW
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_DUP_FILTER_LEN
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Number of addresses in the scan duplicate filter"
|
2017-08-09 09:21:11 +03:00
|
|
|
depends on BT_OBSERVER
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_RX_BUFFERS
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Number of Rx buffers"
|
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
|
2017-05-15 11:10:47 +02:00
|
|
|
range 1 18
|
2016-08-15 12:01:06 +02:00
|
|
|
help
|
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.
|
2016-08-15 12:01:06 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_TX_BUFFERS
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Number of Tx buffers"
|
2017-08-09 09:21:11 +03:00
|
|
|
default 7 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 2
|
2017-05-15 11:10:47 +02:00
|
|
|
range 1 19
|
2016-08-15 12:01:06 +02:00
|
|
|
help
|
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.
|
2016-08-15 12:01:06 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_TX_BUFFER_SIZE
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Tx buffer size"
|
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
|
2017-04-20 12:00:29 -05:00
|
|
|
u16_t for size/length variables).
|
2016-12-30 06:24:42 +01:00
|
|
|
|
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"
|
|
|
|
|
depends on SOC_SERIES_NRF52X
|
|
|
|
|
|
|
|
|
|
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"
|
|
|
|
|
depends on SOC_SERIES_NRF52X
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_COMPANY_ID
|
2018-07-12 13:26:29 +02:00
|
|
|
hex "Company Id"
|
2018-03-02 12:47:09 +01:00
|
|
|
default 0x05F1
|
2017-03-10 12:16:58 +01:00
|
|
|
range 0x0000 0xFFFF
|
|
|
|
|
help
|
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
|
2017-03-10 12:16:58 +01:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_SUBVERSION_NUMBER
|
2018-07-12 13:26:29 +02:00
|
|
|
hex "Subversion Number"
|
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.
|
|
|
|
|
|
2017-03-28 00:37:05 +02:00
|
|
|
comment "BLE Controller features"
|
|
|
|
|
|
2017-08-09 09:21:11 +03:00
|
|
|
if BT_CONN
|
2017-05-29 09:58:59 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_LE_ENC
|
2018-07-24 18:58:38 +02:00
|
|
|
bool "LE Encryption"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on !BT_CTLR_DATA_LENGTH_CLEAR && !BT_CTLR_PHY_2M_NRF
|
2017-05-30 00:12:10 +02:00
|
|
|
default y
|
2018-07-24 18:58:38 +02:00
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth v4.0 LE Encryption feature in the
|
|
|
|
|
Controller.
|
2017-05-30 00:12:10 +02:00
|
|
|
|
2017-03-13 11:17:36 +01:00
|
|
|
config BT_CTLR_CONN_PARAM_REQ
|
|
|
|
|
bool "Connection Parameter Request"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth v4.1 Connection Parameter Request feature
|
|
|
|
|
in the Controller.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_LE_PING
|
2016-12-28 05:34:37 +01:00
|
|
|
bool "LE Ping"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth v4.1 LE Ping feature in the Controller.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_PRIVACY
|
2017-06-13 18:26:27 +02:00
|
|
|
bool "LE Controller-based Privacy"
|
2017-09-05 10:55:48 +02:00
|
|
|
depends on !SOC_SERIES_NRF51X
|
2017-06-13 18:26:27 +02:00
|
|
|
default y
|
2017-08-09 09:21:11 +03:00
|
|
|
select BT_RPA
|
2017-06-13 18:26:27 +02:00
|
|
|
help
|
2017-08-15 12:37:04 +02:00
|
|
|
Enable support for Bluetooth v4.2 LE Controller-based Privacy feature
|
|
|
|
|
in the Controller.
|
2017-06-13 18:26:27 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_RL_SIZE
|
2018-07-12 13:26:29 +02:00
|
|
|
int "LE Controller-based Privacy Resolving List size"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on BT_CTLR_PRIVACY
|
2017-06-13 18:26:27 +02:00
|
|
|
default 8
|
2018-03-19 13:51:25 +01:00
|
|
|
range 1 8 if SOC_FAMILY_NRF
|
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.
|
|
|
|
|
|
2017-08-15 12:37:04 +02:00
|
|
|
config BT_CTLR_EXT_SCAN_FP
|
|
|
|
|
bool "LE Extended Scanner Filter Policies"
|
2018-06-27 16:07:38 +02:00
|
|
|
depends on BT_OBSERVER
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_DATA_LENGTH
|
2016-12-28 06:35:05 +01:00
|
|
|
bool "Data Length Update"
|
2017-09-06 09:09:19 +02:00
|
|
|
default y if SOC_SERIES_NRF52X
|
2016-12-28 06:35:05 +01:00
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth v4.2 LE Data Length Update procedure in
|
|
|
|
|
the Controller.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_DATA_LENGTH_MAX
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Maximum data length supported"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on BT_CTLR_DATA_LENGTH
|
2016-12-28 06:35:05 +01:00
|
|
|
default 27
|
2017-08-14 13:45:13 +02:00
|
|
|
range 27 251 if SOC_SERIES_NRF52X || BT_CTLR_DATA_LENGTH_CLEAR
|
2017-05-30 00:44:19 +02:00
|
|
|
range 27 27
|
2016-12-28 06:35:05 +01:00
|
|
|
help
|
|
|
|
|
Set the maximum data length of PDU supported in the Controller.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_PHY
|
2017-04-29 06:50:52 +02:00
|
|
|
bool "PHY Update"
|
2017-09-06 09:09:19 +02:00
|
|
|
default y if SOC_SERIES_NRF52X
|
2017-04-29 06:50:52 +02:00
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth 5.0 PHY Update Procedure in the
|
|
|
|
|
Controller.
|
|
|
|
|
|
2017-08-09 09:21:11 +03:00
|
|
|
endif # BT_CONN
|
2017-04-26 14:41:23 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_CHAN_SEL_2
|
2017-04-06 05:12:44 +02:00
|
|
|
bool "Channel Selection Algorithm #2"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth 5.0 LE Channel Selection Algorithm #2 in
|
|
|
|
|
the Controller.
|
|
|
|
|
|
2017-08-18 13:46:49 +02:00
|
|
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_ADV_EXT
|
2017-04-26 14:41:23 +02:00
|
|
|
bool "LE Advertising Extensions"
|
2017-08-14 13:45:13 +02:00
|
|
|
select BT_CTLR_SCAN_REQ_NOTIFY
|
|
|
|
|
select BT_CTLR_CHAN_SEL_2
|
2017-04-26 14:41:23 +02:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth 5.0 LE Advertising Extensions in the
|
|
|
|
|
Controller.
|
2017-05-29 09:58:59 +02:00
|
|
|
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_ADVANCED_FEATURES
|
2017-03-28 00:25:14 +02:00
|
|
|
bool "Show advanced features"
|
|
|
|
|
help
|
|
|
|
|
Makes advanced features visible to controller developers.
|
|
|
|
|
|
|
|
|
|
menu "Advanced features"
|
2017-08-14 13:45:13 +02:00
|
|
|
visible if BT_CTLR_ADVANCED_FEATURES
|
2017-03-28 00:25:14 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_DATA_LENGTH_CLEAR
|
2017-05-30 00:44:19 +02:00
|
|
|
bool "Data Length Support (Cleartext only)"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on BT_CTLR_DATA_LENGTH && SOC_SERIES_NRF51X
|
2017-05-30 00:44:19 +02:00
|
|
|
help
|
2017-06-12 15:48:38 -07:00
|
|
|
Enable support for Bluetooth v4.2 LE Data Length Update procedure, up to
|
2017-05-30 00:44:19 +02:00
|
|
|
251 byte cleartext payloads in the Controller. Encrypted connections
|
|
|
|
|
are not supported.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
if BT_CTLR_PHY
|
2017-04-29 06:50:52 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_PHY_2M
|
2017-04-29 06:50:52 +02:00
|
|
|
bool "2Mbps PHY Support"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on !SOC_SERIES_NRF51X || BT_CTLR_PHY_2M_NRF
|
2017-04-29 06:50:52 +02:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth 5.0 2Mbps PHY in the Controller.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_PHY_2M_NRF
|
2017-05-30 00:44:19 +02:00
|
|
|
bool "2Mbps Nordic Semiconductor PHY Support (Cleartext only)"
|
2017-04-29 06:50:52 +02:00
|
|
|
depends on SOC_SERIES_NRF51X
|
2017-08-14 13:45:13 +02:00
|
|
|
select BT_CTLR_PHY_2M
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_PHY_CODED
|
2017-04-29 06:50:52 +02:00
|
|
|
bool "Coded PHY Support"
|
|
|
|
|
depends on SOC_NRF52840
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for Bluetooth 5.0 Coded PHY in the Controller.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
endif # BT_CTLR_PHY
|
2017-04-29 06:50:52 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_WORKER_PRIO
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Radio and Ticker's Worker IRQ priority"
|
2017-03-30 10:49:34 +02: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. This value
|
|
|
|
|
shall be less than or equal to the Ticker's Job priority value.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_JOB_PRIO
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Ticker's JOB IRQ priority"
|
2017-08-14 13:45:13 +02:00
|
|
|
range BT_CTLR_WORKER_PRIO 3 if SOC_SERIES_NRF51X
|
|
|
|
|
range BT_CTLR_WORKER_PRIO 6 if SOC_SERIES_NRF52X
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_XTAL_ADVANCED
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_XTAL_THRESHOLD
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Crystal shutdown threshold in uS"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on BT_CTLR_XTAL_ADVANCED
|
2018-02-02 13:11:41 +01:00
|
|
|
default 1500
|
2017-03-27 11:21:56 +02:00
|
|
|
help
|
|
|
|
|
Configure the optimal delta in micro seconds between two consecutive
|
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.
|
2017-03-27 11:21:56 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_SCHED_ADVANCED
|
2017-03-27 10:44:06 +02:00
|
|
|
bool "Advanced scheduling"
|
2017-08-09 09:21:11 +03:00
|
|
|
depends on (BT_MAX_CONN != 0)
|
2018-07-12 13:26:29 +02:00
|
|
|
default y if !(BT_PERIPHERAL && !BT_CENTRAL)
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_RADIO_ENABLE_FAST
|
2017-05-26 13:01:29 +02:00
|
|
|
bool "Use tTXEN/RXEN,FAST ramp-up"
|
|
|
|
|
depends on SOC_SERIES_NRF52X
|
2017-10-30 13:55:58 +01:00
|
|
|
default y
|
2017-05-26 13:01:29 +02:00
|
|
|
help
|
|
|
|
|
Enable use of fast radio ramp-up mode.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_TIFS_HW
|
2017-05-01 05:52:57 +02:00
|
|
|
bool "H/w Accelerated tIFS Trx switching"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on !BT_CTLR_RADIO_ENABLE_FAST
|
2017-05-01 05:52:57 +02:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable use of hardware accelerated tIFS Trx switching.
|
|
|
|
|
|
2018-01-31 14:02:19 +01:00
|
|
|
config BT_CTLR_SW_SWITCH_SINGLE_TIMER
|
|
|
|
|
bool "Single TIMER tIFS Trx SW switching"
|
|
|
|
|
depends on (!BT_CTLR_TIFS_HW) && SOC_SERIES_NRF52X
|
|
|
|
|
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
|
|
|
|
|
packets exchanged in the event.
|
|
|
|
|
|
2017-08-09 09:21:11 +03:00
|
|
|
if BT_CONN
|
2017-05-29 09:58:59 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_FAST_ENC
|
2016-12-30 06:51:17 +01:00
|
|
|
bool "Fast Encryption Setup"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on BT_CTLR_LE_ENC
|
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.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_CONN_RSSI
|
2016-12-29 17:07:54 +01:00
|
|
|
bool "Connection RSSI"
|
|
|
|
|
help
|
|
|
|
|
Enable connection RSSI measurement.
|
|
|
|
|
|
2017-08-09 09:21:11 +03:00
|
|
|
endif # BT_CONN
|
2017-05-29 09:58:59 +02:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_ADV_INDICATION
|
2017-03-10 11:53:38 +01:00
|
|
|
bool "Advertisement indications"
|
|
|
|
|
help
|
|
|
|
|
Generate events indicating on air advertisement events.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_SCAN_REQ_NOTIFY
|
2017-04-27 11:29:35 +02:00
|
|
|
bool "Scan Request Notifications"
|
|
|
|
|
help
|
|
|
|
|
Generate events notifying the on air scan requests received.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_SCAN_REQ_RSSI
|
2017-04-27 11:29:35 +02:00
|
|
|
bool "Measure Scan Request RSSI"
|
2017-08-14 13:45:13 +02:00
|
|
|
depends on BT_CTLR_SCAN_REQ_NOTIFY
|
2017-04-27 11:29:35 +02:00
|
|
|
help
|
|
|
|
|
Measure RSSI of the on air scan requests received.
|
|
|
|
|
|
2017-03-28 00:25:14 +02:00
|
|
|
endmenu
|
|
|
|
|
|
2017-09-15 15:09:53 +02:00
|
|
|
comment "BLE Controller hardware configuration"
|
|
|
|
|
|
|
|
|
|
menuconfig BT_CTLR_GPIO_PA
|
|
|
|
|
bool "Power Amplifier GPIO interface"
|
2017-10-02 11:18:04 +02:00
|
|
|
depends on !SOC_SERIES_NRF51X
|
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
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Power Amplifier GPIO pin number"
|
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
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Time from PA ON to Tx ready"
|
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"
|
2017-10-02 11:18:04 +02:00
|
|
|
depends on !SOC_SERIES_NRF51X
|
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
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Low Noise Amplifier GPIO pin number"
|
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
|
2018-07-12 13:26:29 +02:00
|
|
|
int "Time from LNA ON to Rx ready"
|
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
|
2018-07-12 13:26:29 +02:00
|
|
|
depends on SOC_FAMILY_NRF && (BT_CTLR_GPIO_PA || BT_CTLR_GPIO_LNA)
|
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
|
2017-09-15 15:09:53 +02:00
|
|
|
help
|
|
|
|
|
Select the nRF5 GPIOTE channel to use for PA/LNA GPIO feature.
|
|
|
|
|
|
2016-12-27 19:23:32 +01:00
|
|
|
comment "BLE Controller debug configuration"
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_ASSERT_HANDLER
|
2016-10-31 11:39:12 +01:00
|
|
|
bool "Bluetooth Controller Assertion Handler"
|
2017-08-09 09:21:11 +03:00
|
|
|
depends on BT_HCI_RAW
|
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
|
|
|
|
|
application code as void \"bt_controller_assert_handle(char \*, int)\"
|
|
|
|
|
and will be invoked whenever the controller code encounters
|
|
|
|
|
an unrecoverable error.
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_PROFILE_ISR
|
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.
|
2016-10-31 11:39:12 +01:00
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
config BT_CTLR_DEBUG_PINS
|
2017-02-21 10:29:39 +01:00
|
|
|
bool "Bluetooth Controller Debug Pins"
|
2018-06-26 23:38:03 +02:00
|
|
|
depends on BOARD_NRF51_PCA10028 || BOARD_NRF52_PCA10040 || BOARD_NRF52810_PCA10040 || BOARD_NRF52840_PCA10056
|
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
|
2018-01-23 23:58:41 +01:00
|
|
|
the code.
|
2017-02-21 10:29:39 +01:00
|
|
|
|
2018-06-26 14:03:34 +02:00
|
|
|
endif # BT_LL_SW
|
|
|
|
|
|
2017-08-14 13:45:13 +02:00
|
|
|
endif # BT_CTLR
|
