background: custorm carrier board, Jetpack4.5，select USB 3.0, PCIe & SATA Lane Mapping Configurations 6
question： Mouse can not be used after power on, and can be used after hot plug, the keyboard and 3.0 camera are normal, What’s wrong with the configuration of the device tree?
192.168.1.194_2021-06-07_08-49-48.log (193.3 KB)
extracted.dts (495.7 KB)
opt@opt-desktop:~$ ls -lh /proc/device-tree/chosen/plugin-manager/odm-data/
total 0
-r–r–r-- 1 root root 4 6月 7 08:46 android-build
-r–r–r-- 1 root root 4 6月 7 08:46 disable-pmic-wdt
-r–r–r-- 1 root root 4 6月 7 08:46 disable-sdmmc-hwcq
-r–r–r-- 1 root root 4 6月 7 08:46 disable-tegra-wdt
-r–r–r-- 1 root root 4 6月 7 08:46 enable-debug-console
-r–r–r-- 1 root root 4 6月 7 08:46 enable-denver-wdt
-r–r–r-- 1 root root 4 6月 7 08:46 enable-pcie-on-uphy-lane2
-r–r–r-- 1 root root 4 6月 7 08:46 enable-pcie-on-uphy-lane4
-r–r–r-- 1 root root 4 6月 7 08:46 enable-sata-on-uphy-lane5
-r–r–r-- 1 root root 4 6月 7 08:46 enable-xusb-on-uphy-lane0
-r–r–r-- 1 root root 4 6月 7 08:46 enable-xusb-on-uphy-lane1
-r–r–r-- 1 root root 9 6月 7 08:46 name
-r–r–r-- 1 root root 4 6月 7 08:46 no-battery
-r–r–r-- 1 root root 4 6月 7 08:46 normal-flashed
opt@opt-desktop:~$
I am unable to say what is going on, but some details I find interesting might be worth pointing out…
USB3, when it sees a slower device, has to reroute that to a slower controller. USB2 controllers have tended to be able to handle slower devices themselves, e.g., if a mouse is USB1.1, then USB3 controllers would route this to another legacy controller, while a USB2 controller would do the job itself (that controller would handle a USB1 or 1.1 device). Mice are typically either USB1 or USB1.1, and if a USB3 controller has not yet been set up with the USB2 information, then there is no chance the device will function. On the other hand, am I correct that a keyboard functions during boot without replug?
You might want to provide an “lsusb” and “lsusb -t” output (A) while the mouse is failing, and the same commands after the mouse replug.
You might also monitor “dmesg --follow”, and post the log output as you unplug the non-functioning mouse and replug to gain function.
If you are using the GUI, then you’ll also want to post the “/var/log/Xorg.0.log” from after the replug of the mouse.
Also, you have lots of filesystem errors, e.g.:
[ 2.174619] EXT4-fs (mmcblk0p1): 29 orphan inodes deleted
[ 2.174621] EXT4-fs (mmcblk0p1): recovery complete
There isn’t much one can say about what part of the filesystem is now missing, but I would be careful in testing and try to shut down in a normal manner and not damage the filesystem. Often those missing nodes won’t have anything to do with the problem, but this can also cause problems which get in the way of debugging.
Are you trying to say keyboard is working fine on the same port while the mouse cannot?
While the mouse is failing
opt@opt-desktop:~$ lsusb
Bus 002 Device 003: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 03f0:2a4a Hewlett-Packard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
opt@opt-desktop:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/3p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
While the mouse replusg
opt@opt-desktop:~$ lsusb
Bus 002 Device 003: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 03f0:094a Hewlett-Packard Optical Mouse [672662-001]
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 03f0:2a4a Hewlett-Packard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
opt@opt-desktop:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/3p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
[ 307.423383] usb 1-2: reset high-speed USB device number 3 using tegra-xusb
[ 307.759184] usb 1-2.3: new low-speed USB device number 8 using tegra-xusb
[ 307.783410] usb 1-2.3: New USB device found, idVendor=03f0, idProduct=094a
[ 307.783418] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 307.783423] usb 1-2.3: Product: HP USB Optical Mouse
[ 307.783427] usb 1-2.3: Manufacturer: PixArt
[ 307.785998] input: PixArt HP USB Optical Mouse as /devices/3530000.xhci/usb1/1-2/1-2.3/1-2.3:1.0/0003:03F0:094A.0003/input/input5
[ 307.786227] hid-generic 0003:03F0:094A.0003: input,hidraw2: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-3530000.xhci-2.3/input0
[ 308.643619] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[ 309.504187] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[ 309.511371] usb 1-2-port4: attempt power cycle
[ 310.680004] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[ 311.540101] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[ 311.547218] usb 1-2-port4: unable to enumerate USB device
192.168.1.194_2021-06-08_15-07-27.log (193.4 KB)
Can you reply “yes” or “no” to my question?
Are you trying to say keyboard is working fine on the same port while the mouse cannot?
If mouse cannot work but keyboard can always work fine on the same port, then I don’t think it is related to device tree or ODM data confiugraiton.
Have you tried other kind of usb mouse?
I’m sorry. keyboard also can’t work
What else can work here? USB SS devices?
Which port has this issue? Both ports or only one port has this issue?
Could you share board schematic? We know nothing about your board.
Why does two usb 3 ports are sharing the same usb2 companion?
usb3-0 {
mode = “host”;
status = “okay”;
nvidia,usb2-companion = <0x1>;
};
usb3-1 {
mode = “host”;
status = “okay”;
nvidia,usb2-companion = <0x1>;
};
1 Like
thank you very much, i have change nvidia,usb2-companion , now mouse can use.
1 Like