USB 3.0 driver code flow for OTG gadget/host decision process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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.

I'm somewhat familiar with the 3.0 spec, but not the driver. Any
pointers gratefully accepted. 

David Kochendorfer
(kotchkotch -  linux.com)
(struggling with 3.0 OTG)

--
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




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux