From: Mikael Pettersson <mikpe@it.uu.se>
To: Tejun Heo <htejun@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
Christian Mueller <Christian.Mueller@wdc.com>,
Bruce Allen <ballen@gravity.phys.uwm.edu>,
Smartmontools Mailing List
<smartmontools-support@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [smartmontools-support] inactive SATA drives won't stay in standby or sleep, PATA models did. (fwd)
Date: Tue, 21 Oct 2008 11:30:25 +0200 [thread overview]
Message-ID: <18685.41265.560866.890756@harpo.it.uu.se> (raw)
In-Reply-To: <48FD9A90.8000205@gmail.com>
Tejun Heo writes:
> Hello,
>
> Mikael Pettersson wrote:
> > Tejun Heo writes:
> > > Hello, Mikael.
> > > I would put this into ->hardreset itself as the controller can also
> > > get out of sync with reality during reset.
> >
> > The only thing I see going on between prereset and (hard/soft)reset
> > is an optional freeze, so I don't see why moving the pdc_reset_port()
> > into the beginning of hardreset() would make any difference.
> >
> > sata_promise currently uses the ->hardreset and ->softreset inherited
> > from ata_sff_port_ops, so it would need to override both to ensure that
> > we always do pdc_reset_port() before libata does its thing. That's why
> > I felt doing that in ->prereset would be the right solution.
>
> Hmm.. reset sequence goes on like the following.
>
> 1. prereset
> 2. hardreset, if fail, retry
> 3. follow-up softreset if requested, if fail, goto #2
> 4. postreset, if successful
>
> So, if some PHY event happens while the reset is waiting for device
> readiness and makes the controller state go out of sync with the
> drive. ->prereset() will NOT be called for the following retry.
I see. Ok, then I'll forget about ->prereset and bind ->hardreset to
code which does pdc_reset_port() before invoking sata_sff_hardreset().
Thanks for your input.
/Mikael
next prev parent reply other threads:[~2008-10-21 9:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48EBFB63.20506@gmail.com>
2008-10-08 0:20 ` Christian Mueller
2008-10-08 0:28 ` Tejun Heo
2008-10-12 14:55 ` Mikael Pettersson
2008-10-13 5:16 ` Tejun Heo
2008-10-13 7:03 ` Mikael Pettersson
2008-10-13 7:08 ` Tejun Heo
2008-10-19 23:40 ` Mikael Pettersson
2008-10-21 4:18 ` Tejun Heo
2008-10-21 7:56 ` Mikael Pettersson
2008-10-21 9:02 ` Tejun Heo
2008-10-21 9:30 ` Mikael Pettersson [this message]
2008-10-21 7:59 ` Mikael Pettersson
2008-10-21 8:55 ` Tejun Heo
[not found] <Pine.LNX.4.64.0809142159550.18213@gc.phys.uwm.edu>
[not found] ` <48E1B8F8.3090205@gmail.com>
[not found] ` <48E26BDA.8080804@tlinx.org>
[not found] ` <48E26E61.2010705@gmail.com>
[not found] ` <48E34BC8.3050009@tlinx.org>
[not found] ` <48E6DE07.70706@gmail.com>
2008-10-07 0:37 ` Linda Walsh
2008-10-07 1:08 ` Tejun Heo
2008-10-07 1:36 ` Linda Walsh
2008-10-07 1:42 ` Tejun Heo
2008-10-07 10:13 ` Linda Walsh
2008-10-07 22:27 ` Linda Walsh
2008-10-07 23:59 ` Tejun Heo
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=18685.41265.560866.890756@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=Christian.Mueller@wdc.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smartmontools-support@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®