Lines Matching refs:commands

127 Allow low-level driver to filter ATA PACKET commands, returning a status
185 typically raid controllers that use ATA commands but do not actually do
389 Origins of commands
399 libata commands can originate from two sources - libata itself and SCSI
400 midlayer. libata internal commands are used for initialization and error
401 handling. All normal blk requests and commands for SCSI emulation are
402 passed as SCSI commands through queuecommand callback of SCSI host
405 How commands are issued
408 Internal commands
413     used by normal SCSI translated commands and ``qc->waiting`` is the
415     commands.
420 SCSI commands
427     commands use :c:func:`ata_scsi_qc_complete` while ATAPI commands use
435 How commands are processed
438 Depending on which protocol and which controller are used, commands are
447     types of commands don't require any software intervention once
467 How commands are completed
471 time out. For commands which are handled by interrupts,
474 also complete commands.
499 For all non-ATAPI commands, whether it fails or not, almost the same
504 However, failed ATAPI commands require more handling as REQUEST SENSE is
555    about the timed out command and ready for new commands.
559    quiescent state. Timed out commands may succeed or fail any time.
673 For ATA commands, this type of errors are indicated by !BSY && ERR
676 For ATAPI commands,
718     READ and WRITE commands report CHS or LBA of the first failed sector
736 Depending on commands, not all STATUS/ERROR bits are applicable. These
768 command phase (one or more NCQ commands outstanding). Although STATUS
777 and all other in-flight commands must be retried. Note that this retry
778 should not be counted - it's likely that commands retried this way would
875 -  EH needs to make HBA/device forget about in-flight commands
916     other commands. As in software reset, EDD affects both devices on a