> http://marc.theaimsgroup.com/?l=linux-kernel&m=102320879912115&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=102320879912113&w=2
> http://marc.theaimsgroup.com/?l=linux-kernel&m=102320879912119&w=2
By the way, this suggests that USB devices should have two new
optional methods in struct usb_driver:
int (*suspend) (struct usb_device *dev, u32 state, u32 level);
int (*resume) (struct usb_device *dev, u32 level);
Currently calls of those names are there, commented out (no infrastructure),
and with slightly different syntax (state/level stuff unresolved).
Seems to me that upcoming USB patches ought to
(a) add those two calls
(b) add usbcore glue to turn struct device suspend/resume
calls into ones made on usb device drivers
(c) teach at least the "hub" driver what to do there ... like
for starters, suspend should disconnect devices when the
power rules mean they won't be suspending.
I suspect an initial patch would likely skip (c).
Eventually the hub suspend/resume code would enable remote
wakeup (of course, only on root hubs that support it :) in
configurations that can support it. That'd seem to be an
interesting project for someone who wants to pick up some
new USB development.
- Dave
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
