Lines Matching refs:us
73 * If the kernel has caught up with us, thaw the queue.
953 * control byte. This will cause us to interrupt the host and allow
963 * BDR message in response to a bad reselection would leave us pointed to
970 * in case the target decides to put us in this phase for some strange
1181 * Either way, the target should take us to message out phase
1198 * to mesgin to give an invalid message, let the host abort us.
1211 * See if we attempted to deliver a message but the target ingnored us.
1281 * Is it a disconnect message? Set a flag in the SCB to remind us
1291 * should take us to message out phase and then attempt to
1360 * transfer, just mark us at the end rather than perform a
1396 * This allows us to tolerate devices like the GEM318
1641 * the host driver to fix us up based on the transfer residual
1651 * us to another phase, and then notify the host.
1733 * If the target has left us in data phase, loop through
1778 * allows us to update our notion of where we are
1785 * another segment. This will allow us to immediately
1797 * hardware will only interrupt us once SHVALID or
1813 * feature of the chip allows us to load two elements
1852 * On RevA Silicon, if the target returns us to data-out
1854 * possible for us to transition the free running clock to
1883 * have lost the race (e.g. host paused us) and our attempts
2006 * will not be asserted if the NONPACKREQ is for us,
2097 * the FIFO anyway since it costs us only one extra