From: Tejun Heo <htejun@gmail.com>
To: Fajun Chen <fajunchen@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: How to make SATA hotplug path tight?
Date: Tue, 19 Sep 2006 12:11:46 +0900 [thread overview]
Message-ID: <450F5FF2.9030208@gmail.com> (raw)
In-Reply-To: <8202f4270609181218h160b8df7x4853f58429229b3b@mail.gmail.com>
[adding linux-ide back, please don't drop it]
Fajun Chen wrote:
> Hi Tejun,
>
> I try to understand your eh code and still have several questions:
>
> 1. Why software is needed after hard reset under certain condition?
Because some controllers including sil24 cannot acquire device signature
after hardreset.
> rc = ata_do_reset(ap, reset, classes);
> did_followup_srst = 0;
> if (reset == hardreset &&
> ata_eh_followup_srst_needed(rc, classify, classes)) {
> /* okay, let's do follow-up softreset */
> did_followup_srst = 1;
> reset = softreset;
> ...
> Sometimes this part of the code costed as many as 7 secs:
> [ 366.400000] ata2: hard resetting port
> [ 366.400000] sata_phy_debounce: ENTER
> [ 368.490000] sata_phy_debounce: EXIT
> [ 368.490000] sil24_softreset: ENTER
> [ 375.750000] ata_dev_classify: found ATA device by sig
> [ 375.750000] sil24_softreset: EXIT, class=1
> Is there any way to get drive going without going through this?
Well, on hotplug case, you need to detect which class of device is
attached, so you need a softreset there.
> 2. What's the concept of port suspend and resume?
Port being suspended and resumed, I think. :-) You need ask more
specifically.
--
tejun
prev parent reply other threads:[~2006-09-19 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 15:12 How to make SATA hotplug path tight? Fajun Chen
2006-09-15 17:11 ` Leon Woestenberg
2006-09-15 19:40 ` Fajun Chen
2006-09-15 18:09 ` Tejun Heo
2006-09-15 19:48 ` Fajun Chen
2006-09-16 1:52 ` Tejun Heo
[not found] ` <8202f4270609181218h160b8df7x4853f58429229b3b@mail.gmail.com>
2006-09-19 3:11 ` Tejun Heo [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=450F5FF2.9030208@gmail.com \
--to=htejun@gmail.com \
--cc=fajunchen@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).