linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Albert Lee <albertcc@tw.ibm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Doug Maxey <dwm@maxeymade.com>,
	Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 1/1] libata: Handle ATAPI interrupt before CDB is sent
Date: Wed, 8 Jun 2005 12:01:10 +0200	[thread overview]
Message-ID: <58cb370e05060803014046ef0b@mail.gmail.com> (raw)
In-Reply-To: <42A6A60D.7020807@tw.ibm.com>

Hi Albert,
Hi Jeff,

On 6/8/05, Albert Lee <albertcc@tw.ibm.com> wrote:

> @@ -3457,6 +3461,32 @@
>  {
>         u8 status, host_stat;
> 
> +       /* ATAPI: Handle the interrupt before CDB is sent */
> +       if (is_atapi_taskfile(&qc->tf) &&
> +           ap->pio_task_state != PIO_ST_CDB_SENT) {
> +               /* check whether it's our irq */
> +               host_stat = ap->ops->bmdma_status(ap);
> +
> +               if (host_stat & ATA_DMA_INTR) {
> +                       /* Some pre-ATAPI-4 devices assert INTRQ here
> +                        * if nIEN is zero. qc->dev->id[0] bits 5-6 can
> +                        * be used to identify such devices.
> +                        */
> +                       DPRINTK("ata%u: atapi interrupt handled\n", ap->id);

This looks wrong for ATA_PROT_ATAPI_[NODATA],
we can't expect host to support DMA.

> +
> +                       /* clear INTRQ */
> +                       status = ata_chk_status(ap);
> +
> +                       /* clear bmdma status irq bit */
> +                       ap->ops->irq_clear(ap);
> +
> +                       return 1;       /* irq handled */
> +               } else {
> +                       DPRINTK("ata%u: not my atapi interrupt\n", ap->id);
> +                       goto idle_irq;
> +               }
> +       }
> +
>         switch (qc->tf.protocol) {
> 
>         case ATA_PROT_DMA:

	case ATA_PROT_DMA:
	case ATA_PROT_ATAPI_DMA:
	case ATA_PROT_ATAPI:
		/* check status of DMA engine */
		host_stat = ap->ops->bmdma_status(ap);
		VPRINTK("ata%u: host_stat 0x%X\n", ap->id, host_stat);

		/* if it's not our irq... */
		if (!(host_stat & ATA_DMA_INTR))
			goto idle_irq;

		/* before we do anything else, clear DMA-Start bit */
		ap->ops->bmdma_stop(ap);

		/* fall through */

ditto (vanilla libata-core.c)

Bartlomiej

  reply	other threads:[~2005-06-08 10:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29  9:27 [PATCH 0/2] libata-2.6: Fix races caused by the interrupt handler Albert Lee
2005-04-29  9:34 ` [PATCH 1/2] libata-2.6: Prevent the interrupt handler from completing a command twice Albert Lee
2005-05-15 22:47   ` Jeff Garzik
2005-04-29  9:39 ` [PATCH 2/2] libata-2.6: Ignore interrupt before the ATAPI CDB is sent to the device Albert Lee
2005-05-15 22:49   ` Jeff Garzik
2005-05-16 10:37     ` Albert Lee
2005-06-08  8:02       ` [PATCH 1/1] libata: Handle ATAPI interrupt before CDB is sent Albert Lee
2005-06-08 10:01         ` Bartlomiej Zolnierkiewicz [this message]
2005-06-08 12:17           ` Albert Lee
2005-06-09  7:13           ` Albert Lee
2005-06-28  3:06       ` [PATCH 2/2] libata-2.6: Ignore interrupt before the ATAPI CDB is sent to the device Jeff Garzik
2005-06-28 10:05         ` 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=58cb370e05060803014046ef0b@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=albertcc@tw.ibm.com \
    --cc=dwm@maxeymade.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    /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).