On Friday, 28 September 2007 09:04, Oliver Neukum wrote:
quoted text
> Am Donnerstag 27 September 2007 schrieb Rafael J. Wysocki:
> > On Thursday, 27 September 2007 21:59, Oliver Neukum wrote:
> > > Am Donnerstag 27 September 2007 schrieb Rafael J. Wysocki:
> > > > On Thursday, 27 September 2007 21:37, Oliver Neukum wrote:
> > > > > Am Donnerstag 27 September 2007 schrieb Rafael J. Wysocki:
> > > > > > > But there's a problem, in that the resume methods don't take =
a message =

quoted text
> > > > > > > parameter. =A0So they wouldn't know whether they were doing a=
 runtime =

quoted text
> > > > > > > resume or a system resume.
> > > > > > =

quoted text
> > > > > > This is a general problem with the .resume() routines.
> > > > > > =

quoted text
> > > > > > If you want to use one for runtime resume, the driver needs to =
preserve
quoted text
> > > > > > information allowing it to figure out what kind of resume is go=
ing to happen.
quoted text
> > > > > =

quoted text
> > > > > How? Suppose you
> > > > > =

quoted text
> > > > > 1) runtime suspend
> > > > > 2) whole system suspend
> > > > > 3) whole system resume
> > > > > =

quoted text
> > > > > What kind of resume do you do?
> > > > =

quoted text
> > > > System resume, I'd guess.
> > > =

quoted text
> > > How do you know unless resume() tells you to do so?
> > > =

quoted text
> > > > Anyway, if we are going to stop using the freezer during suspend, t=
he locking
quoted text
> > > > requirements will probably have to unified between the runtime and =
system
quoted text
> > > > suspend.
> > > =

quoted text
> > > Even so, eg. for storage devices you should unquiesce them in case of=
 runtime
quoted text
> > > suspend, which makes no sense otherwise.
> > =

quoted text
> > OK
> > =

quoted text
> > What exactly would you like to do?
> =

quoted text
> Put the stuff into struct device and move the autosuspend code into
> driver core.

Well, I thought that it would be nicer if drivers handled autosuspend in a
transparent (from the point of view of the core) way.

Now, it seems to follow from what you're saying that this is not possible in
general, because of USB mass storage devices that need some special handlin=
g.

I'm not familiar with the USB code, so can you please tell me how the USB
autosuspend is handled at present and what exactly the problem with that is?

Greetings,
Rafael

-------------------------------------------------------------------------
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