85cfff0d92
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>
109 lines
3.3 KiB
Plaintext
109 lines
3.3 KiB
Plaintext
if BLUETOOTH_CONTROLLER
|
|
|
|
comment "BLE Controller configuration"
|
|
|
|
config BLUETOOTH_CONTROLLER_RX_BUFFERS
|
|
prompt "Number of Rx buffers"
|
|
int
|
|
default 1
|
|
default 6 if BLUETOOTH_HCI_RAW
|
|
range 1 10
|
|
help
|
|
Set the number of Rx PDUs to be buffered in the controller.
|
|
|
|
config BLUETOOTH_CONTROLLER_TX_BUFFERS
|
|
prompt "Number of Tx buffers"
|
|
int
|
|
default 1
|
|
default 7 if BLUETOOTH_HCI_RAW
|
|
range 1 10
|
|
help
|
|
Set the number of Tx PDUs to be queued for transmission
|
|
in the controller.
|
|
|
|
config BLUETOOTH_CONTROLLER_TX_BUFFER_SIZE
|
|
prompt "Tx buffer size"
|
|
int
|
|
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
|
|
uint16_t for size/length variables).
|
|
|
|
config BLUETOOTH_CONTROLLER_RX_STACK_SIZE
|
|
int "Size of the receiving thread stack"
|
|
default 512
|
|
range 512 65536
|
|
help
|
|
Size of the receiving thread stack. This is the context from
|
|
which all radio messages are encoded into HCI events or data
|
|
before passing it to Bluetooth receiving thread.
|
|
|
|
comment "BLE Controller features"
|
|
|
|
config BLUETOOTH_CONTROLLER_LE_PING
|
|
bool "LE Ping"
|
|
default y
|
|
help
|
|
Enable support for Bluetooth v4.1 LE Ping feature in the Controller.
|
|
|
|
config BLUETOOTH_CONTROLLER_DATA_LENGTH
|
|
bool "Data Length Update"
|
|
default y
|
|
help
|
|
Enable support for Bluetooth v4.2 LE Data Length Update procedure in
|
|
the Controller.
|
|
|
|
config BLUETOOTH_CONTROLLER_DATA_LENGTH_MAX
|
|
prompt "Maximum data length supported"
|
|
depends on BLUETOOTH_CONTROLLER_DATA_LENGTH
|
|
int
|
|
default 27
|
|
range 27 251
|
|
help
|
|
Set the maximum data length of PDU supported in the Controller.
|
|
|
|
config BLUETOOTH_CONTROLLER_FAST_ENC
|
|
bool "Fast Encryption Setup"
|
|
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.
|
|
|
|
config BLUETOOTH_CONTROLLER_CONN_RSSI
|
|
bool "Connection RSSI"
|
|
help
|
|
Enable connection RSSI measurement.
|
|
|
|
comment "BLE Controller debug configuration"
|
|
|
|
config BLUETOOTH_CONTROLLER_ASSERT_HANDLER
|
|
bool "Bluetooth Controller Assertion Handler"
|
|
depends on BLUETOOTH_HCI_RAW
|
|
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.
|
|
|
|
config BLUETOOTH_CONTROLLER_PROFILE_ISR
|
|
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.
|
|
|
|
endif # BLUETOOTH_CONTROLLER
|