From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: Do we need to implement sr START/STOP management Date: Thu, 3 Nov 2011 14:04:33 -0700 Message-ID: <20111103210433.GL4417@google.com> References: <1320126812.7701.17.camel@dabdike> <4EB0992C.5070309@gmail.com> <4EB2B468.9010001@interlog.com> <4EB2CBAC.70003@interlog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-gy0-f174.google.com ([209.85.160.174]:37979 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751480Ab1KCVMk (ORCPT ); Thu, 3 Nov 2011 17:12:40 -0400 Content-Disposition: inline In-Reply-To: <4EB2CBAC.70003@interlog.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Douglas Gilbert Cc: JiSheng Zhang , Robert Hancock , James Bottomley , linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org Hello, On Thu, Nov 03, 2011 at 01:13:16PM -0400, Douglas Gilbert wrote: > Do you mean the GET EVENT STATUS NOTIFICATION command (as there is > no CHECK MEDIA EVENT STATUS command in SCSI or ATA)? If so it is > one of the "good guys" along with the REQUEST SENSE command. And > as I said TUR is not recommended. So looking at MS usage _and_ > the standards is a useful guide. Yes, that's the one. Sorry, I always get confused about its name. IIRC, it's a relatively new command, right? Anyways, I'm not arguing standards are useless but that actual usages have to take precedence. > I agree. SCSI and ATA define idle states (with some fuzziness in > the naming) that have timers associated with them. Those > mechanisms seem to work pretty well without the intervention of > commands like START STOP UNIT. Cool, thanks. -- tejun