From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: JiSheng Zhang <jszhang3@gmail.com>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Do we need to implement sr START/STOP management
Date: Tue, 01 Nov 2011 16:35:36 +0400 [thread overview]
Message-ID: <1320150936.17402.10.camel@dabdike> (raw)
In-Reply-To: <CADyp2Pdac=z6KzKnNykBCZNRLnjkv-z901Hwd-U0o2wB2qHWOA@mail.gmail.com>
On Tue, 2011-11-01 at 14:35 +0800, JiSheng Zhang wrote:
> 2011/11/1 James Bottomley <James.Bottomley@hansenpartnership.com>:
> > On Tue, 2011-11-01 at 13:31 +0800, JiSheng Zhang wrote:
> >> Currently, there's no start/stop management in scsi cdrom driver to
> >> spin up/down the motor do we need to implement it?
> >
> > Say more ... like what you think it buys. The auto spin down of a CD
> > tends to be the best power control we have and it's not even clear that
> > manufacturers have implemented any other useful power states.
>
> Does it mean the behavior depends on manufacturers? Some cd will spin
> down automatically?
All CDs spin down when not reading (or burning) since the motor power is
pretty high. Most also do speed adjustments on the fly as well to try
to match platter speed and read or burn rate.
> Even so, how about during shutdown just after reading
> something from cdrom?
What's the use case? For internal CDs, shutdown removes power anyway.
James
next prev parent reply other threads:[~2011-11-01 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 5:31 Do we need to implement sr START/STOP management JiSheng Zhang
2011-11-01 5:53 ` James Bottomley
2011-11-01 6:35 ` JiSheng Zhang
2011-11-01 12:35 ` James Bottomley [this message]
2011-11-02 1:13 ` Robert Hancock
2011-11-03 6:38 ` JiSheng Zhang
2011-11-03 14:38 ` Tejun Heo
2011-11-03 15:34 ` Douglas Gilbert
2011-11-03 15:46 ` Tejun Heo
2011-11-03 17:13 ` Douglas Gilbert
2011-11-03 21:04 ` 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=1320150936.17402.10.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=jszhang3@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