On Thu, May 02, 2013 at 04:01:32PM -0400, Alan Stern wrote: > Sarah: > > xhci_queue_isoc_tx_prepare() has a comment saying "Always assume > URB_ISO_ASAP set". I'd like to see about fixing this, but I don't know > where to look. It doesn't seem as though any significant computations > are done for the starting frame; the value always gets set to the > current (micro)frame number. In particular, the driver doesn't use > HCS_IST. > > Does the hardware expose the scheduling information for isochronous > endpoints? I couldn't find any mention of this in the xHCI spec. That's a big can of worms. I have a larger plan to fix some isochronous ring performance issues, and I'd like to implement this change along with that. Can you wait for that change to go in? AFAIK no in-kernel drivers don't set URB_ISO_ASAP, so I didn't think this was an urgent change. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
