linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Mark Lord <liml@rtr.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Pavel Machek <pavel@suse.cz>, Jeff Garzik <jeff@garzik.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata hibernation fixes
Date: Tue, 04 Nov 2008 20:24:10 -0600	[thread overview]
Message-ID: <491103CA.7090905@shaw.ca> (raw)
In-Reply-To: <49110093.5090506@rtr.ca>

Mark Lord wrote:
> Robert Hancock wrote:
>>
>> IDLE IMMEDIATE just transitions the device to the Idle state, which is 
>> normally parked/unloaded and spun down.
> ..
> 
> No, you're confusing "IDLE" with "STANDBY".  IDLE just puts the drive
> electronics into a lower-power state than "ACTIVE", but normally leaves
> the platters spinning.
> 
> The "UNLOAD" enhancement causes it to also "unload" or "park" (drive's 
> option)
> the heads as part of this action.
> 
> "STANDBY" is the command set which parks heads and spins down the platters.

Right, STANDBY IMMEDIATE was the one I was thinking of.

  reply	other threads:[~2008-11-05  2:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.Ast7pgG6P20u1PcyOsfgzoaX5YA@ifi.uio.no>
     [not found] ` <fa.1+JQHm7yjIiZJxAzR0eBPn39a9M@ifi.uio.no>
     [not found]   ` <fa.+bfipgmFkcLlZMtnFL0Ks2zyN8Q@ifi.uio.no>
     [not found]     ` <fa.Iek0GbTZLinM2sOi6+b7bsCgnfs@ifi.uio.no>
2008-11-05  0:01       ` [git patches] libata hibernation fixes Robert Hancock
2008-11-05  0:45         ` Elias Oltmanns
2008-11-05  2:30           ` Tejun Heo
2008-11-05  9:31             ` Elias Oltmanns
2008-11-05  9:37               ` Tejun Heo
2008-11-05 14:37               ` Robert Hancock
     [not found]   ` <fa.8GbzH83c2CAI53n9dyzVOFugmoc@ifi.uio.no>
     [not found]     ` <fa.hGdpNHQGmXAR19JiGuHxSr9N9CA@ifi.uio.no>
2008-11-05  0:20       ` Robert Hancock
2008-11-05  2:10         ` Mark Lord
2008-11-05  2:24           ` Robert Hancock [this message]
2009-01-27  7:31 Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2008-11-04  6:27 Jeff Garzik
2008-11-04 16:29 ` Linus Torvalds
2008-11-04 16:53   ` Rafael J. Wysocki
2008-11-04 16:59     ` Mark Lord
2008-11-04 17:07       ` Rafael J. Wysocki
2008-11-05  2:17         ` Tejun Heo
2008-11-04 20:30   ` Pavel Machek
2008-11-04 21:08     ` Rafael J. Wysocki
2008-11-04 21:12     ` Linus Torvalds
2008-11-05  2:23       ` Tejun Heo
2008-11-05  2:42   ` Tejun Heo
2008-11-10  8:52     ` Tejun Heo
2009-01-02  2:36 ` Tejun Heo
2009-01-05  8:34   ` Jeff Garzik
2009-01-11  5:44   ` Jeff Garzik
2009-01-11 12:43     ` Rafael J. Wysocki
2009-01-18 10:20       ` Frans Pop
2009-01-18 20:25         ` Rafael J. Wysocki
2009-01-18 20:39           ` Jeff Garzik
2009-01-18 20:59           ` Frans Pop
2009-01-18 22:52             ` Rafael J. Wysocki

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=491103CA.7090905@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=torvalds@linux-foundation.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).