From: Jeff Garzik <jgarzik@pobox.com>
To: gp <poppitzg@iomega.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATAPI timing
Date: Fri, 28 Jan 2005 12:47:43 -0500 [thread overview]
Message-ID: <41FA7ABF.7080404@pobox.com> (raw)
In-Reply-To: <83EB8C3C-7142-11D9-B91E-000A95D2AC6A@iomega.com>
gp wrote:
> Jeff
>
> I think I may have found an issue in the ATAPI code in the function
> atapi_packet_task.
>
> From my testing with the sata_via driver, I have been getting a timeout
> when sending the first inquiry command.
>
>
> Here is the section of code of interest:
>
>
> /* make sure DRQ is set */
> status = ata_chk_status(ap);
> if ((status & (ATA_BUSY | ATA_DRQ)) != ATA_DRQ)
> goto err_out;
>
> /* send SCSI cdb */
> DPRINTK("send cdb\n");
> assert(ap->cdb_len >= 12);
> ata_data_xfer(ap, qc->cdb, ap->cdb_len, 1);
>
> ** Wait is needed here to work correctly
> DPRINTK("Wait for a bit\n");
>
> /* if we are DMA'ing, irq handler takes over from here */
> if (qc->tf.protocol == ATA_PROT_ATAPI_DMA)
> ap->ops->bmdma_start(qc); /* initiate bmdma */
>
>
> In the test case, the dma transfer is being used. From my perusal of the
> ATA spec in section 9.8, it looks like there needs to be a definite
> state transition before issuing the bmdma_start.
Yeah, it looks like there needs to be an intrq-wait state in there...
Wanna submit a patch? :)
Jeff
next prev parent reply other threads:[~2005-01-28 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 15:37 SATAPI timing gp
2005-01-28 17:47 ` Jeff Garzik [this message]
2005-02-01 10:49 ` Albert Lee
2005-02-06 15:17 ` Jeff Garzik
2005-02-19 5:15 ` Jeff Garzik
2005-02-21 7:54 ` Jens Axboe
2005-02-22 6:33 ` Albert Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41FA7ABF.7080404@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=poppitzg@iomega.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.