Lines Matching full:operation

54 …      xip_offset;   /**< Address offset into the external memory for Execute in Place operation. */
154  * Write, read, and erase operations check memory device busy state before starting the operation.
155 …* If the memory is busy, the resulting action depends on the mode in which the read operation is u…
156  *  - blocking mode (without handler) - a delay occurs until the last operation still runs and
157  *    until operation data is still being read.
158  *  - interrupt mode (with handler) - event emission occurs after the last operation
165  * @retval NRFX_SUCCESS            If the operation was successful (blocking mode) or operation
167  * @retval NRFX_ERROR_BUSY         If the driver currently handles another operation.
177  * Write, read, and erase operations check memory device busy state before starting the operation.
178 …* If the memory is busy, the resulting action depends on the mode in which the write operation is …
179  *  - blocking mode (without handler) - a delay occurs until the last operation still runs and
180  *    until operation data is still being sent.
181  *  - interrupt mode (with handler) - event emission occurs after the last operation
182  *    and sending of operation data are finished.
183  * To manually control operation execution in the memory device, use @ref nrfx_qspi_mem_busy_check
186  * before the write operation checked if memory was busy.
192  * @retval NRFX_SUCCESS            If the operation was successful (blocking mode) or operation
194  * @retval NRFX_ERROR_BUSY         If the driver currently handles other operation.
204  * Write, read, and erase operations check memory device busy state before starting the operation.
205 …* If the memory is busy, the resulting action depends on the mode in which the erase operation is …
206  *  - blocking mode (without handler) - a delay occurs until the last operation still runs and
207  *    until operation data is still being sent.
208  *  - interrupt mode (with handler) - event emission occurs after the last operation
209  *    and sending of operation data are finished.
210  * To manually control operation execution in the memory device, use @ref nrfx_qspi_mem_busy_check
213  * before the erase operation checked if memory was busy.
219  * @retval NRFX_SUCCESS    If the operation was successful (blocking mode) or operation
221  * @retval NRFX_ERROR_BUSY If the driver currently handles another operation.
227  * @brief Function for starting an erase operation of the whole chip.
229  * @retval NRFX_SUCCESS    If the operation was successful (blocking mode) or operation
231  * @retval NRFX_ERROR_BUSY If the driver currently handles another operation.
239  * @retval NRFX_SUCCESS    If the driver and memory are ready to handle a new operation.
240  * @retval NRFX_ERROR_BUSY If the driver or memory currently handle another operation.
245 …* @brief Function for sending operation code, sending data, and receiving data from the memory dev…
255  * @retval NRFX_SUCCESS            If the operation was successful.
257  * @retval NRFX_ERROR_BUSY         If the driver currently handles other operation.
263 …* @brief Function for sending operation code and data to the memory device with simpler configurat…
268  * @param[in] opcode      Operation code. Sending first.
272  * @retval NRFX_SUCCESS            If the operation was successful.
273  * @retval NRFX_ERROR_BUSY         If the driver currently handles another operation.