2975ca0754
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>
24 lines
513 B
C
24 lines
513 B
C
/*
|
|
* Copyright (c) 2016 Nordic Semiconductor ASA
|
|
* Copyright (c) 2016 Vinayak Kariappa Chettimada
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#ifndef _HAL_DEBUG_H_
|
|
#define _HAL_DEBUG_H_
|
|
|
|
#ifdef CONFIG_BT_CONTROLLER_ASSERT_HANDLER
|
|
void bt_controller_assert_handle(char *file, u32_t line);
|
|
#define LL_ASSERT(cond) if (!(cond)) { \
|
|
bt_controller_assert_handle(__FILE__, \
|
|
__LINE__); \
|
|
}
|
|
#else
|
|
#define LL_ASSERT(cond) BT_ASSERT(cond)
|
|
#endif
|
|
|
|
#include "nrf5/debug.h"
|
|
|
|
#endif /* _HAL_DEBUG_H_ */
|