Lines Matching full: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
382 Origins of commands
392 libata commands can originate from two sources - libata itself and SCSI
393 midlayer. libata internal commands are used for initialization and error
394 handling. All normal blk requests and commands for SCSI emulation are
395 passed as SCSI commands through queuecommand callback of SCSI host
398 How commands are issued
401 Internal commands
406     used by normal SCSI translated commands and ``qc->waiting`` is the
408     commands.
413 SCSI commands
420     commands use :c:func:`ata_scsi_qc_complete` while ATAPI commands use
428 How commands are processed
431 Depending on which protocol and which controller are used, commands are
440     types of commands don't require any software intervention once
460 How commands are completed
464 time out. For commands which are handled by interrupts,
467 also complete commands.
492 For all non-ATAPI commands, whether it fails or not, almost the same
497 However, failed ATAPI commands require more handling as REQUEST SENSE is
548    about the timed out command and ready for new commands.
552    quiescent state. Timed out commands may succeed or fail any time.
666 For ATA commands, this type of errors are indicated by !BSY && ERR
669 For ATAPI commands,
711     READ and WRITE commands report CHS or LBA of the first failed sector
729 Depending on commands, not all STATUS/ERROR bits are applicable. These
761 command phase (one or more NCQ commands outstanding). Although STATUS
770 and all other in-flight commands must be retried. Note that this retry
771 should not be counted - it's likely that commands retried this way would
868 -  EH needs to make HBA/device forget about in-flight commands
909     other commands. As in software reset, EDD affects both devices on a