Lines Matching refs:transfer

459 	 * completions to continue the data transfer.
481  * is responsible for polling for transfer completion.
845 	 * Main loop for information transfer phases.  Wait for the
875 	 * re-allocate a FIFO so transfer state is
911 		 * the transfer has completed successfully.  Work
914 		 * of the new phase.  If the transfer has completed
918 		 * transfer.
1360 	 * transfer, just mark us at the end rather than perform a
1639 	 * phase, our transfer location has almost certainly been
1641 	 * the host driver to fix us up based on the transfer residual
1685 	 * The transfer is complete if either the last segment
1697 	 * The transfer has terminated either due to a phase
1721 	 * transfer and then test to see if the data FIFO is
1722 	 * non-empty.  We know there is more data yet to transfer
1779  * in this transfer.
1782  * to fetch additional segments for this transfer,
1857 		 * this L-Q is a continuation of a data transfer for which
1862 		 * situation by noticing that this is the first data transfer
1863 		 * after an LQ (LQIWORKONLQ true), that the data transfer is
1864 		 * a continuation of a transfer already setup in our FIFO
1919  * if the target changes to a new L_Q or busfrees/QASes and the transfer
1946 	 * Host sets up address/count and enables transfer.
1958 	 * Wait in idle loop for transfer to complete.
2009 	 * have satisfied the transfer by loading segments and
2068 	 * Mark transfer as completed.
2117  * Watch over the status transfer.  Our host sense buffer is