All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Peter Favrholdt <linux-ide@how.dk>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.31] sata_promise: update reset code
Date: Thu, 17 Sep 2009 16:50:44 -0400	[thread overview]
Message-ID: <4AB2A124.8010509@pobox.com> (raw)
In-Reply-To: <19119.37343.976763.528719@pilspetsen.it.uu.se>

On 09/15/2009 09:08 AM, Mikael Pettersson wrote:
> sata_promise's reset code has deviated quite a bit from
> the Promise reference driver's, and it has been observed
> to fail to recover from errors in some cases.
>
> This patch thus updates the reset code to more closely
> match the reference driver:
>
> - soft reset (pdc_reset_port):
>    * wait for ATA engine to not be in packet command mode
>      (2nd gen only)
>    * write reset bit in PDC_CTLSTAT before the first read
>      in the loop
>    * for 2nd gen SATA follow up with FPDMA reset and clearing
>      error status registers
> - hard reset (pdc_sata_hardreset):
>    * wait for ATA engine to not be in packet command mode
>      (2nd gen only)
>    * reset ATA engine via the PCI control register
>    * Tejun's change to use non-waiting hardreset + follow-up SRST
>
> I'm not changing the hotplug mask bits since they are taken care
> of by sata_promise's ->freeze() and ->thaw() operations. And I'm
> not writing the PMP port # because that's always zero (for now).
>
> Tested here on various controllers. In particular, one disk
> which used to timeout and fail to recover from certain hdparm
> and smartmonctl commands now works nicely.
>
> Signed-off-by: Mikael Pettersson<mikpe@it.uu.se>
> ---
> I should have submitted this long ago, sorry.
> This update involves a lot of details, so it should probably sit
> in a testing tree for a while before going upstream.
>
>   drivers/ata/sata_promise.c |  121 ++++++++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 120 insertions(+), 1 deletion(-)

applied -- I would rather push it to upstream and see what happens, 
given that waiting would probably mean less test exposure at this point 
[unless we wait a full release cycle]

	Jeff




  reply	other threads:[~2009-09-17 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 13:08 [PATCH 2.6.31] sata_promise: update reset code Mikael Pettersson
2009-09-17 20:50 ` Jeff Garzik [this message]
2009-09-18  1:05   ` Mikael Pettersson

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=4AB2A124.8010509@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@how.dk \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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.