Yes it is a type A usb.
Ok… I already told this in previous comment. So let me paste the document again …
Please refer to the product design guide. As below page, if you want to make a usb3.0 type A port, you also need a usb 2.0 pin coupled with this port…
Oh I get what you’re asking now. We’ve intentionally left the usb2.0 data lines out in the hardware to ensure it only connect with usb3.0
The Usb2.0 data lines are added to make it backward compatible.
But they should be coupled in software.
Again, I am not sure what you are talking about… What does that mean it is coupled in software?
The usb 3.0 type A port must have a usb2 pin. If this thing does not exist on your board design, then our software won’t support it.
I’m really asking how do I ensure the configs and drivers to support the Usb ports are correct when the usb2.0 is coupled with the usb3.0 correctly?
I saw in one of the threads that we shouldn’t use the dummy regulator “vdd-ac-bat” (0x26).
Would the node below be how to config a gpio pin for this purpose?
regulator@4 {
compatible = “regulator-fixed-sync”;
reg = <0x4>;
regulator-name = “vdd-usb0-5v”;
regulator-min-microvolt = <0x4c4b40>;
regulator-max-microvolt = <0x4c4b40>;
gpio = <0x1b 0x5c 0x0>;
gpio-open-drain;
enable-active-high;
regulator-enable-ramp-delay = <0x3b1>;
regulator-disable-ramp-delay = <0xa5a>;
linux,phandle = <0xa8>;
phandle = <0xa8>;
You should make sure you are making a correct hardware… but not just keep asking me about the software.
If the hardware is wrong, then any configuration in the software won’t resolve your problem.
Also, the software guidance is already in the adaptation guide. I already told this 3 times.
Thank you for your response WayneWWW
Make it easier to understand… everything in the device tree should match your hardware.
For example, currently you write “nvidia,usb2-companion = <0x1>;” under both your usb3-0 and usb3-1…
It means physically your 2x usb 3 ports are coupled with same usb2 pins… This is a obvious mistake…
As for you question about the gpio of the regulator… it also needs to match your hardware. If your vbus hardware design does not use a gpio to control, then I see no point to configure any gpio in device tree.