All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>, Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] libata: Handle drives that require a spin-up command before first access
Date: Sat, 28 Apr 2007 14:41:15 -0400	[thread overview]
Message-ID: <4633954B.6040306@garzik.org> (raw)
In-Reply-To: <4625497F.7010109@rtr.ca>

Mark Lord wrote:
> 
> (S)ATA drives can be configured for "power-up in standby",
> a mode whereby a specific "spin up now!" command is required
> before the first media access.
> 
> Currently, a drive with this feature enabled can not be used at all
> with libata, and once in this mode, the drive becomes a doorstop.
> 
> The older drivers/ide subsystem at least enumerates the drive,
> so that it can be woken up after the fact from a userspace HDIO_*
> command, but not libata.
> 
> This patch adds support to libata for the "power-up in standby"
> mode where a "spin up now!" command (SET_FEATURES) is needed.
> With this, libata will recognize such drives, spin them up,
> and then re-IDENTIFY them if necessary to get a full/complete
> set of drive features data.
> 
> Drives in this state are determined by looking for
> special values in id[2], as documented in the current ATA specs.
> 
> Signed-off-by: Mark Lord <mlord@pobox.com>

applied

though I'm curious where the verify step went, that was in the previous 
rev of the patch



  reply	other threads:[~2007-04-28 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 22:26 [PATCH] libata: Handle drives that require a spin-up command before first access Mark Lord
2007-04-28 18:41 ` Jeff Garzik [this message]
2007-04-28 20:05   ` Mark Lord
  -- strict thread matches above, loose matches on Subject: below --
2007-04-19 13:40 Mark Lord
2007-04-20  4:46 ` 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=4633954B.6040306@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@redhat.com \
    --cc=htejun@gmail.com \
    --cc=liml@rtr.ca \
    --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 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.