From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: mlord@pobox.com, albertcc@tw.ibm.com, alan@lxorguk.ukuu.org.uk,
axboe@suse.de, forrest.zhao@intel.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 12/12] libata-hp-prep: implement followup softreset handling
Date: Tue, 30 May 2006 00:12:28 -0400 [thread overview]
Message-ID: <447BC62C.9080706@pobox.com> (raw)
In-Reply-To: <11488839582516-git-send-email-htejun@gmail.com>
Tejun Heo wrote:
> In some cases, hardreset must be followed by SRST.
>
> * some controllers can't classify with hardreset
> * some controllers can't wait for !BSY after hardreset (LLDD should
> explicitly request followup softreset by returning -EAGAIN)
> * (later) PM needs SRST w/ PMP==15 to operate after hardreset
>
> To handle above cases, this patch implements follow-up softreset.
> After a hardreset, ata_eh_reset() checks whether any of above
> conditions are met and do a follow-up softreset if necessary.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
ACK
next prev parent reply other threads:[~2006-05-30 4:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 6:25 [PATCHSET 01/03] prep for hotplug support, take 4 Tejun Heo
2006-05-29 6:25 ` [PATCH 02/12] libata-hp-prep: implement ata_dev_init() Tejun Heo
2006-05-29 6:25 ` [PATCH 01/12] libata-hp-prep: add flags and eh_info/context fields for hotplug Tejun Heo
2006-05-29 6:25 ` [PATCH 10/12] libata-hp-prep: implement sata_phy_debounce() Tejun Heo
2006-05-30 4:10 ` Jeff Garzik
2006-05-30 5:08 ` Tejun Heo
2006-05-30 5:23 ` Jeff Garzik
2006-05-29 6:25 ` [PATCH 07/12] libata-hp-prep: store attached SCSI device Tejun Heo
2006-05-29 8:45 ` zhao, forrest
2006-05-29 9:14 ` Tejun Heo
2006-05-30 4:04 ` Jeff Garzik
2006-05-30 4:55 ` Tejun Heo
2006-05-29 6:25 ` [PATCH 03/12] libata-hp-prep: make some ata_device fields persistent Tejun Heo
2006-05-30 4:00 ` Jeff Garzik
2006-05-29 6:25 ` [PATCH 05/12] libata-hp-prep: use __ata_scsi_find_dev() Tejun Heo
2006-05-29 6:25 ` [PATCH 11/12] libata-hp-prep: add prereset() method and implement ata_std_prereset() Tejun Heo
2006-05-29 11:12 ` [PATCH 11/12] (updated) " Tejun Heo
2006-05-30 4:12 ` Jeff Garzik
2006-05-29 6:25 ` [PATCH 12/12] libata-hp-prep: implement followup softreset handling Tejun Heo
2006-05-30 4:12 ` Jeff Garzik [this message]
2006-05-29 6:25 ` [PATCH 09/12] libata-hp-prep: make probing related functions global Tejun Heo
2006-05-30 4:06 ` Jeff Garzik
2006-05-29 6:25 ` [PATCH 06/12] libata-hp-prep: implement ap->hw_sata_spd_limit Tejun Heo
2006-05-29 6:25 ` [PATCH 04/12] libata-hp-prep: update ata_scsi_find_dev() and friends Tejun Heo
2006-05-29 8:40 ` zhao, forrest
2006-05-29 9:09 ` Tejun Heo
2006-05-30 4:38 ` Jeff Garzik
2006-05-30 4:02 ` Jeff Garzik
2006-05-30 4:26 ` Tejun Heo
2006-05-30 4:37 ` Jeff Garzik
2006-05-30 4:43 ` Tejun Heo
2006-05-29 6:25 ` [PATCH 08/12] libata-hp-prep: add ata_scsi_wq Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 11:05 [PATCHSET 01/03] prep for hotplug support, take 5 Tejun Heo
2006-05-31 11:05 ` [PATCH 12/12] libata-hp-prep: implement followup softreset handling 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=447BC62C.9080706@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=axboe@suse.de \
--cc=forrest.zhao@intel.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.com \
/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).