TX2i（R32.7.4）custom board USB3.0 issue

Robotics & Edge Computing Jetson Systems Jetson TX2
,
1

While debugging the USB 3.0 functions, I noticed even after disabling all 3.0 ports, the kernel boot log still outputs the following information:

tegra-xusb 3530000.xhci: Upgrade port 0 to USB3.0
tegra-xusb 3530000.xhci: Upgrade port 1 to USB3.0

In my opinion, if the corresponding USB 3.0 port is disabled, these messages should not occur, right?
I suspect it’s hardware issues, just in case, I’d like to confirm whether it’s related to the dts configuration.
By the way, I use ODMDATA=0x7090000, already checked as follows:

ls /proc/device-tree/chosen/plugin-manager/odm-data/

android-build     disable-sdmmc-hwcq  enable-debug-console  enable-pcie-on-uphy-lane4  enable-xusb-on-uphy-lane0  enable-xusb-on-uphy-lane2  no-battery
disable-pmic-wdt  disable-tegra-wdt   enable-denver-wdt     enable-sata-on-uphy-lane5  enable-xusb-on-uphy-lane1  name                       normal-flashed

Hers is my dts, with all USB 3.0 disabled.
tegra186-quill-p3489-1000-a00-00-base.dts.txt (12.0 KB)
Hers is my boot log.
boot_log_test.txt (56.5 KB)
The reason for my debugging is that the USB interface(when enable USB2-1+USB3-0), it only recognizes USB device as USB 2.0. For example, when inserting a USB 3.0 device, the kernel outputs as follows:

[ 2396.012644] tegra-xusb 3530000.xhci: exiting ELPG
[ 2396.015637] tegra-xusb 3530000.xhci: Firmware timestamp: 2020-07-06 13:39:28 UTC, Version: 55.18 release
[ 2396.141305] tegra-xusb 3530000.xhci: exiting ELPG done
[ 2396.169313] usb usb2: usb_suspend_both: status 0
[ 2396.369246] usb 1-2: new high-speed USB device number 2 using tegra-xusb
[ 2396.393274] usb 1-2: New USB device found, idVendor=0951, idProduct=1666
[ 2396.393295] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 2396.393310] usb 1-2: Product: DataTraveler 3.0
[ 2396.393323] usb 1-2: Manufacturer: Kingston
[ 2396.393335] usb 1-2: SerialNumber: E0D55EA574ED1890E84100CB
[ 2396.394956] usb-storage 1-2:1.0: USB Mass Storage device detected
[ 2396.397313] scsi host2: usb-storage 1-2:1.0
[ 2397.430520] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 3.0 0000 PQ: 0 ANSI: 4
[ 2397.439701] sd 2:0:0:0: [sdb] 121077760 512-byte logical blocks: (62.0 GB/57.7 GiB)
[ 2397.447711] sd 2:0:0:0: [sdb] Write Protect is off
[ 2397.452547] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 2397.452773] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 2397.472847] sdb: sdb1
[ 2397.474614] sd 2:0:0:0: [sdb] Attached SCSI removable disk

3

You stills has usb3 lanes mentioned in your DT in xhci@3530000. So the log still prints.

4

Hi, I removed the usb3 from xhci@3530000 node, and replaced the rebuild dtb.
I checked the xhci@3530000 node information of the dtb via the dtc tool, as follows:

        xhci@3530000 {
                compatible = "nvidia,tegra186-xhci";
                reg = <0x0 0x3530000 0x0 0x8000 0x0 0x3538000 0x0 0x1000>;
                interrupt-parent = <0x3a>;
                iommus = <0x11 0x1b>;
                iommu_sodev_map;
                status = "okay";
                otg-controller = <0xad>;
                interrupts = <0x0 0xa3 0x4 0x0 0xa4 0x4 0x0 0xa7 0x4>;
                clocks = <0x10 0x71 0x10 0xf4 0x10 0x72 0x10 0xf2 0x10 0x261 0x10 0xf5 0x10 0x215 0x10 0x261 0x10 0x200>;
                clock-names = "xusb_host", "xusb_falcon_src", "xusb_ss", "xusb_ss_src", "xusb_hs_src", "xusb_fs_src", "pll_u_480m", "clk_m", "pll_e";
                nvidia,xusb-padctl = <0xa2>;
                extcon-cables = <0xa3 0x1>;
                extcon-cable-names = "id";
                #extcon-cells = <0x1>;
                avddio_usb-supply = <0x13>;
                avdd_pll_utmip-supply = <0x12>;
                hvdd_usb-supply = <0x12>;
                phys = <0xa1 0xae>;
                phy-names = "usb2-0", "usb2-1";
                linux,phandle = <0x1c7>;
                phandle = <0x1c7>;
        };

usb3 in xusb_padctl@3520000 still disabled, but the following log still prints.

tegra-xusb 3530000.xhci: Upgrade port 0 to USB3.0
tegra-xusb 3530000.xhci: Upgrade port 1 to USB3.0
5

I don’t think that print really matters. Does it affect something on your result?

6

Probably no impact, I want to confirm whether those prints are related to usb 3.0 works fine(software).
If not, I can just ignore them.
Previously, no matter how I configured USB 3.0 in dtb, those prints didn’t change, which made me doubt my modifications were effective.
Following is how I enable USB2-1+USB3-0(USB1_D+USB_SS0) based on the dts I provided before. If nothing goes wrong, I will further troubleshoot the hardware.

xusb_padctl@3520000 {
  ...
  pads {
  ...
    usb3 {
      lanes {
        usb3-0 {
	      nvidia,function = "xusb";
		  status = "okay";
		};
      ...
      };
    ...
    };
  ...
  ports {
  ...
     usb3-0 {
        status = "okay";
        nvidia,usb2-companion = <1>;
     };
  ...
};
7

Sorry in advance in case I took your purpose wrong.

What are you trying to do here? I guess you only want to you usb2 speed even though hardware has USB3?

8

Maybe we misunderstood each other.
Actually, I want to enable USB 3.0 so the 3.0 device can use 3.0 speed.
But, after I configured USB2-1+USB3-0(USB1_D+USB_SS0) in dts as above, the usb3.0 devices are still registered as usb2.0.
Then I noticed the print “tegra-xusb 3530000.xhci: Upgrade port 0 to USB3.0”, I thought I had disabled USB 3.0 of port 0 (usb2-0) in the dts, so this print shouldn’t appear. This makes me wonder if the dts is configured correctly.

9

Sorry for my unclear question. I should just ask my real question directly.

10

Is that a pure type A port ?

11

Yes, it is a pure and standard type-A port.
Please help me verify whether the dts is correct to enable USB2-1+USB3-0(USB1_D+USB_SS0).

12

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0225

Is this still an issue to support? Any result can be shared?