[PATCH V6 00/12] Tegra xHCI support
flat view
From: Andrew Bresticker <hidden>
Date: 2015-02-25 17:27:40
Also in:
linux-devicetree, linux-tegra, lkml
Hi Thierry,
Sorry for taking so awfully long to look at this. I've spent some time looking at various pieces of documentation and I concluded that representing the port assignment as muxing options doesn't seem right after all. Instead I've come up with an alternate proposal (attached). Could you take a look and see if that sounds reasonable to you?
Thanks for taking a look at this. I've been meaning to pick this series back up, but haven't had quite enough bandwidth lately. This all looks good to me, just one comment below:
quoted hunk ↗ jump to hunk
+PHY nodes: +---------- + +An optional child node named "phys" can contain nodes describing additional +properties of each PHY. Only USB3 and UTMI PHYs can be complemented in this +way, in which case the name of each node must match one of the following: + + usb3-0, usb3-1, utmi-0, utmi-1, utmi-2 + +Required properties for USB3 PHYs: +- nvidia,lanes: specifies the name of the lane that this USB3 PHY uses +- nvidia,port: specifies the number of the USB2 port that is used for this + USB3 PHY + +Optional properties for UTMI PHYs: +- vbus-supply: regulator providing the VBUS voltage for the UTMI pad
What about the HSIC PHYs? Shouldn't they be represented as PHY nodes as well?