Lines Matching refs:ATA
10 libATA is a library used inside the Linux kernel to support ATA host
11 controllers and devices. libATA provides an ATA driver API, class
12 transports for ATA and ATAPI devices, and SCSI<->ATA translation for ATA
16 internals, and a couple sample ATA low-level drivers.
24 with the ATA and SCSI layers.
29 defining at a bare minimum the bus I/O addresses of the ATA shadow
35 Disable ATA port
123 ATA command execute
131 causes an ATA command, previously loaded with ``->tf_load()``, to be
143 Allow low-level driver to filter ATA PACKET commands, returning a status
150 Read specific ATA shadow registers
159 Reads the Status/AltStatus ATA shadow register from hardware. On some
164 Write specific ATA shadow register
172 Write the device control ATA shadow register to the hardware. Most
175 Select ATA device on bus
185 the ATA bus. This generally has no meaning on FIS-based devices.
199 with the ATA timing rules and also applies blacklists and cable limits.
201 typically raid controllers that use ATA commands but do not actually do
404 advised to read SCSI EH (Documentation/scsi/scsi_eh.txt) and ATA
455 ``qc->complete_fn()`` callback is used for completion notification. ATA
471 Currently 6 ATA command protocols are used. They can be sorted into the
474 ATA NO DATA or DMA
479 ATA PIO
579 conditions are represented with ATA STATUS and ERROR registers.
580 Errors which aren't ATA device errors are treated as ATA device
582 properly represent ATA and other errors/exceptions is needed.
597 - ATA errors are directly handled in the interrupt handler and PIO
637 ATA errors and exceptions
641 ATA/ATAPI devices and describe how they should be handled in
669 during issuing or execution any ATA/ATAPI command.
679 is transferred. ATA/ATAPI standard states that "The device shall not
693 ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION)
696 These are errors detected and reported by ATA/ATAPI devices indicating
698 values are valid and describe error condition. Note that some of ATA bus
699 errors are detected by ATA/ATAPI devices and reported using the same
703 For ATA commands, this type of errors are indicated by !BSY && ERR
718 Of errors detected as above, the following are not ATA/ATAPI device
719 errors but ATA bus errors and should be handled according to
720 `ATA bus error <#excatATAbusErr>`__.
724 corruption occurred during data transfer. Up to ATA/ATAPI-7, the
726 transfers but ATA/ATAPI-8 draft revision 1f says that the bit may be
730 Up to ATA/ATAPI-7, the standard specifies that ABRT could be set on
733 aren't allowed to use ICRC bit up to ATA/ATAPI-7, it seems to imply
736 However, ATA/ATAPI-8 draft revision 1f removes the part that ICRC
740 ATA/ATAPI device errors can be further categorized as follows.
743 This is indicated by UNC bit in the ERROR register. ATA devices
749 but ATA/ATAPI standard specifies that the amount of transferred data
768 up to ATA/ATAPI-7 no definition of "na" can be found. However,
769 ATA/ATAPI-8 draft revision 1f describes "N/A" as follows.
789 similarly to other SCSI errors. Note that sense data may indicate ATA
791 PARITY ERROR). In such cases, the error should be considered as an ATA
792 bus error and handled according to `ATA bus error <#excatATAbusErr>`__.
794 ATA device error (NCQ)
805 command can be handled as a normal ATA command error as in
806 `ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION) <#excatDevErr>`__
811 Note that ATA bus errors can be reported as ATA device NCQ errors. This
812 should be handled as described in `ATA bus error <#excatATAbusErr>`__.
818 ATA bus error
821 ATA bus error means that data corruption occurred during transmission
822 over ATA bus (SATA or PATA). This type of errors can be indicated by
825 `ATA/ATAPI device error (non-NCQ / non-CHECK CONDITION) <#excatDevErr>`__.
841 likely to indicate ATA bus error.
843 Once it's determined that ATA bus errors have possibly occurred,
844 lowering ATA bus transmission speed is one of actions which may
875 `ATA bus error <#excatATAbusErr>`__ for more details.
913 - When it's known that HBA is in ready state but ATA/ATAPI device is in
925 OTOH, ATA/ATAPI standard describes in detail ways to reset ATA/ATAPI
942 Although ATA/ATAPI standard doesn't describe exactly, EDD implies
978 ATA/ATAPI standard specifies that some parameters must be maintained
984 Also, ATA/ATAPI standard requires that IDENTIFY DEVICE / IDENTIFY PACKET
1021 The bulk of the ATA knowledge comes thanks to long conversations with
1022 Andre Hedrick (www.linux-ide.org), and long hours pondering the ATA and