From: Jeff Garzik <jgarzik@pobox.com>
To: Albert Lee <albertcc@tw.ibm.com>
Cc: Linux IDE <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@maxeymade.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: [PATCH 3/3] libata-dev: Fix pdc2027x ATAPI DMA lost irq problem
Date: Wed, 10 Aug 2005 23:05:43 -0400 [thread overview]
Message-ID: <42FAC087.2000800@pobox.com> (raw)
In-Reply-To: <42F252ED.8020206@tw.ibm.com>
Albert Lee wrote:
> Jeff,
>
> Patch 3/3: Fix pdc2027x ATAPI DMA lost irq problem
>
> Description:
> Sometimes pdc2027x will lost irq after ATAPI DMA data transfer.
> With the previous rule (cmd->request_bufflen % 256), the ATAPI DMA irq
> lost
> problem still occurs during the test.
>
> Root cause for the irq lost is unknown. I've tried your ATAPI DMA
> alignment
> patch, but the problem still occurs, even the buffer is aligned. I guess
> it is pdc2027x hardware problem.
>
> The following workarounds are adapted from the Promise pdc618 GPL driver.
> They seems know about the problem and has the workaround.
I think this needs to be investigated a bit more, but the pdc618 driver
does it, we may need to do this eventually.
Jeff
prev parent reply other threads:[~2005-08-11 3:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 17:17 [PATCH 0/3] libata-dev: pdc2027x fixes Albert Lee
2005-08-04 17:32 ` [PATCH 1/3] libata-dev: Convert pdc2027x from PIO to MMIO Albert Lee
2005-08-04 19:40 ` Brett Russ
2005-08-09 11:04 ` Albert Lee
2005-08-11 2:37 ` Jeff Garzik
2005-08-11 3:03 ` Jeff Garzik
2005-08-11 9:49 ` Albert Lee
2005-08-11 17:49 ` Jeff Garzik
2005-08-04 17:34 ` [PATCH 2/3] libata-dev: pdc2027x mdelay() problem fix for power5 micro-partitioning Albert Lee
2005-08-07 9:18 ` Benjamin Herrenschmidt
2005-08-11 3:04 ` Jeff Garzik
2005-08-11 8:36 ` Benjamin Herrenschmidt
2005-08-11 9:52 ` Albert Lee
2005-08-04 17:39 ` [PATCH 3/3] libata-dev: Fix pdc2027x ATAPI DMA lost irq problem Albert Lee
2005-08-04 18:41 ` Doug Maxey
2005-08-11 3:05 ` Jeff Garzik [this message]
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=42FAC087.2000800@pobox.com \
--to=jgarzik@pobox.com \
--cc=albertcc@tw.ibm.com \
--cc=bzolnier@gmail.com \
--cc=dwm@maxeymade.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).