5dd1cdda3b
The comment states the reason for this requirement is to detect
violations by a remote peer. The ATT version of this was removed in
ea04fd95f9. TLDR: It's neither possible
for, nor the job of the host to police the remote device.
We remove this requirement to be more flexible about the number of
priority levels in the system, and to avoid the temptation of using
priorities as a synchronization mechanism.
Signed-off-by: Aleksander Wasaznik <aleksander.wasaznik@nordicsemi.no>
54 lines
2.0 KiB
C
54 lines
2.0 KiB
C
/**
|
|
* @file dummy.c
|
|
* Static compilation checks.
|
|
*/
|
|
|
|
/*
|
|
* Copyright (c) 2017 Nordic Semiconductor ASA
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <zephyr/kernel.h>
|
|
#include <zephyr/bluetooth/bluetooth.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.
|
|
*/
|
|
BUILD_ASSERT(sizeof(bt_addr_t) == BT_ADDR_SIZE);
|
|
BUILD_ASSERT(sizeof(bt_addr_le_t) == BT_ADDR_LE_SIZE);
|
|
|
|
#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
|