Lines Matching full:commands

143 Allow low-level driver to filter ATA PACKET commands, returning a status
201 typically raid controllers that use ATA commands but do not actually do
407 Origins of commands
417 libata commands can originate from two sources - libata itself and SCSI
418 midlayer. libata internal commands are used for initialization and error
419 handling. All normal blk requests and commands for SCSI emulation are
420 passed as SCSI commands through queuecommand callback of SCSI host
423 How commands are issued
426 Internal commands
429     mechanism when qc is not available, internal commands are currently
437     used by normal SCSI translated commands and ``qc->waiting`` is the
439     commands.
444 SCSI commands
456     commands use :c:func:`ata_scsi_qc_complete` while ATAPI commands use
464 How commands are processed
467 Depending on which protocol and which controller are used, commands are
476     types of commands don't require any software intervention once
496 How commands are completed
500 time out. For commands which are handled by interrupts,
503 also complete commands.
528 For all non-ATAPI commands, whether it fails or not, almost the same
533 However, failed ATAPI commands require more handling as REQUEST SENSE is
585    about the timed out command and ready for new commands.
589    quiescent state. Timed out commands may succeed or fail any time.
703 For ATA commands, this type of errors are indicated by !BSY && ERR
706 For ATAPI commands,
748     READ and WRITE commands report CHS or LBA of the first failed sector
766 Depending on commands, not all STATUS/ERROR bits are applicable. These
798 command phase (one or more NCQ commands outstanding). Although STATUS
807 and all other in-flight commands must be retried. Note that this retry
808 should not be counted - it's likely that commands retried this way would
905 -  EH needs to make HBA/device forget about in-flight commands
946     other commands. As in software reset, EDD affects both devices on a