From: Jeff Garzik <jgarzik@pobox.com>
To: albertl@mail.com
Cc: IDE Linux <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@maxeymade.com>,
edmudama@gmail.com
Subject: Re: [PATCH/RFC] libata-dev: handle ERR=1 DRQ=1
Date: Tue, 21 Mar 2006 12:35:15 -0500 [thread overview]
Message-ID: <44203953.3080803@pobox.com> (raw)
In-Reply-To: <441FE605.8010202@tw.ibm.com>
Albert Lee wrote:
> handle ERR=1 DRQ=1 for PIO protocol
>
> Signed-off-by: Albert Lee <albertcc@tw.ibm.com>
> ---
>
> Some PIO read commands might set DRQ=1 alone with ERR=1.
> Under such situation, the data block should be transferred even if err=1.
>
> This patch adds extra logic to HSM_ST_ERR to handle the required
> data transfer.
>
> BTW, also found the following work in progress:
> "Disable Data Transfer after Error Detection"
> http://t13.org/docs2006/dt1825Lr3-DDT_TR.pdf
> If this feature is turned on, then DRQ will be guaranteed 0 when ERR=1
> which would simplify the PIO error handling.
>
> Patch against the irq-pio branch.
> Need your review and advice, thanks.
If DRQ==1 then the error register and ATA_ERR should be considered
irrelevant. I agree with Eric, that's more of a "don't touch it, other
than to SRST it" situation.
Jeff
next prev parent reply other threads:[~2006-03-21 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 11:39 [PATCH/RFC] libata-dev: handle ERR=1 DRQ=1 Albert Lee
2006-03-21 17:35 ` Jeff Garzik [this message]
2006-03-21 17:43 ` Eric D. Mudama
2006-03-23 8:04 ` [PATCH 1/2] libata-dev: irq-pio minor fixes Albert Lee
2006-03-23 8:18 ` Jeff Garzik
2006-03-24 17:28 ` Jeff Garzik
2006-03-25 10:07 ` [PATCH 1/3] libata-dev: irq-pio minor fixes (respin) Albert Lee
2006-03-29 22:22 ` Jeff Garzik
2006-03-25 10:11 ` [PATCH 2/3] libata-dev: fix the device err check sequence (respin) Albert Lee
2006-03-25 10:18 ` [PATCH 3/3] libata-dev: wait idle after reading the last data block Albert Lee
2006-03-23 8:26 ` [PATCH/RFC 2/2] libata-dev: fix the device err check sequence 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=44203953.3080803@pobox.com \
--to=jgarzik@pobox.com \
--cc=albertl@mail.com \
--cc=dwm@maxeymade.com \
--cc=edmudama@gmail.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).