Lines Matching refs:libata
18 libata Driver API
22 is defined for every low-level libata
61 optional ``->mode_filter()`` hook is called when libata has built a mask of
131 This hook may be specified as NULL, in which case libata will assume
182 By default libata performs drive and controller tuning in accordance
318 system, by libata. ``->irq_clear`` is called during probe just before the
378 This chapter describes how errors are handled under libata. Readers are
385 In libata, a command is represented with
392 libata commands can originate from two sources - libata itself and SCSI
393 midlayer. libata internal commands are used for initialization and error
414 All libata drivers use :c:func:`ata_scsi_queuecmd` as
444 ATA_PROT_PIO is in this category. libata currently implements PIO
513 for libata. As discussed above, this will be entered in two cases -
516 EH will know to handle it later. Then it calls low level libata driver's
573 difficult. Low level drivers override libata callbacks. If EH is
577 libata Library
580 .. kernel-doc:: drivers/ata/libata-core.c
583 libata Core Internals
586 .. kernel-doc:: drivers/ata/libata-core.c
589 .. kernel-doc:: drivers/ata/libata-eh.c
591 libata SCSI translation/emulation
594 .. kernel-doc:: drivers/ata/libata-scsi.c
597 .. kernel-doc:: drivers/ata/libata-scsi.c
989 and in general for motivation to hack on libata.
991 libata's device detection method, ata_pio_devchk, and in general all