linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] libata test-unit-ready for ATAPI devices
Date: Wed, 16 Nov 2005 07:46:28 -0500	[thread overview]
Message-ID: <437B2A24.9050508@pobox.com> (raw)
In-Reply-To: <20051116100117.GA22225@htj.dyndns.org>

Tejun Heo wrote:
> On Tue, Nov 15, 2005 at 11:48:41PM -0500, Jeff Garzik wrote:
> 
>>The following patch clears the "I was just reset" condition from an
>>ATAPI device, and waits for it to come online, before continuing with
>>the probe.
>>
>>Not checking this into any upstream-bound branch, as I'm not yet
>>convinced of its value.
>>
> 
> 
> How about the following one?  It doesn't make libata wait for the
> device to become ready before trying to configure ATA stuff.  It just
> makes sr wait for the device to become ready before performing SCSI
> configuration.  Maybe both are needed?

[thinking out loud]  My rationale for doing TUR in libata was to clear 
the UNIT ATTENTION that libata caused through software/hardware reset. 
Once the UNIT ATTENTION was cleared, my rationale for waiting for the 
NOT READY(BECOMING READY) condition was simply symmetry with other 
libata probe tasks, which similarly wait for device readiness.

However, given that sr is already coded to clear "the initial startup 
UNIT_ATTENTION", I tend to think your patch is more appropriate, and my 
patch should not be applied at all.

	Jeff



      reply	other threads:[~2005-11-16 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16  4:48 [PATCH] libata test-unit-ready for ATAPI devices Jeff Garzik
2005-11-16 10:01 ` Tejun Heo
2005-11-16 12:46   ` Jeff Garzik [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=437B2A24.9050508@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@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).