On Thu, Mar 27, 2014 at 12:32:07PM -0600, David Kochendorfer wrote: > Greg, > > I apologize if you've already received a copy of this - I inadvertently > shutdown evolution in the middle of sending and it doesn't look like the > first one was sent, so ... > > Is there a document/tutorial on the USB 3.0 driver code flow in general, > especially regarding the OTG decisions process? > > I am interested in both: (1) my Samsung (android linux) defaults to a > host at 2.0 when a 3.0 OTG gadget is plugged in, posting a pop-up to > select 3.0; I'd like to have it default to 3.0 in that case. That sounds like a hardware configuration issue, can't you just select this order properly in your code? > I'm also interested in your thoughts on what it would take to make the > large file data transfer (isochronous?) rate approach the 3.0 spec > maximum, even if it means compromising other transfers. Where are you seeing slowdowns compared to "possible maximum speeds"? There are known areas that we can improve on, but a lot of them still rely on the hardwar getting things right, and I don't know if that's the case that hardware is even doing everything right just yet. And we can't "compromise other transfers", especially with isoc transfers, that's not how USB works. good luck, greg k-h -- 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
