79e6b0e0f6
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
60 lines
2.3 KiB
C
60 lines
2.3 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 the Tx thread to execute at higher priority
|
|
* than the Rx thread as the Tx thread needs to process the acknowledgements
|
|
* before new Rx data is processed. This is a necessity to correctly detect
|
|
* transaction violations in ATT and SMP protocols.
|
|
*/
|
|
BUILD_ASSERT(CONFIG_BT_HCI_TX_PRIO < CONFIG_BT_RX_PRIO);
|
|
|
|
/* 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
|