diff options
| author | Tejun Heo | 2007-10-29 08:41:09 +0100 |
|---|---|---|
| committer | Jeff Garzik | 2007-10-29 11:21:33 +0100 |
| commit | cdeab1140799f09c5f728a5ff85e0bdfa5679cd2 (patch) | |
| tree | 51e70854ce9a41e3d7e0363fe5748635671b6a6f /drivers/ata/libata-eh.c | |
| parent | pata_ns87415: define SUPERIO_IDE_MAX_RETRIES (diff) | |
| download | kernel-qcow2-linux-cdeab1140799f09c5f728a5ff85e0bdfa5679cd2.tar.gz kernel-qcow2-linux-cdeab1140799f09c5f728a5ff85e0bdfa5679cd2.tar.xz kernel-qcow2-linux-cdeab1140799f09c5f728a5ff85e0bdfa5679cd2.zip | |
libata: relocate forcing PIO0 on reset
Forcing PIO0 on reset was done inside ata_bus_softreset(), which is a
bit out of place as it should be applied to all resets - hard, soft
and implementation which don't use ata_bus_softreset(). Relocate it
such that...
* For new EH, it's done in ata_eh_reset() before calling prereset.
* For old EH, it's done before calling ap->ops->phy_reset() in
ata_bus_probe().
This makes PIO0 forced after all resets. Another difference is that
reset itself is done after PIO0 is forced.
Signed-off-by: Tejun Heo <htejun@gmail.com>
Acked-by: Alan Cox <alan@redhat.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'drivers/ata/libata-eh.c')
| -rw-r--r-- | drivers/ata/libata-eh.c | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c index 496edaff119a..b237ff18b39e 100644 --- a/drivers/ata/libata-eh.c +++ b/drivers/ata/libata-eh.c @@ -2083,6 +2083,25 @@ int ata_eh_reset(struct ata_link *link, int classify, ata_eh_about_to_do(link, NULL, ehc->i.action & ATA_EH_RESET_MASK); + ata_link_for_each_dev(dev, link) { + /* If we issue an SRST then an ATA drive (not ATAPI) + * may change configuration and be in PIO0 timing. If + * we do a hard reset (or are coming from power on) + * this is true for ATA or ATAPI. Until we've set a + * suitable controller mode we should not touch the + * bus as we may be talking too fast. + */ + dev->pio_mode = XFER_PIO_0; + + /* If the controller has a pio mode setup function + * then use it to set the chipset to rights. Don't + * touch the DMA setup as that will be dealt with when + * configuring devices. + */ + if (ap->ops->set_piomode) + ap->ops->set_piomode(ap, dev); + } + /* Determine which reset to use and record in ehc->i.action. * prereset() may examine and modify it. */ |