linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: linux-scsi@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Subject: SCSI, MMC, SAS and SATA power management
Date: Thu, 11 Aug 2005 16:24:46 +1000	[thread overview]
Message-ID: <42FAEF2E.3090102@torque.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While looking into implementing the START STOP UNIT
SCSI command for SATA disks, I spent some time looking
at power management state machines in various standards.
It is pretty confusing stuff so I have made a web page to
summarise the various states. See:
http://www.torque.net/sg/power.html


One linux (or device) problem I noticed while looking
at this was how lk 2.6.13-rc6 reacts when an ATAPI
cd/dvd drive is placed into SLEEP state. This isn't
a normal thing to do but can be done thus:
   sg_start -pc=5 /dev/hdd
where sg_start is found in the sg3_utils package. The
ATA8-ACS draft says that the device should first respond
to a SLEEP ATA command and thereafter not respond to
any commands until a reset occurs. One would think that
the MMC equivalent (i.e. START STOP UNIT command
[power_condition=5]) should react the same way. What I
observed on my laptop was about 10 minutes of timeouts
(with a message about lost interrupts every minute)
before things stabilised. Same thing occurred on a desktop
with a recent LG DVD+-R DL drive. I don't think kscd
polling the drive was helping.

Doug Gilbert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFC+u8unayo+9E+FQIRAknJAJ9wGSGIuhK7Hhd5gTd4bIj08GD+jACgovDm
q+/tSP5uo2LIFbQwENqc2j4=
=43KH
-----END PGP SIGNATURE-----

                 reply	other threads:[~2005-08-11  6:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42FAEF2E.3090102@torque.net \
    --to=dougg@torque.net \
    --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).