Hi, > > This is true for ISP116x. But the ISP1362 has a smarter handling for > > periodic transfers than the ISP116x. PTDs in the INTL buffer will > > automatically be rescheduled without CPU intervention (as long as they > > are NAKed by the device). Thus the SOF interrupt is not necessary for > > INT transfers. > > Yes, that is about INT transfer completion. > > But not using SOF you just ignore the intervals for the INT > endpoints, as requested by urb->interval. If the device's > INT endpoint happens to be able to respond with data within > say 1 ms, then the transfers/urb dequeuing/resubmission/urb > enqueuing occur also every ms regardless that the transfer > interval requested by the device driver was perhaps order(s) > of magnitude larger. Right? > No. You can specify the starting frame number (lower 5 bits) and the interval in the PTD and the chip will only submit the PTD when the lower bits of the current frame number match the Starting Frame bits in the PTD. This is just like OHCI does.
Lothar Wassmann ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
