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>
This commit is contained in:
parent
02383dee67
commit
2975ca0754
286 changed files with 3405 additions and 3421 deletions
|
@ -23,14 +23,13 @@ BUILD_ASSERT(CONFIG_SYSTEM_WORKQUEUE_PRIORITY < 0);
|
|||
* before new Rx data is processed. This is a necessity to correctly detect
|
||||
* transaction violations in ATT and SMP protocols.
|
||||
*/
|
||||
BUILD_ASSERT(CONFIG_BLUETOOTH_HCI_TX_PRIO < CONFIG_BLUETOOTH_RX_PRIO);
|
||||
BUILD_ASSERT(CONFIG_BT_HCI_TX_PRIO < CONFIG_BT_RX_PRIO);
|
||||
|
||||
#if defined(CONFIG_BLUETOOTH_CONTROLLER)
|
||||
#if defined(CONFIG_BT_CONTROLLER)
|
||||
/* The Bluetooth Controller's priority receive thread priority shall be higher
|
||||
* than the Bluetooth Host's Tx and the Controller's receive thread priority.
|
||||
* This is required in order to dispatch Number of Completed Packets event
|
||||
* before any new data arrives on a connection to the Host threads.
|
||||
*/
|
||||
BUILD_ASSERT(CONFIG_BLUETOOTH_CONTROLLER_RX_PRIO <
|
||||
CONFIG_BLUETOOTH_HCI_TX_PRIO);
|
||||
#endif /* CONFIG_BLUETOOTH_CONTROLLER */
|
||||
BUILD_ASSERT(CONFIG_BT_CONTROLLER_RX_PRIO < CONFIG_BT_HCI_TX_PRIO);
|
||||
#endif /* CONFIG_BT_CONTROLLER */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue