OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/include/bluetooth/mesh.h

26 lines
531 B
C
Raw Normal View History

Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
/** @file
* @brief Bluetooth Mesh Profile APIs.
*/
/*
* Copyright (c) 2017 Intel Corporation
*
* SPDX-License-Identifier: Apache-2.0
*/
#ifndef __BT_MESH_H
#define __BT_MESH_H
#include <zephyr/types.h>
#include <stddef.h>
#include <net/buf.h>
Bluetooth: Mesh: Refactor public headers into dedicated subdirectory As the number of mesh APIs grows it becomes a bit cumbersome to have everything in a single header file. Split the mesh.h header file into multiple files in a new mesh subdirectory, and include the new headers from the old one to retain backwards compatibility and simplicity for apps (they only need to include <bluetooth/mesh.h>). Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:33:26 +08:00
#include <bluetooth/mesh/access.h>
#include <bluetooth/mesh/main.h>
#include <bluetooth/mesh/cfg_srv.h>
#include <bluetooth/mesh/health_srv.h>
Bluetooth: Mesh: Add skeleton for Configuration Client Model Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:48:55 +08:00
#include <bluetooth/mesh/cfg_cli.h>
Bluetooth: Mesh: Add skeleton for Health Client model Add a skeleton for the Health Client model. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-22 14:49:52 +08:00
#include <bluetooth/mesh/health_cli.h>
Bluetooth: Mesh: Refactor public headers into dedicated subdirectory As the number of mesh APIs grows it becomes a bit cumbersome to have everything in a single header file. Split the mesh.h header file into multiple files in a new mesh subdirectory, and include the new headers from the old one to retain backwards compatibility and simplicity for apps (they only need to include <bluetooth/mesh.h>). Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-12 19:33:26 +08:00
#include <bluetooth/mesh/proxy.h>
Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
#endif /* __BT_MESH_H */