linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, albertcc@tw.ibm.com, linux-ide@vger.kernel.org
Cc: htejun@gmail.com
Subject: [PATCHSET] libata: various fixes related to EH, take #4
Date: Fri, 10 Feb 2006 23:58:48 +0900	[thread overview]
Message-ID: <11395835282719-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: 


Hello, Jeff.

< %nn denotes patch nn from the last iteration, #nn in this iteration >

This is the fourth take of new reset mechanism.  4 (%01-%04) out of 11
patches made into upstream in the last iteration [1].  The rest are
acked but haven't been applied because standard reset operations need
more changes before being used.

This patchset is composed of 9 patches.

#01-02	: modify std reset operations such that they act almost
	  identically with ->phy_reset register-wise.
#03-09	: These seven patches are %05-%09 with minor changes.

After #01, the only meaningful difference of the new reset mechanism
from ->phy_reset is that SError is cleared after SATA hardreset.  This
difference is removed by #02.  #02 is separated to make the change
optional.  If #02 gets into upstream, I'll have to submit another
patch to resurrect it later for EH.  Jeff, it's your call.

After #01 and #02, the following differences remain.

1. SStatus access for sata_print_link_status() in ata_std_postreset()
   is at different postion register-wise compared to ->phy_reset.

2. ->phy_reset doesn't proceed with softreset if ata_busy_sleep()
   fails after PHY is waken, but new reset mechanism proceeds anyway.
   Note that the original code is not very consistent regarding this.
   Some drivers (e.g. ata_piix), uses ata_bus_reset() instead of
   sata_phy_reset() and thus doesn't perform ata_busy_sleep() before
   SRST in the first place.

If a low level driver uses ata_std_probeinit() but doesn't implement
softreset, it will end up performing extra phy_resume and
ata_busy_sleep before the actual hardreset sequence compared to
->phy_reset.  This is noted int the comment above ata_std_probeinit().

#08 has been modified not to use ata_std_probeinit() because it only
implements hardreset, but #09 implements softreset and adds
ata_std_probeinit() back; thus, the end result is unchanged.

Thanks.

--
tejun

[1] http://article.gmane.org/gmane.linux.ide/7804


             reply	other threads:[~2006-02-10 14:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 14:58 Tejun Heo [this message]
2006-02-10 14:58 ` [PATCH 7/9] ata_piix: convert sata to new reset mechanism Tejun Heo
2006-02-11 23:30   ` Jeff Garzik
2006-02-10 14:58 ` [PATCH 5/9] sata_sil24: add hardreset Tejun Heo
2006-02-10 14:58 ` [PATCH 3/9] sata_sil: convert to new reset mechanism Tejun Heo
2006-02-10 14:58 ` [PATCH 1/9] libata: make new reset act identical to ->phy_reset register-wise Tejun Heo
2006-02-10 15:30   ` Jeff Garzik
2006-02-10 14:58 ` [PATCH 6/9] ata_piix: convert pata to new reset mechanism Tejun Heo
2006-02-11 23:29   ` Jeff Garzik
2006-02-10 14:58 ` [PATCH 2/9] libata: kill SError clearing in sata_std_hardreset() Tejun Heo
2006-02-10 14:58 ` [PATCH 4/9] sata_sil24: convert to new reset mechanism Tejun Heo
2006-02-10 14:58 ` [PATCH 9/9] ahci: add softreset Tejun Heo
2006-02-10 14:58 ` [PATCH 8/9] ahci: convert to new reset mechanism Tejun Heo
2006-02-10 15:01 ` Sorry, wrong PATCHSET name, it should be [PATCHSET] libata: various fixes related to EH, take #4 Tejun Heo
2006-02-10 15:04   ` Gee, wrong again. libata: [PATCHSET] libata: new reset mechanism, take#4 Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2006-02-10  6:10 [PATCHSET] libata: various fixes related to EH, take #4 Tejun Heo
2006-02-10 12:00 ` Jeff Garzik
2006-02-10 12:16   ` 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=11395835282719-git-send-email-htejun@gmail.com \
    --to=htejun@gmail.com \
    --cc=albertcc@tw.ibm.com \
    --cc=jgarzik@pobox.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).