Hi!
> > > Exactly. �Furthermore, the suspend call is a logical place to specify
> > > whether wakeup should be enabled. �Also note that once a device is
> > > suspended, it may not be possible to change whether wakeup is enabled or
> > > disabled without first resuming the device.
> >
> > Specifying wakeup_enabled at suspend() time will mean one more
> > parameter to suspend() :-(. We already have enable_wake() function, I
> > do not think we want to change API.
>
> USB cannot enable remote wakeup on a suspended device. It must be done
> before.
Well, enable_wake() is currently only defined on PCI. Driver model
does not seem to solve wakeups for now.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
