66ff97e69b
Because the number of ACL RX buffers must be at least the number of maximum connections plus one, increasing `CONFIG_BT_MAX_CONN` could inadvertently lead to a build failure if the number of ACL RX buffers is not also increased. This dependency may not be obvious to users. To address this issue, this commit deprecates the `CONFIG_BT_BUF_RX_COUNT` Kconfig symbol and computes the value in `buf.h` using the new `BT_BUF_RX_COUNT` define. Note that the default value and the minimum range value have been changed to 0 to "disable" the option. Additionally, to allow users to increase the number of ACL RX buffers, this commit introduces the new `CONFIG_BT_BUF_RX_COUNT_EXTRA` Kconfig symbol. The value of this symbol will be added to the computed value of `BT_BUF_RX_COUNT`. The configurations of tests and samples have been updated to reflect these changes. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
62 lines
2.3 KiB
C
62 lines
2.3 KiB
C
/**
|
|
* @file dummy.c
|
|
* Static compilation checks.
|
|
*/
|
|
|
|
/*
|
|
* Copyright (c) 2017 Nordic Semiconductor ASA
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <stdalign.h>
|
|
|
|
#include <zephyr/kernel.h>
|
|
#include <zephyr/bluetooth/bluetooth.h>
|
|
#include <zephyr/bluetooth/buf.h>
|
|
|
|
/*
|
|
* The unpacked structs below are used inside __packed structures that reflect
|
|
* what goes on the wire. While alignment is not a problem for those, since all
|
|
* their members are bytes or byte arrays, the size is. They must not be padded
|
|
* by the compiler, otherwise the on-wire packet will not map the packed
|
|
* structure correctly.
|
|
*
|
|
* The bt_addr structs are not marked __packed because it's considered ugly by
|
|
* some. But here is a proof that the structs have all the properties of, and
|
|
* can be safely used as packed structs.
|
|
*/
|
|
BUILD_ASSERT(sizeof(bt_addr_t) == BT_ADDR_SIZE);
|
|
BUILD_ASSERT(alignof(bt_addr_t) == 1);
|
|
BUILD_ASSERT(sizeof(bt_addr_le_t) == BT_ADDR_LE_SIZE);
|
|
BUILD_ASSERT(alignof(bt_addr_le_t) == 1);
|
|
|
|
#if defined(CONFIG_BT_HCI_HOST)
|
|
/* The Bluetooth subsystem requires that higher priority events shall be given
|
|
* in a priority 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_BT_DRIVER_RX_HIGH_PRIO < CONFIG_BT_HCI_TX_PRIO);
|
|
#endif /* defined(CONFIG_BT_HCI_HOST) */
|
|
|
|
#if (defined(CONFIG_LOG_BACKEND_RTT) && \
|
|
(defined(CONFIG_SEGGER_RTT_MODE_BLOCK_IF_FIFO_FULL) || \
|
|
defined(CONFIG_LOG_BACKEND_RTT_MODE_BLOCK))) || \
|
|
defined(CONFIG_LOG_BACKEND_NET) || \
|
|
defined(CONFIG_LOG_IMMEDIATE_CLEAN_OUTPUT)
|
|
#define INCOMPATIBLE_IMMEDIATE_LOG_BACKEND 1
|
|
#endif
|
|
|
|
/* Immediate logging on most backend is not supported
|
|
* with the software-based Link Layer since it introduces ISR latency
|
|
* due to outputting log messages with interrupts disabled.
|
|
*/
|
|
#if !defined(CONFIG_TEST) && !defined(CONFIG_ARCH_POSIX) && \
|
|
defined(CONFIG_BT_LL_SW_SPLIT) && \
|
|
defined(INCOMPATIBLE_IMMEDIATE_LOG_BACKEND)
|
|
BUILD_ASSERT(!IS_ENABLED(CONFIG_LOG_MODE_IMMEDIATE), "Immediate logging "
|
|
"on selected backend(s) not "
|
|
"supported with the software Link Layer");
|
|
#endif
|