From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Albert Lee <albertcc@tw.ibm.com>, gp <poppitzg@iomega.com>,
linux-ide@vger.kernel.org
Subject: Re: SATAPI timing
Date: Mon, 21 Feb 2005 08:54:45 +0100 [thread overview]
Message-ID: <20050221075445.GU4056@suse.de> (raw)
In-Reply-To: <4216CB7E.1030109@pobox.com>
On Sat, Feb 19 2005, Jeff Garzik wrote:
> Albert Lee wrote:
> >I'm a little confused about what is the "correct behavior" of ATAPI DMA
> >INTRQ.
> >
> >1. The ATA-4 flowchart and ATA-6 state diagram seems to be inconsistent.
> >In the ATA-4 flowchart, no wait for INTRQ is specified.
> >
> >2. From the ATA-5 errata:
> >http://www.t13.org/project/e01122r0.pdf
> >
> >"...Page 265 through 270 of NCITS 340-2000 clause 9.8 was not properly
> >converted from the flow
> >charts in NCITS 317-1998 to the state diagrams. The state diagrams figures
> >33 and 34 and
> >associated text is modified to indicate that the device interrupts only at
> >command completion. "
> >
> >Notice the "device interrupts only at command completion." statement.
> >However, the diagrams in the errata are inconsistent with the above
> >statement.
> >
> >3. The ide-cd code does not wait for INTRQ before starting BM-DMA
> >
> > /* Arm the interrupt handler. */
> > ide_set_handler(drive, handler, rq->timeout, cdrom_timer_expiry);
> >
> > /* ATAPI commands get padded out to 12 bytes minimum */
> > cmd_len = COMMAND_SIZE(rq->cmd[0]);
> > if (cmd_len < ATAPI_MIN_CDB_BYTES)
> > cmd_len = ATAPI_MIN_CDB_BYTES;
> >
> > /* Send the command to the device. */
> > HWIF(drive)->atapi_output_bytes(drive, rq->cmd, cmd_len);
> >
> > /* Start the DMA if need be */
> > if (info->dma)
> > hwif->dma_start(drive);
> >
> > return ide_started;
> >
> >4. My CD-ROM drive does not generate INTRQ after it received the command
> >packet.
> > It only assert DMARQ.
> >
> >Maybe the state diagrams in ATA-5 and ATA-6 are incorrect? Any idea?
>
>
> As I mentioned in an earlier email, research seems to indicate the
> IDENTIFY PACKET DEVICE word 0, bits 6-5 can be used to indicate INTRQ
> will be delivered. This is consistent with my ATA-4 specification.
>
> Apparently this behavior is obsolete, but we still need to support it.
ide-cd uses those bits to check for interrupt delivery, see
drq_interrupt in that file.
--
Jens Axboe
next prev parent reply other threads:[~2005-02-21 7:55 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
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 [this message]
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=20050221075445.GU4056@suse.de \
--to=axboe@suse.de \
--cc=albertcc@tw.ibm.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).