Lines Matching full:blocking

118  * ignored and all transfers are blocking.
123  * @brief Flag indicating blocking transfer.
126  * to non-blocking operation. If UARTE is transmitting when the user requests blocking transfer,
128  * accepted to poll the driver and continuously request blocking transfer until it
129  * is accepted. It can be done from any priority context. Blocking transfer returns
136  * @brief Flag indicating to return from blocking transfer not waiting for the last transmit event.
138  * The flag indicates a blocking transfer just like @ref NRFX_UARTE_TX_BLOCKING.
173  * When linked transfers are used, then blocking transfers (see @ref NRFX_UARTE_TX_BLOCKING and
175  * and the @ref nrfx_uarte_tx is called during ongoing blocking transfer.
367  *                          blocking mode.
440  * is done. Otherwise, the transfer is performed in blocking mode, that is, this function
462  *                                   (blocking mode only) or transfer cannot be performed due to
489  *       in non-blocking mode. It will contain the number of bytes sent until the abort was called.
552  * Otherwise, the transfer is performed in blocking mode, that is this function
553  * returns when the transfer is finished. Blocking mode is not using interrupt so
555  * The receive buffer pointer is double-buffered in non-blocking mode. The secondary
585  *                                 in non-blocking mode).
587  *                                 (blocking mode only).
596  * @brief Function for testing the receiver state in blocking mode.
612  * @note @ref NRFX_UARTE_EVT_RX_DONE event will be generated in non-blocking mode.
641  * @note Function must be used in the blocking mode only. In case of non-blocking mode, an error