All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: saeed bishara <saeed.bishara@gmail.com>
Cc: "Eric D. Mudama" <edmudama@gmail.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: question about boot time drive initialization
Date: Mon, 15 May 2006 22:52:36 +0900	[thread overview]
Message-ID: <446887A4.1060904@gmail.com> (raw)
In-Reply-To: <c70ff3ad0605150608h60d69592uadb0abd7ee2eaf62@mail.gmail.com>

saeed bishara wrote:
>> Hmmm.. weird.  That's not what I'm seeing.  AHCI reports command issue
>> failure if something goes wrong while transmitting D2H fis for a command
> you mean H2D, don't you?

Yeap.

>> (probably when it sees R_ERR).  If I issue SRST shortly after power-on,
>> AHCI fails SRST due to command issue failure.  So, it seems that the
>> device rejects SRST before it transmits the first FIS34.
> 
> there is also the possiblity that the AHCI doesn't issue the FIS34 as
> long as the BSY bit in the Status shadow register is set. so it's not
> the disk fault. I have taken a look at the AHCI spec, and found that
> you need to use the Commnad List Override (CLO) feature in order to
> send FIS while BSY is set. do you use that ?

AHCI driver does CLO if necessary before issuing SRST, so I don't think 
CLO is the issue here.

-- 
tejun

      reply	other threads:[~2006-05-15 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4466DE81.2040006@gmail.com>
     [not found] ` <311601c90605140929s5fe919efk69c59bd5f61fee7d@mail.gmail.com>
2006-05-15  1:50   ` question about boot time drive initialization Tejun Heo
2006-05-15 10:38     ` saeed bishara
2006-05-15 11:08       ` Tejun Heo
2006-05-15 13:08         ` saeed bishara
2006-05-15 13:52           ` Tejun Heo [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=446887A4.1060904@gmail.com \
    --to=htejun@gmail.com \
    --cc=edmudama@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=saeed.bishara@gmail.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 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.