On Thursday 06 July 2006 2:37 am, Ajay Jain wrote: > Hi, > I am writing a usb function driver for our own usb h/w. I am not very > clear on what is to be done when I receive a reset, suspend & resume.
There are gadget driver upcalls for suspend() and resume(), though there can be chip-specific details for the controller driver. Reset handling is a very basic part of enumeration; read the USB 2.0 spec to see how resets are used, and your chip docs to see which parts of the controller reset you need to handle in software. > What is expected from my driver/device when I detect a reset given by > windows host, Same thing as from _any_ host. Read the above-mentioned docs. > similarly what should be my behavior on suspend. And > what about resume. Can somebody explain all three and the device's > behavior on each. Gadget drivers for self-powered devices can safely ignore suspend and resume calls, unless they want to do things like re-enable manual controls or explicitly stop battery charging during suspend. - Dave Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
