Hi, I'm contemplating removing the option to provide clock() and reset() functions for isp116x-hcd in platform code. However, these functions may be necessary for power saving, which hasn't been a priority for me as none of my platforms is battery powered.
clock() - if implemented by user, this function is currently called only in 2 cases: to start external clock when the driver is loaded and to stop external clock when the driver is unloaded. Has anyone implemented this function? reset() - if implemented by user, hardware reset is done to the chip instead of software reset. It seems to have two advantages over the SW reset: 1. HW reset is more thorogh. 2. On driver unloading, the chip is left in reset state; this is not possible with the SW reset, because chip comes automatically out of it. I say "it seems" because, for 1, I have been using SW reset recently on all my platforms and it seems to work well. For 2, though there is a power saving win when comparing the chip in reset and in suspended states, I don't have good means to measure this difference. Also, I'm not sure that many people would unload the driver during operation to conserve power. Would anyone recommend any of these two functions to stay? Olav ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
