Lines Matching full:and

5  * Redistribution and use in source and binary forms, with or without
9  *    list of conditions and the following disclaimer.
12  *    notice, this list of conditions and the following disclaimer in the
13  *    documentation and/or other materials provided with the distribution.
19  * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
20  * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26  * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
120  * This function configures the peripheral and its interrupts and activates it. During the 
121  * activation process, the internal clocks are started and the QSPI peripheral tries to read 
122  * the status byte to read the busy bit. Reading the status byte is done in a simple poll and wait
154  * Write, read, and erase operations check memory device busy state before starting the operation.
156  *  - blocking mode (without handler) - a delay occurs until the last operation still runs and
159  *    and reading of data are finished.
177  * Write, read, and erase operations check memory device busy state before starting the operation.
179  *  - blocking mode (without handler) - a delay occurs until the last operation still runs and
182  *    and sending of operation data are finished.
185 …* Remember that an incoming event signalizes only that data was sent to the memory device and the …
204  * Write, read, and erase operations check memory device busy state before starting the operation.
206  *  - blocking mode (without handler) - a delay occurs until the last operation still runs and
209  *    and sending of operation data are finished.
212 …* Remember that an incoming event signalizes only that data was sent to the memory device and the …
236  * @brief Function for getting the current driver status and status byte of memory device with
239  * @retval NRFX_SUCCESS    If the driver and memory are ready to handle a new operation.
245 …* @brief Function for sending operation code, sending data, and receiving data from the memory dev…
247  * Use this function to transfer configuration data to memory and to receive data from memory.
249  * This function is a synchronous function and should be used only if necessary.
251  * @param[in]  p_config    Pointer to the structure with opcode and transfer configuration.
263 …* @brief Function for sending operation code and data to the memory device with simpler configurat…
265  * Use this function to transfer configuration data to memory and to receive data from memory.
266  * This function is a synchronous function and should be used only if necessary.
269  * @param[in] length      Length of the data to send and opcode. See @ref nrf_qspi_cinstr_len_t.