Re: Fwd: Re: [PATCH 3/4] libata: reimplement suspend/resume support using sdev->manage_start_stop

Alan Stern <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
On Tue, 20 Mar 2007, Oliver Neukum wrote:

> Hi,
> 
> I am looking at doing autosuspend support for usb storage along those lines.
> 
> 	Regards
> 		Oliver
> 
> ----------  Weitergeleitete Nachricht  ----------
> 
> Subject: Re: [PATCH 3/4] libata: reimplement suspend/resume support using sdev->manage_start_stop
> Date: Dienstag, 20. März 2007 16:29
> From: Christoph Hellwig <[email protected]>
> To: Tejun Heo <[email protected]>
> Cc: Jeff Garzik <[email protected]>, [email protected], [email protected], James Bottomley <[email protected]>, [email protected], [email protected]
> 
> On Wed, Mar 21, 2007 at 12:25:33AM +0900, Tejun Heo wrote:
> > Reimplement suspend/resume support using sdev->manage_start_stop.
> > 
> > * Device suspend/resume is now SCSI layer's responsibility and the
> >   code is simplified a lot.
> 
> Finally.  I've been telling people to do it this way forever.
> 
> Can you please also kill the braindead suspend and resume scsi_host_template
> methods now?

It's not clear what you mean.  That patch series removed some braindead 
code and added a facility whereby the SCSI disk driver would spin down a 
disk during suspend and spin up during resume.  How is this relevant to 
usb-storage?

Alan Stern


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.