LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Eric D. Mudama" <edmudama@gmail.com>
To: "Henrique de Moraes Holschuh" <hmh@hmh.eng.br>
Cc: "Soeren Sonnenburg" <kernel@nn7.de>,
	"Tejun Heo" <htejun@gmail.com>, "Jeff Garzik" <jeff@garzik.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: SATA hotplug from the user side ?
Date: Thu, 25 Jan 2007 14:21:48 -0700	[thread overview]
Message-ID: <311601c90701251321s58c8c0e2s9050fbf9c41cabad@mail.gmail.com> (raw)
In-Reply-To: <20070124153727.GC15402@khazad-dum.debian.net>

On 1/24/07, Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> Tejun, is it feasible to teach libata to check the device power management
> state before issuing any of the sleep, head unload and spin-down commands?
>
> libata would need to block its EH from resetting a channel for this check
> operation (we don't want to wake up sleeping devices to ask it if it is
> sleeping...) if it cannot easily check if an device is asleep before issuing
> a command to it.   Either that, or (for as long as there is no such a thing
> as a multi-initiator libata device) just keep track of the device power
> management state by snooping all the commands sent to it.

In the ATA spec, the CHECK POWER MODE command (E5h) specifically
states that it shouldn't alter the power mode of the device.
Therefore, there should be no harm in checking the power mode of a
device in STANDBY or IDLE state, and it shouldn't cause the device to
spin up.  Checking a drive on my bench I confirmed this behavior.

With Serial ATA you have to consider the SATA bus PM states as well,
but that's a different topic of discussion.

--eric

  parent reply	other threads:[~2007-01-25 21:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  7:57 Soeren Sonnenburg
2007-01-12 17:04 ` Jeff Garzik
2007-01-12 22:07   ` Soeren Sonnenburg
2007-01-13  1:55     ` Tejun Heo
2007-01-13  7:22       ` Soeren Sonnenburg
2007-01-15  2:21         ` Tejun Heo
2007-01-22  9:04           ` Soeren Sonnenburg
2007-01-22 21:03             ` Henrique de Moraes Holschuh
2007-01-23  6:23               ` Tejun Heo
2007-01-23 13:10                 ` Henrique de Moraes Holschuh
2007-01-24  2:07                   ` Tejun Heo
2007-01-24  9:09                     ` Soeren Sonnenburg
2007-01-24 15:37                       ` Henrique de Moraes Holschuh
2007-01-25 12:56                         ` Soeren Sonnenburg
2007-01-25 21:56                           ` Henrique de Moraes Holschuh
2007-01-25 21:21                         ` Eric D. Mudama [this message]
2007-02-05 11:56                           ` Tejun Heo
2007-02-05 11:50                         ` Tejun Heo
2007-01-23  6:19             ` Tejun Heo
     [not found] <fa.pn1gmGiSlhDVMiPyzEEm1A66vcY@ifi.uio.no>
     [not found] ` <fa.Od11QHN89ZQ9VkFktF6HvxWuLV0@ifi.uio.no>
     [not found]   ` <fa.vsuV8EVipw4cXaHgzWpaf0q1pAA@ifi.uio.no>
     [not found]     ` <fa.8a1kVu4a2ISeaFZcL3migbjZ5N0@ifi.uio.no>
     [not found]       ` <fa.79JzgEcD2u5B9SYqrw3sr5b+iy8@ifi.uio.no>
     [not found]         ` <fa.DH50RMz6OHKG0AoGA/cChsCW8Ig@ifi.uio.no>
2007-01-25  0:33           ` Robert Hancock

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=311601c90701251321s58c8c0e2s9050fbf9c41cabad@mail.gmail.com \
    --to=edmudama@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: SATA hotplug from the user side ?' \
    /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

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).