public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Greg KH <gregkh@suse.de>
Cc: Oliver Neukum <oneukum@suse.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [1/4] 2.6.23-rc6: known regressions
Date: Thu, 13 Sep 2007 09:50:21 -0500	[thread overview]
Message-ID: <1189695021.4082.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20070913144139.GD3309@suse.de>

On Thu, 2007-09-13 at 07:41 -0700, Greg KH wrote:
> On Thu, Sep 13, 2007 at 10:19:48AM -0400, Alan Stern wrote:
> > On Thu, 13 Sep 2007, Greg KH wrote:
> > 
> > > Ok, after conferring with Oliver this morning, I think the best solution
> > > here is to both revert the usb-storage suspend patch as it has some
> > > basic problems that can cause data loss, _and_ add the change to the
> > > kernel that by default disables autosuspend on all USB devices except
> > > hubs.
> > 
> > Are you referring to the disk spin-down issue?  As far as I know, 
> > that's the only troublesome aspect of usb-storage autosuspend (apart 
> > from the fact that so many devices don't seem to support it very well, 
> > if at all).
> > 
> > Solving the spin-down problem will require coordination with the SCSI 
> > developers.  Basically, the SCSI core has to notify the HBA driver 
> > whenever the bus has been idle sufficiently long and all its devices 
> > are ready to be suspended.  In particular, all disk heads should be 
> > parked and drives spun down, if they need to be.
> 
> I am not sure.  I will defer to Oliver for the knowledge of the details,
> it was early in the morning and I can't remember them all exactly :)
> 
> (although it might be a few days for him to respond, he's here at a
> conference without a laptop, so his lag time might be a bit longer than
> normal...)

I'll wait, certainly ... enjoy the Czech backwoods.

One thing I would say though is that if there's special action we have
to take after autosuspend, it should probably be built into the
framework Kristen is developing for ACHI link power management (your USB
autosuspend is effectively a simple type of link power management as
well).

James



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

      reply	other threads:[~2007-09-13 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070913093651.GA5077@suse.de>
2007-09-13 14:19 ` [1/4] 2.6.23-rc6: known regressions Alan Stern
2007-09-13 14:41   ` Greg KH
2007-09-13 14:50     ` James Bottomley [this message]

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=1189695021.4082.10.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=gregkh@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=oneukum@suse.de \
    --cc=stern@rowland.harvard.edu \
    /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