public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: "Ortwin Glück" <odi@odi.ch>, "Tejun Heo" <tj@kernel.org>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ata link not reset properly
Date: Sun, 27 Jun 2010 22:27:32 +0400	[thread overview]
Message-ID: <4C279814.9030100@ru.mvista.com> (raw)
In-Reply-To: <4C257CEE.2070309@gmail.com>

Hello.

Robert Hancock wrote:

>> On 25.06.2010 17:19, Tejun Heo wrote:
>>> Patch attached, but please see below.

>> Cheers, I will give it a try and provide feedback if "it" happens again.

>>> Is it PATA?

>> Yes. This chipset doesn't have SATA, only PATA.

> Ahh, ok, it's not sata_nv at all then, it's pata_amd. On the same chip, 
> totally different controller though.

> PATA doesn't normally use hard-resets as a means of error recovery - 
> that would mean hitting the RESET line, which I don't think most 
> controllers can do on software command (it usually only gets asserted on 
> power up or hitting the reset button), unlike on SATA where there's a 
> defined way to trigger a COMRESET which is mostly equivalent. Also, that 
> resets both devices on the channel, unlike soft reset which is specific 
> to one device.

    PATA soft reset affects both devices too. Unless you mean ATAPI Device 
Reset command.

MBR, Sergei


      parent reply	other threads:[~2010-06-27 18:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 17:08 ata link not reset properly Ortwin Glück
2010-06-23 17:28 ` Tejun Heo
2010-06-23 17:31   ` Tejun Heo
2010-06-24  7:13     ` Ortwin Glück
2010-06-25 15:19       ` Tejun Heo
2010-06-25 18:00         ` Ortwin Glück
2010-06-26  4:07           ` Robert Hancock
2010-06-26  8:03             ` Tejun Heo
2010-06-26  9:00             ` Ortwin Glück
2010-06-27 18:27             ` Sergei Shtylyov [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=4C279814.9030100@ru.mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=odi@odi.ch \
    --cc=tj@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