On Thu, Aug 21, 2014 at 6:34 AM, Tomeu Vizoso <tomeu@xxxxxxxxxxxxxxx> wrote: > On 18 August 2014 19:08, Andrew Bresticker <abrestic@xxxxxxxxxxxx> wrote: >> >> Tested on Venice2, Jetson TK1, and Big with a variety of USB2.0 and >> USB3.0 memory sticks and ethernet dongles using controller firmware from >> the ChromiumOS tree [2]. > > Hi Andrew, > > do you have any information regarding the port assignments for the > Blaze board? Would like to test this there. Sure: - USB3 port 0 (using PCIe lane 0) and UTMI port 0 are connected to the USB A connector on the left side, - UTMI port 1 is connected to an internal hub, which is in turn connected to the camera, the LTE modem (if present), and one of the USB A connectors on the right side, and - UTMI port 2 is connected to the other USB A connector on the right side. The mapping of ports on the right side varies by SKU (i.e. the one on the internal hub may be the front or rear USB A port). The USB3 device tree bits for Venice2 should work just fine for Blaze; the only real difference is that USB3 port 1/PCIe lane 1 are unused. Also, because of the board design on Blaze, the fused HS_CURR_LEVEL values need to be adjusted before being programmed into USB2_OTG_PAD*_CTL0. This only affects UTMI ports 0 and 2, so ports connected to the internal hub should still work. I'll add a pinconfig property to address this in the likely event I need to re-spin this series. Or, if you like, I can send a follow-on patch to this set to add the property. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
