OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/bluetooth/controller/Kconfig

53 lines
1.4 KiB
Plaintext
Raw Normal View History

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 18:01:06 +08:00
if BLUETOOTH_CONTROLLER
comment "BLE Controller configuration"
config BLUETOOTH_CONTROLLER_DATA_LENGTH
prompt "Maximum data length supported"
int
default 27
range 27 251
help
Bluetooth: Controller: Kconfig: Clean up style issues The right convention for help text is tab + 2 spaces. Change-Id: I2722a8b33f5f74be110dc43fbcecc12841f0db84 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 17:37:04 +08:00
Set the maximum data length of PDU supported in the stack.
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 18:01:06 +08:00
config BLUETOOTH_CONTROLLER_RX_BUFFERS
prompt "Number of Rx buffers"
int
Bluetooth: Controller: Improve default RX/TX buffer counts Currently the ideal buffer counts for a controller-only build are 6 RX buffers and 7 TX buffers: ATT_MTU of 158 bytes can be sent in one connection interval of 6 tx/rx -es wherein connection interval is 7.5ms Change-Id: I64b4620c5e8e7db8d7ed72fa1db82e266e121f27 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-10 17:30:04 +08:00
default 6 if BLUETOOTH_HCI_RAW
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 18:01:06 +08:00
default 1
range 1 10
help
Bluetooth: Controller: Kconfig: Clean up style issues The right convention for help text is tab + 2 spaces. Change-Id: I2722a8b33f5f74be110dc43fbcecc12841f0db84 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 17:37:04 +08:00
Set the number of Rx PDUs to be buffered in the controller.
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 18:01:06 +08:00
config BLUETOOTH_CONTROLLER_TX_BUFFERS
prompt "Number of Tx buffers"
int
Bluetooth: Controller: Improve default RX/TX buffer counts Currently the ideal buffer counts for a controller-only build are 6 RX buffers and 7 TX buffers: ATT_MTU of 158 bytes can be sent in one connection interval of 6 tx/rx -es wherein connection interval is 7.5ms Change-Id: I64b4620c5e8e7db8d7ed72fa1db82e266e121f27 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-10 17:30:04 +08:00
default 7 if BLUETOOTH_HCI_RAW
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 18:01:06 +08:00
default 1
range 1 10
help
Bluetooth: Controller: Kconfig: Clean up style issues The right convention for help text is tab + 2 spaces. Change-Id: I2722a8b33f5f74be110dc43fbcecc12841f0db84 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 17:37:04 +08:00
Set the number of Tx PDUs to be queued for transmission
in the controller.
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 18:01:06 +08:00
Bluetooth: Controller: Measure and use correct stack size Use stack_analyse in the recv fiber to print actual stack usage, use this as default in Kconfig option, and declare a rx fiber stack of Kconfig supplied stack size. Change-id: Id97ad2de4f7be3069f93271d60544f760abbf575 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-09-02 03:34:56 +08:00
config BLUETOOTH_CONTROLLER_RX_STACK_SIZE
Bluetooth: Controller: Stop using deprecated APIs Switch from fiber_start() to k_thread_spawn() and from NANOKERNEL to POST_KERNEL init level. Change-Id: I34fb11cbe20216c8646ebacb07be304a67e3cd0a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-11 16:02:49 +08:00
int "Size of the receiving thread stack"
Bluetooth: Controller: Measure and use correct stack size Use stack_analyse in the recv fiber to print actual stack usage, use this as default in Kconfig option, and declare a rx fiber stack of Kconfig supplied stack size. Change-id: Id97ad2de4f7be3069f93271d60544f760abbf575 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-09-02 03:34:56 +08:00
default 256
range 256 65536
help
Bluetooth: Controller: Stop using deprecated APIs Switch from fiber_start() to k_thread_spawn() and from NANOKERNEL to POST_KERNEL init level. Change-Id: I34fb11cbe20216c8646ebacb07be304a67e3cd0a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-11 16:02:49 +08:00
Size of the receiving thread stack. This is the context from
Bluetooth: Controller: Measure and use correct stack size Use stack_analyse in the recv fiber to print actual stack usage, use this as default in Kconfig option, and declare a rx fiber stack of Kconfig supplied stack size. Change-id: Id97ad2de4f7be3069f93271d60544f760abbf575 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-09-02 03:34:56 +08:00
which all radio messages are encoded into HCI events or data
Bluetooth: Controller: Stop using deprecated APIs Switch from fiber_start() to k_thread_spawn() and from NANOKERNEL to POST_KERNEL init level. Change-Id: I34fb11cbe20216c8646ebacb07be304a67e3cd0a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-11 16:02:49 +08:00
before passing it to Bluetooth receiving thread.
Bluetooth: Controller: Measure and use correct stack size Use stack_analyse in the recv fiber to print actual stack usage, use this as default in Kconfig option, and declare a rx fiber stack of Kconfig supplied stack size. Change-id: Id97ad2de4f7be3069f93271d60544f760abbf575 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-09-02 03:34:56 +08:00
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 18:39:12 +08:00
config BLUETOOTH_CONTROLLER_ASSERT_HANDLER
bool "Bluetooth Controller Assertion Handler"
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-09 18:23:21 +08:00
depends on BLUETOOTH_HCI_RAW
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 18:39:12 +08: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.
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 18:01:06 +08:00
endif # BLUETOOTH_CONTROLLER