Lines Matching +full:perm +full:- +full:secure

6  * Copyright (c) 2015-2016 Intel Corporation
8 * SPDX-License-Identifier: Apache-2.0
38 /** No operations supported, e.g. for notify-only */
61 * If set, requires encryption using authenticated link-key for read
68 * If set, requires encryption using authenticated link-key for write
80 /** @brief Attribute read permission with LE Secure Connection encryption.
82 * If set, requires that LE Secure Connections is used for read access.
86 /** @brief Attribute write permission with LE Secure Connection encryption.
88 * If set, requires that LE Secure Connections is used for write access.
100 #define BT_GATT_ERR(_att_err) (-(_att_err))
220 * proper object of this type. The field @ref perm, and methods
300 uint16_t perm: 15; member
548 return bt_att_err_to_str((gatt_err) < 0 ? -(gatt_err) : (gatt_err)); in bt_gatt_err_to_str()
562 * Register callbacks to perform application-specific authorization of GATT
604 * @return -EAGAIN if ``bt_init()`` has been called but ``settings_load()`` hasn't yet.
1108 * @note Only use this with attributes which user_data is a NULL-terminated C
1129 * @param _value User description NULL-terminated C string.
1204 .perm = _perm, \
1300 * @retval -EINVAL
1301 * - One of the attribute handles is invalid.
1302 * - Only one parameter was passed. This API expects 2 or more.
1303 * - Not all `func` were equal or not all `user_data` were equal.
1304 * - One of the characteristics is not notifiable.
1305 * - An UUID was passed in one of the parameters.
1306 * @retval -ERANGE
1307 * - The notifications cannot all fit in a single ATT_MULTIPLE_HANDLE_VALUE_NTF.
1308 * - They exceed the MTU of all open ATT bearers.
1309 * @retval -EPERM
1312 * @retval -EOPNOTSUPP
1510 * field can contain up to ATT_MTU - 3 octets (size of opcode and handle).
1541 * The Response comes in callback @p params->func. The callback is run from
1551 * @retval 0 Successfully queued request. Will call @p params->func on
1554 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
1559 * @retval -EALREADY The MTU exchange procedure has been already performed.
1580 * - uuid UUID representing the type of attribute.
1581 * - handle Handle in the remote database.
1582 * - user_data The value of the attribute, if the discovery type maps to an
1586 * The effective type of @c attr->user_data is determined by @c params. Note
1587 * that the fields @c params->type and @c params->uuid are left unchanged by
1590 * @c params->type | @c params->uuid | Type of @c attr->user_data
1591 * -------------------------------------|-------------------------|---------------------------
1603 * Also consider if using read-by-type instead of discovery is more convenient.
1650 * - Characteristic Extended Properties
1651 * - Client Characteristic Configuration
1652 * - Server Characteristic Configuration
1653 * - Characteristic Presentation Format
1684 /** Only for stack-internal use, used for automatic discovery. */
1710 * The Response comes in callback @p params->func. The callback is run from
1720 * @retval 0 Successfully queued request. Will call @p params->func on
1723 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
1736 * When reading using by_uuid, `params->start_handle` is the attribute handle
1825 * The Response comes in callback @p params->func. The callback is run from
1835 * @retval 0 Successfully queued request. Will call @p params->func on
1838 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
1876 * The Response comes in callback @p params->func. The callback is run from
1882 * this function will instead instead return `-ENOMEM` if it would block to
1888 * @retval 0 Successfully queued request. Will call @p params->func on
1891 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
1923 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
1949 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
1967 * In the case of an empty notification, the @p data pointer will be non-NULL
2091 * The Response comes in callback @p params->subscribe. The callback is run from
2093 * The Notification callback @p params->notify is also called from the BT RX
2106 * @retval 0 Successfully queued request. Will call @p params->write on
2109 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
2114 * @retval -EALREADY if there already exist a subscription using the @p params.
2116 * @retval -EBUSY if @p params.ccc_handle is 0 and @kconfig{CONFIG_BT_GATT_AUTO_DISCOVER_CCC} is
2148 * The Response comes in callback @p params->func. The callback is run from
2158 * @retval 0 Successfully queued request. Will call @p params->write on
2161 * @retval -ENOMEM ATT request queue is full and blocking would cause deadlock.
2176 * - #bt_gatt_exchange_mtu
2177 * - #bt_gatt_discover
2178 * - #bt_gatt_read
2179 * - #bt_gatt_write
2180 * - #bt_gatt_subscribe
2181 * - #bt_gatt_unsubscribe