From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
stable@kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes UPDATED] sata_nv: fix generic, nf2/3 detection regression
Date: Tue, 04 Nov 2008 01:10:43 -0500 [thread overview]
Message-ID: <490FE763.1060704@garzik.org> (raw)
In-Reply-To: <490E720D.7070101@kernel.org>
Tejun Heo wrote:
> All three flavors of sata_nv's are different in how their hardreset
> behaves.
>
> * generic: Hardreset is not reliable. Link often doesn't come online
> after hardreset.
>
> * nf2/3: A little bit better - link comes online with longer debounce
> timing. However, nf2/3 can't reliable wait for the first D2H
> Register FIS, so it can't wait for device readiness or classify the
> device after hardreset. Follow-up SRST required.
>
> * ck804: Hardreset finally works.
>
> The core layer change to prefer hardreset and follow up changes
> exposed the above issues and caused various detection regressions for
> all three flavors. This patch, hopefully, fixes all the known issues
> and should make sata_nv error handling more reliable.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> Forgot to update comment for longer debounce timing required for
> nf2/3. Commit message and comment updated.
>
> drivers/ata/sata_nv.c | 53 +++++++++++++++++++++++---------------------------
> 1 file changed, 25 insertions(+), 28 deletions(-)
applied
prev parent reply other threads:[~2008-11-04 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 3:14 [PATCH #upstream-fixes] sata_nv: fix generic, nf2/3 detection regression Tejun Heo
2008-11-03 3:37 ` [PATCH #upstream-fixes UPDATED] " Tejun Heo
2008-11-04 6:10 ` 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=490FE763.1060704@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.