On Mon, Sep 20, 2004 at 03:39:19AM -0500, Al Borchers wrote: > The problem that Sam found is that throttle can be called in interrupts, > and io_ti throttle calls usb_control_msg to drop RTS, but that sleeps. > > However, it is simply not necessary for io_ti throttle to explicitly > drop RTS. The firmware in the TI based edgeports is capable > of handling incoming flow control. All that is needed is for the > driver to stop submitting urbs on the bulk in endpoint for the port > when throttle is called, and restart submitting urbs when unthrottle > is called. The device will drop RTS when the bulk in urbs stop, and > assert RTS when the urbs start again. > > The io_ti.c in the kernel uses this feature _and_ also explicitly controls > RTS for hardware flow control. Greg might remember why this was done--this > is the way the code was when I started working on it.
I really don't remember, sorry. Probably was the same thing that the Windows driver did originally. greg k-h ------------------------------------------------------- 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
