How to forse re-scan NX USB3.0 after reboot NX

Luna2020 · November 28, 2022, 6:02am

Hi NV_Team，

We have a 5G module(through USB3.0) , but ‘reboot’ can’t find usb devices. Can we force re-scan USB3.0 and how to re-scan NX USB3.0 (we don’t use usb hub on this CVB).

If we power down our CVB and re-plugin the power cable, 5G usb device works fine.
If we use ‘reboot’ in terminal on the CVB, 5G usb device is gone (lsusb can’t find any vid/pid)

After reboot 

nvidia@nx:~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
    |__ Port 3: Dev 2, If 0, Class=Wireless, Driver=, 480M
    |__ Port 3: Dev 2, If 1, Class=Wireless, Driver=, 480M
    |__ Port 3: Dev 2, If 2, Class=Vendor Specific Class, Driver=, 480M

reboot.nousb3.dmesg.log (61.5 KB)

After Power down and re-plug the power cable 

nvidia@nx:~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
    |__ Port 3: Dev 2, If 0, Class=Communications, Driver=cdc_ncm, 5000M
    |__ Port 3: Dev 2, If 1, Class=CDC Data, Driver=cdc_ncm, 5000M
    |__ Port 3: Dev 2, If 2, Class=Vendor Specific Class, Driver=option, 5000M
    |__ Port 3: Dev 2, If 3, Class=Vendor Specific Class, Driver=option, 5000M
    |__ Port 3: Dev 2, If 4, Class=Vendor Specific Class, Driver=option, 5000M
    |__ Port 3: Dev 2, If 5, Class=Vendor Specific Class, Driver=option, 5000M
    |__ Port 3: Dev 2, If 6, Class=Vendor Specific Class, Driver=option, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
    |__ Port 3: Dev 2, If 0, Class=Wireless, Driver=, 480M
    |__ Port 3: Dev 2, If 1, Class=Wireless, Driver=, 480M
    |__ Port 3: Dev 2, If 2, Class=Vendor Specific Class, Driver=, 480M

shutdownandpoweron.dmesg.log (63.8 KB)

WayneWWW · November 28, 2022, 8:34am

/sys/bus/usb/devices/1-4$ cat authorized
1

please try to reset 1/0 on your usb device node.

Luna2020 · November 28, 2022, 8:44am

Hi WayneWWW,

What do you mean "please try to reset 1/0 on your usb device node. "? we tried to set “echo 0 > authorized”, then set “echo 1 > authorized”， but still not find the usb3.0 5G module.

We don’t use any USB Hub for USB3.0 or USB2.0, why the “2-0:1.0” still get four usb2-port*

WayneWWW · November 28, 2022, 8:57am

Is this custom board or NV devkit?

Luna2020 · November 28, 2022, 9:00am

Hi WayneWWW,

Our custom board, not devkit.

WayneWWW · November 28, 2022, 9:01am

Is same usb device able to be directly detected as 3.0 device on devkit?

Luna2020 · November 28, 2022, 9:04am

Hi,

Devkit use usb hub for usb 3.0 and 2.0 devices but we don’t use any usb hub, because we only use one usb3.0 port for 5G module and usb 2.0 for host (one port).

WayneWWW · November 28, 2022, 9:07am

Hi,

Yes, I know what you are talking about but your comment didn’t give you a reason to stop telling me the result from devkit…

WayneWWW · November 28, 2022, 9:08am

You can try to control the regulator. But you need to make sure it is matching your hardware design. The regulator in use may not be same.

Luna2020 · November 28, 2022, 9:48am

Because our 5g module is BGA package not support hot-plug, so I can’t reproduce this bug on devkit.

Luna2020 · November 28, 2022, 9:52am

We tried to add regulator in dtsi, but still not work.

We have a question about this usb setting, we don’t use usb 2.0 and 3.0 hub, but why there is still usb hub log in the dmesg log ?

WayneWWW · November 28, 2022, 11:57am

I am not sure if your really understand what I tried to say. My point is if you want a method to rescan usb device, then we provided. Whether the regulator exists or works depends on your hardware design.
It is normal. There are root hubs inside tegra usb design.

linuxdev · November 28, 2022, 6:46pm

The log made me curious about something:

[    8.069102] tegra-pcie-dw 141a0000.pcie: Failed to get 3V slot regulator: -19
[    8.069111] tegra-pcie-dw 141a0000.pcie: Failed to get 12V slot regulator: -19

This may not be relevant, but what do you see in the “works” case versus the “not” working case from “lspci”? I ask because some regulator behavior might be shared between USB and PCI. Also, on a custom board, the device tree might need to be modified for regulators to behave correctly with a different electrical layout. I’m just curious if lspci also changes between working and not working cases. If it does, then the problem is following the regulator behavior.

Luna2020 · November 29, 2022, 3:26am

Hi WayneWWW,

We understood your information, now we tried re-scan and re-set vbus output, now this problem is solved.
Thanks for your support.
We got it.

system · December 21, 2022, 1:05am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.