From: Albert Lee <albertcc@tw.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: albertl@mail.com, Tejun Heo <htejun@gmail.com>,
Nicolas STRANSKY <Nico@stransky.cx>,
linux-ide@vger.kernel.org, Doug Maxey <dwm@maxeymade.com>
Subject: Re: [PATCH 1/1] libata: Fix the HSM error_mask mapping
Date: Fri, 19 May 2006 13:22:59 +0800 [thread overview]
Message-ID: <446D5633.9010309@tw.ibm.com> (raw)
In-Reply-To: <446D3EC8.5070109@tw.ibm.com>
Albert Lee wrote:
> Jeff Garzik wrote:
>
>>Tejun Heo wrote:
>>
>>
>>>It seems that HSM_ST needs to handle !DRQ && ERR case before the first
>>>iteration (or maybe it should be pushed into HSM_ST_FIRST?). Does my
>>>analysis make sense?
>>
>>
>>Agreed, though we should check for ERR on ATAPI path first, too, IMO.
>>
>
>
> Fix the HSM error_mask mapping.
>
> Changes:
> - Better mapping in ac_err_mask()
> - In HSM_ST_FIRST ans HSM_ST state, check ATA_ERR|ATA_DF and map it to AC_ERR_DEV instead of AC_ERR_HSM.
> - In HSM_ST_FIRST and HSM_ST state, map DRQ=1 ERR=1 to AC_ERR_HSM.
> - For PIO data in and DRQ=1 ERR=1, add check after the junk data block is read.
>
> Signed-off-by: Albert Lee <albertcc@tw.ibm.com>
> ---
> The device might stop the HSM by BSY=0 DRQ=1 ERR=1 when it finds something wrong.
Sorry, it should be
"The device might stop the HSM by BSY=0 DRQ=0 ERR=1 when it finds something wrong."
-- albert
> Map this condition to AC_ERR_DEV for accuracy.
> This should fix the problem of SMART reported by Nicolas.
> (patch against upstream branch.)
prev parent reply other threads:[~2006-05-19 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 22:41 libata-tj and SMART Nicolas STRANSKY
2006-05-15 23:13 ` Tejun Heo
2006-05-16 7:44 ` Nicolas STRANSKY
2006-05-16 8:11 ` Tejun Heo
2006-05-16 8:36 ` Nicolas STRANSKY
2006-05-17 21:15 ` Nicolas STRANSKY
2006-05-18 4:00 ` Tejun Heo
2006-05-18 15:54 ` Jeff Garzik
2006-05-19 3:43 ` [PATCH 1/1] libata: Fix the HSM error_mask mapping (was: Re: libata-tj and SMART) Albert Lee
2006-05-19 5:22 ` Albert Lee [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=446D5633.9010309@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=Nico@stransky.cx \
--cc=albertl@mail.com \
--cc=dwm@maxeymade.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).