mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-04 14:21:55 +00:00
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
588 B
C
24 lines
588 B
C
/** @file
|
|
* @brief Internal API for Generic Attribute Profile handling.
|
|
*/
|
|
|
|
/*
|
|
* Copyright (c) 2015-2016 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
void bt_gatt_init(void);
|
|
void bt_gatt_connected(struct bt_conn *conn);
|
|
void bt_gatt_disconnected(struct bt_conn *conn);
|
|
|
|
#if defined(CONFIG_BT_GATT_CLIENT)
|
|
void bt_gatt_notification(struct bt_conn *conn, u16_t handle,
|
|
const void *data, u16_t length);
|
|
#else
|
|
static inline void bt_gatt_notification(struct bt_conn *conn, u16_t handle,
|
|
const void *data, u16_t length)
|
|
{
|
|
}
|
|
#endif /* CONFIG_BT_GATT_CLIENT */
|