From: Douglas Gilbert <dgilbert@interlog.com>
To: Tejun Heo <tj@kernel.org>
Cc: JiSheng Zhang <jszhang3@gmail.com>,
Robert Hancock <hancockrwd@gmail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Do we need to implement sr START/STOP management
Date: Thu, 03 Nov 2011 11:34:00 -0400 [thread overview]
Message-ID: <4EB2B468.9010001@interlog.com> (raw)
In-Reply-To: <CAOS58YOVC-dknjK50LHTjMOFFdM3KNyWzRPs8Ru2YRau4QQBWw@mail.gmail.com>
On 11-11-03 10:38 AM, Tejun Heo wrote:
> Hello,
>
> On Wed, Nov 2, 2011 at 11:38 PM, JiSheng Zhang<jszhang3@gmail.com> wrote:
>> I have talked with one cdrom firmware engineer, cdrom also need to put
>> the head at
>> "park" position. So we also need to let cdrom spin down when poweroff,
>> suspend etc for lifespan?
>
> I'm pretty skeptical that's necessary, and here's what we should do
> regarding ATAPI devices.
>
> Do what Windows does.
>
> In many cases, manufacturers are verifying only against windows and
> deviation from windows behavior usually means trouble regardless of
> the standard. Even sending TURs repeatedly can send devices into
> complete lockup. So, I don't really care what the standard says. If
That's a pretty poor attitude. I suspect Microsoft care. If so they
would be transitioning away from TEST UNIT READY to REQUEST SENSE
to monitor power conditions and the progress indication.
In the latest MMC draft (mmc6r02g.pdf 20091211), monitoring based on
the TEST UNIT READY command is typically followed by this rider:
"This behavior is not recommended"!
Doug Gilbert
next prev parent reply other threads:[~2011-11-03 15:34 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
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 [this message]
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=4EB2B468.9010001@interlog.com \
--to=dgilbert@interlog.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hancockrwd@gmail.com \
--cc=jszhang3@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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).