Lines Matching +full:time +full:- +full:of +full:- +full:flight
6 * Copyright (c) 2015-2016 Intel Corporation
8 * SPDX-License-Identifier: Apache-2.0
73 * Connection Interval: 30-50 ms
102 uint8_t pref_tx_phy; /**< Bitmask of preferred transmit PHYs */
103 uint8_t pref_rx_phy; /**< Bitmask of preferred receive PHYs */
108 * @param _pref_tx_phy Bitmask of preferred transmit PHYs.
109 * @param _pref_rx_phy Bitmask of preferred receive PHYs.
120 * @param _pref_tx_phy Bitmask of preferred transmit PHYs.
121 * @param _pref_rx_phy Bitmask of preferred receive PHYs.
152 /** Maximum Link Layer transmission payload time in us. */
156 /** Maximum Link Layer reception payload time in us. */
164 /** Maximum Link Layer transmission payload time in us. */
171 * @param _tx_max_time Maximum Link Layer transmission payload time in us.
182 * @param _tx_max_time Maximum Link Layer transmission payload time in us.
205 /** Maximum Peripheral latency in units of subrated connection intervals. */
207 /** Minimum number of underlying connection events to remain active
208 * after a packet containing a Link Layer PDU with a non-zero Length
223 /** Number of underlying connection events to remain active after
224 * a packet containing a Link Layer PDU with a non-zero Length
239 /** Number of underlying connection events to remain active after
240 * a packet containing a Link Layer PDU with a non-zero Length
244 /** Peripheral latency in units of subrated connection intervals. */
265 /** Supported AA-Only RTT precision. */
267 /** AA-Only RTT variant is not supported. */
269 /** 10ns time-of-flight accuracy. */
271 /** 150ns time-of-flight accuracy. */
279 /** 10ns time-of-flight accuracy. */
281 /** 150ns time-of-flight accuracy. */
289 /** 10ns time-of-flight accuracy. */
291 /** 150ns time-of-flight accuracy. */
297 /** Number of CS configurations */
299 /** Maximum number of consecutive CS procedures.
302 * numbers of CS procedures before termination.
305 /** Number of antennas. */
307 /** Maximum number of antenna paths. */
313 /** Mode-3 */
315 /** RTT AA-Only */
321 /** Number of CS steps needed to achieve the
327 /** Number of CS steps needed to achieve the
333 /** Number of CS steps needed to achieve the
339 /** Phase-based normalized attack detector metric
343 /** Phase-based normalized attack detector metric
355 /** Subfeature: Phase-based Ranging from RTT sounding sequence. */
357 /** Optional T_IP1 time durations during CS steps.
359 * - Bit 0: 10 us
360 * - Bit 1: 20 us
361 * - Bit 2: 30 us
362 * - Bit 3: 40 us
363 * - Bit 4: 50 us
364 * - Bit 5: 60 us
365 * - Bit 6: 80 us
368 /** Optional T_IP2 time durations during CS steps.
370 * - Bit 0: 10 us
371 * - Bit 1: 20 us
372 * - Bit 2: 30 us
373 * - Bit 3: 40 us
374 * - Bit 4: 50 us
375 * - Bit 5: 60 us
376 * - Bit 6: 80 us
379 /** Optional T_FCS time durations during CS steps.
381 * - Bit 0: 15 us
382 * - Bit 1: 20 us
383 * - Bit 2: 30 us
384 * - Bit 3: 40 us
385 * - Bit 4: 50 us
386 * - Bit 5: 60 us
387 * - Bit 6: 80 us
388 * - Bit 7: 100 us
389 * - Bit 8: 120 us
392 /** Optional T_PM time durations during CS steps.
394 * - Bit 0: 10 us
395 * - Bit 1: 20 us
398 /** Time in microseconds for the antenna switch period of the CS tones. */
402 * - Bit 0: 18dB
403 * - Bit 1: 21dB
404 * - Bit 2: 24dB
405 * - Bit 3: 27dB
406 * - Bit 4: 30dB
418 /** Mode-1 (RTT) */
420 /** Mode-2 (PBR) */
422 /** Mode-3 (RTT and PBR) */
430 /** Mode-1 (RTT) */
432 /** Mode-2 (PBR) */
434 /** Mode-3 (RTT and PBR) */
450 /** RTT with 32-bit sounding sequence */
452 /** RTT with 96-bit sounding sequence */
454 /** RTT with 32-bit random sequence */
456 /** RTT with 64-bit random sequence */
458 /** RTT with 96-bit random sequence */
460 /** RTT with 128-bit random sequence */
476 /** Use Channel Selection Algorithm #3b for non-mode-0 CS steps */
478 /** Use Channel Selection Algorithm #3c for non-mode-0 CS steps */
484 /** Use Hat shape for user-specified channel sequence */
486 /** Use X shape for user-specified channel sequence */
498 /** Minimum number of CS main mode steps to be executed before a submode step is executed */
500 /** Maximum number of CS main mode steps to be executed before a submode step is executed */
502 /** Number of main mode steps taken from the end of the last CS subevent to be repeated
503 * at the beginning of the current CS subevent directly after the last mode-0 step of that
507 /** Number of CS mode-0 steps to be included at the beginning of each CS subevent */
515 /** The number of times the Channel_Map field will be cycled through for non-mode-0 steps
521 /** User-specified channel sequence shape */
523 /** Number of channels skipped in each rising and falling sequence */
525 /** Interlude time in microseconds between the RTT packets */
527 /** Interlude time in microseconds between the CS tones */
529 /** Time in microseconds for frequency changes */
531 /** Time in microseconds for the phase measurement period of the CS tones */
597 * This is the CS procedure count since the completion of
601 /** Frequency compensation value in units of 0.01 ppm.
603 * This is a 15-bit signed integer in the range [-100, 100] ppm.
605 * A value of @ref BT_HCI_LE_CS_SUBEVENT_RESULT_FREQ_COMPENSATION_NOT_AVAILABLE
612 * Range: -127 to 20
614 * A value of @ref BT_HCI_LE_CS_REF_POWER_LEVEL_UNAVAILABLE indicates
648 /** Number of antenna paths used during the phase measurement stage.
651 /** Number of CS steps in the subevent.
668 * Increment the reference count of a connection object.
681 * Decrement the reference count of a connection object.
695 * sequentially-consistent view for objects allocated during the current
696 * invocation of this API. E.g. If preempted while allocations A then B then C
721 /** @brief Get destination (peer) address of a connection.
729 /** @brief Get array index of a connection
731 * This function is used to map bt_conn to index of an array of
736 * @return Index of the connection object.
737 * The range of the returned value is 0..CONFIG_BT_MAX_CONN-1
818 /** Level 4: Authenticated Secure Connections and 128-bit key. */
820 /** Bit to force new pairing procedure, bit-wise OR with requested
830 /** Paired with Out of Band method. */
875 /** Remote feature set (pages of bitmasks). */
878 /** Number of pages in the remote feature set. */
897 /** Per-manufacturer unique revision */
944 /** Phy of Transmit power reporting. */
948 * - 0xXX - Transmit power level
949 * + Range: -127 to 20
952 * - 0x7E - Remote device is not managing power levels on this PHY.
953 * - 0x7F - Transmit power level is not available
963 * - 0xXX - Change in transmit power level (positive indicates increased
966 * - 0x7F - Change is not available or is out of range.
1016 /** Minimum time in number of connection events to be observed once the
1057 * @return -EBUSY The remote information is not yet available.
1068 * @return -ENOBUFS HCI command buffer is not available.
1079 * @retval -ENOBUFS HCI command buffer is not available.
1090 * @retval -ENOBUFS HCI command buffer is not available.
1102 * @retval -ENOBUFS HCI command buffer is not available.
1154 * Request a change to the subrating parameters of a connection.
1192 * Update the preferred transmit and receive PHYs of the connection.
1212 * - @ref BT_HCI_ERR_AUTH_FAIL
1213 * - @ref BT_HCI_ERR_REMOTE_USER_TERM_CONN
1214 * - @ref BT_HCI_ERR_REMOTE_LOW_RESOURCES
1215 * - @ref BT_HCI_ERR_REMOTE_POWER_OFF
1216 * - @ref BT_HCI_ERR_UNSUPP_REMOTE_FEATURE
1217 * - @ref BT_HCI_ERR_PAIRING_NOT_SUPPORTED
1218 * - @ref BT_HCI_ERR_UNACCEPT_CONN_PARAM
1248 /** Bit-field of create connection options. */
1344 * will return -EINVAL if dereferenced @p conn is not NULL.
1385 * will return -EINVAL if dereferenced @p conn is not NULL.
1413 * @return -ENOMEM No free connection object available.
1427 * Every time the device loses the connection with peer, this connection
1428 * will be re-established if connectable advertisement from peer is received.
1433 * @param param If non-NULL, auto connect is enabled with the given
1451 * instead controlled by the values of the registered @ref bt_conn_auth_cb. If
1455 * This function may return an error if the required level of security defined using
1457 * (e.g., input output capabilities), or if the maximum number of paired devices
1536 * number of antenna paths (in the range [1, 4]).
1538 * +--------------+-------------+-------------------+-------------------+--------+
1540 * +--------------+-------------+-------------------+-------------------+--------+
1549 * +--------------+-------------+-------------------+-------------------+--------+
1551 * There are therefore four groups of possible antenna configurations:
1553 * - 1:1 configuration, where both A and B support 1 antenna each
1554 * - 1:N_AP configuration, where A supports 1 antenna, B supports N_AP antennas, and
1556 * - N_AP:1 configuration, where A supports N_AP antennas, B supports 1 antenna, and
1558 * - 2:2 configuration, where both A and B support 2 antennas and N_AP = 4
1575 /* State of the CS procedure */
1581 /* Transmit power level used for CS procedures (-127 to 20 dB; 0x7F if unavailable) */
1584 /* Duration of each CS subevent in microseconds (1250 us to 4 s) */
1587 /* Number of CS subevents anchored off the same ACL connection event (0x01 to 0x20) */
1590 /* Time between consecutive CS subevents anchored off the same ACL connection event in
1591 * units of 0.625 ms
1595 /* Number of ACL connection events between consecutive CS event anchor points */
1598 /* Number of ACL connection events between consecutive CS procedure anchor points */
1601 /* Number of CS procedures to be scheduled (0 if procedures to continue until disabled) */
1604 /* Maximum duration for each procedure in units of 0.625 ms (0x0001 to 0xFFFF) */
1610 * This structure is used for tracking the state of a connection.
1611 * It is registered with the help of the bt_conn_cb_register() API.
1612 * It's permissible to register multiple instances of this @ref bt_conn_cb
1613 * type, in case different modules of an application are interested in
1614 * tracking the connection state. If a callback is not of interest for
1621 * This callback notifies the application of a new connection.
1622 * In case the err parameter is non-zero it means that the
1627 * callback. Instead use the connected callback of the
1631 * @param err HCI error. Zero for success, non-zero otherwise.
1633 * @p err can mean either of the following:
1634 * - @ref BT_HCI_ERR_UNKNOWN_CONN_ID Creating the connection started by
1639 * - @p BT_HCI_ERR_ADV_TIMEOUT High duty cycle directed connectable
1669 * Use this to e.g. re-start connectable advertising or scanning.
1673 * Bluetooth API calls in this context is error-prone and strongly
1687 * It is recommended for an application to have just one of these
1732 /** @brief The security level of a connection has changed.
1734 * This callback notifies the application that the security of a
1737 * The security level of the connection can either have been increased
1745 * @param level New security level of the connection.
1746 * @param err Security error. Zero for success, non-zero otherwise.
1759 * @param remote_info Connection information of remote device.
1766 /** @brief The PHY of the connection has changed.
1768 * This callback notifies the application that the PHY of the
1779 /** @brief The data length parameters of the connection has changed.
1782 * payload length or transmission time has changed.
1836 * of the connection may have changed.
1861 * This callback notifies the application that the remote mode-0
1886 * @param config_id ID of the CS configuration that was removed.
1929 * Register callbacks to monitor the state of connections.
1934 * @retval -EEXIST if @p cb was already registered.
1941 * Unregister the state of connections callbacks.
1946 * @retval -EINVAL If @p cb is NULL
1947 * @retval -ENOENT if @p cb was not registered
1954 * @param _name Name of callback structure.
1963 * @return The string representation of the security error code.
1980 * Set/clear the Bonding flag in the Authentication Requirements of
1982 * The initial value of this flag depends on BT_BONDABLE Kconfig setting.
1983 * For the vast majority of applications calling this function shouldn't be
1993 * The initial value of this flag depends on @kconfig{CONFIG_BT_BONDABLE} Kconfig
2003 * Set/clear the Bonding flag in the Authentication Requirements of
2013 * The default value of the global configuration is defined using
2046 * @return Zero on success or -EINVAL if NULL
2065 * @return Zero on success or error code otherwise, positive in case of
2066 * protocol error or negative (POSIX) in case of stack internal error.
2084 * @return Zero on success or error code otherwise, positive in case of
2085 * protocol error or negative (POSIX) in case of stack internal error.
2105 * @param passkey A valid passkey (0 - 999999) or BT_PASSKEY_INVALID
2114 /** Type of OOB pairing method */
2148 * and a subset of the packet data, except for the initial Code octet.
2195 * pairing_confirm is registered both will be called for Just-Works
2216 * range of 0 - 999999, and is expected to be padded with zeroes so
2222 * to non-NULL the cancel callback must also be provided, since
2235 * feedback on the progress of entering the passkey over there. This is
2239 * The handler of this callback is expected to keep track of the number
2240 * of digits entered and show a password-field-like feedback to the
2246 * The event type is verified to be in range of the enum. No other
2247 * sanitization has been done. The remote could send a large number of
2248 * events of any type in any order.
2251 * @param type Type of event. Verified in range of the enum.
2260 * must be in the range of 0 - 999999, and should be expected to
2261 * be zero-padded, as that's how the peer device will typically be
2268 * device lacks the ability to enter a passkey. If set to non-NULL
2281 * be in the range of 0 - 999999, and should be zero-padded to
2290 * device lacks the ability to confirm a passkey. If set to non-NULL
2300 /** @brief Request the user to provide Out of Band (OOB) data.
2310 * This callback must be set to non-NULL in order to support OOB
2336 * request where none of the other user callbacks is applicable.
2345 * to non-NULL the cancel callback must also be provided, since
2482 * @retval -EINVAL Improper use of the API.
2483 * @retval -ENOMEM Failed to allocate.
2484 * @retval -ENOBUFS Failed to allocate.