Lines Matching refs:phase

549 		 * 2) In a non QAS, protocol allowed phase change,
706 		 * On a phase change oustside of packet boundaries,
805 		 * REQs in a non-packet phase.
839 	 * should go into the message out phase since we have ATN
847 	 * the bus phase.
865  * Command phase.  Set up the DMA registers and let 'er rip.
904 		 * command phase starts.  There is only one problem
905 		 * with this approach.  If the target changes phase
907 		 * that can go out on the bus in a data phase.  Due
913 		 * 800ns dead time between command phase and the REQ
914 		 * of the new phase.  If the transfer has completed
916 		 * see a phase change.  We thus treat any phasemiss
927 	 * Don't allow a data phase if the command
937  * Status phase.  Wait for the data byte to appear, then read it
950  * Message out phase.  If MSG_OUT is MSG_IDENTIFYFLAG, build a full
954  * it to handle the message phase completely on its own.  If the bit
970  * in case the target decides to put us in this phase for some strange
999  * phase and any required retries.
1010  * If the next bus phase after ATN drops is message out, it means
1023  * Message in phase.  Bytes are read using Automatic PIO mode.
1181 	 * Either way, the target should take us to message out phase
1291 	 * should take us to message out phase and then attempt to
1330 	 * phase has been detected or we are really
1344  * only if we've actually been into a data phase to change them.  This
1377  * SCB anytime we enter a data phase for the first time, so all
1378  * we need to do is clear the DPHASE flag and let the data phase
1380  * sure we have a clean start for the next data or command phase.
1399 		 * an async phase due to our asserted ACK.  Each
1613 	 * Since we've are entering a data phase, we will
1638 	 * If we re-enter the data phase after going through another
1639 	 * phase, our transfer location has almost certainly been
1651 	 * us to another phase, and then notify the host.
1665 	/* Wait for non-data phase. */
1678 	/* We have seen a data phase at least once. */
1686 	 * completes or the target changes phase.  Both conditions
1697 	 * The transfer has terminated either due to a phase
1703 	 * complete) that usually follow a data phase.
1733 	 * If the target has left us in data phase, loop through
1755 		 * initiator before changing phase.  We only need to
1786  * pickup on the next segment on the next data phase.
2147 	 * a NONPACKREQ phase change have occurred and the FIFO is
2172 	 * The unexpected nonpkt phase handler assumes that any
2190  * we simply do not have the full I_T_L_Q for this phase.