We infer the following information based on devkit DeviceTree, circuit diagram and website information
UPHY 1: usb3-2
UPHY 6: usb3-0
UPHY 11: usb3-3
Our USB-A 3.0 uses UPHY 11 and USB2-3, so set nvidia and usb2-companion of usb3-3 to <3>, but this Port will still recognize USB 3.0 devices as 2.0.
I’m now trying to confirm against the TRM, what are the register that can be read to confirm this?
Or let us know if our information about UPHY is wrong.
I have another module at hand to burn the Jetpack 4.6.2 version. Using our past DeviceTree, the USB can recognize the 3.0 device normally. I plan to find out the reason by looking for the register status of the two.
Regarding the upgrade of JetPack 4 to JetPack 5, you should not worry about the difference of dtsi, because we directly use the BSP Source of JetPack 5 for development.
Without changing the include of tegra194-p2888-0001-p2822-0000.dts, gradually add the original Jetpack 4 settings.
Except for OTG and some variable names that need to be modified, in fact, except for the speed problem of USB 3.0, the rest of the interfaces can work. Of course, this requires longer verification and testing.
Regarding the test results using xxd just now, nvidia, usb2-companion are consistent with the DeviceTree I set.
If you boot up the system and can see the device tree is correct. usb2-3 is enabled, set to host mode, and has vbus pin configured. usb3-3 is enabled and companioned with usb2-3. Then the device tree looks fine for a USB3 type-A port. For next, please try to disable and then enable regulator to trigger re-enumeration: Switch on and off usb ports programmatically on AGX - #5 by DaneLLL
To see if it can be enumerated as USB3 device. Your regulator may be different from Xavier developer kit so please disable/enable the one supplying to the usb2-3/usb3-3 port.