On Sat, 26 Nov 2005, Franck wrote: > 2005/11/26, Olav Kongas <[EMAIL PROTECTED]>: > > I think there's nothing wrong. Processing the fifo ram > > loaded with finished transfer data does not interfere with > > the suspended bus. > > > > Suppose isp116x_bus_suspend() is called and let's consider > > the two possible cases: (a) at that moment there are > > transfers scheduled for or happening on the bus (i.e., the > > chip's fifo ram is loaded) > > It's just sound weird to suspend the host controler hardware whereas a > transfer might be not finished. But if the _suspended_ hardware can > still deal with INT, that's OK.
The isp116x_bus_suspend() does what its name says - it suspends the usb bus. This doesn't mean that the HC is not allowed to generate interrupts. For example, if configured so, the HC may generate ResumeDetected interrupt as a response to the resume signalling by devices on the suspended bus. > Though you "freeze" your system during 7ms. Why not sleeping instead > with INT enable ? OK, I'll consider reworking it. Olav ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
