JetPack4.2.1 After Suspend, usb keyboard can't work on Jetson Tx2

1、Flash Jetson Tx2 using new JetPack4.2.1
2、Plug Usb-Hub on J19, connect USB Keyboard && Mouse
3、Login the system (usb keyboard && mouse work normally after system up)
4、Suspend the system manually
5、Wake-up the system, Press Enter on the keyboard.
6、this time, keyboard doesn’t work, only mouse work.

I do some test, Plug-out the mouse && keyboard, And Plug-in keyboard first, then keyboard can work correctly, but if I Plug-in Mouse First, keyboard can’t work. But dmesg can detect the keyboard plug-in, following is the msg output:

plug-in Mouse
root@nvidia-desktop:~# dmesg -c
[ 1216.833122] tegra-xusb 3530000.xhci: exiting ELPG
[ 1216.837334] tegra-xusb 3530000.xhci: Firmware timestamp: 2018-12-26 10:30:04 UTC, Version: 55.12 release
[ 1216.838747] tegra-xusb 3530000.xhci: exiting ELPG done
[ 1217.184568] usb 1-2.3: new low-speed USB device number 7 using tegra-xusb
[ 1217.210416] usb 1-2.3: New USB device found, idVendor=093a, idProduct=2510
[ 1217.210452] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1217.210470] usb 1-2.3: Product: USB Optical Mouse
[ 1217.210486] usb 1-2.3: Manufacturer: PixArt
[ 1217.220086] input: PixArt USB Optical Mouse as /devices/3530000.xhci/usb1/1-2/1-2.3/1-2.3:1.0/0003:093A:2510.0008/input/input10
[ 1217.220326] hid-generic 0003:093A:2510.0008: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-3530000.xhci-2.3/input0
root@nvidia-desktop:~# dmesg -c
root@nvidia-desktop:~# dmesg -c

Plug-in keyboard
root@nvidia-desktop:~# dmesg -c
[ 1226.276570] usb 1-2.1: new low-speed USB device number 8 using tegra-xusb
[ 1226.304245] usb 1-2.1: New USB device found, idVendor=1c4f, idProduct=0026
[ 1226.304289] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1226.304307] usb 1-2.1: Product: USB Keyboard
[ 1226.304322] usb 1-2.1: Manufacturer: SIGMACHIP
[ 1226.311617] input: SIGMACHIP USB Keyboard as /devices/3530000.xhci/usb1/1-2/1-2.1/1-2.1:1.0/0003:1C4F:0026.0009/input/input11
[ 1226.373214] hid-generic 0003:1C4F:0026.0009: input,hidraw1: USB HID v1.10 Keyboard [SIGMACHIP USB Keyboard] on usb-3530000.xhci-2.1/input0
[ 1226.377884] input: SIGMACHIP USB Keyboard as /devices/3530000.xhci/usb1/1-2/1-2.1/1-2.1:1.1/0003:1C4F:0026.000A/input/input12
[ 1226.439288] hid-generic 0003:1C4F:0026.000A: input,hidraw2: USB HID v1.10 Device [SIGMACHIP USB Keyboard] on usb-3530000.xhci-2.1/input1
root@nvidia-desktop:~# dmesg -c

Did someone met the same issue, hope to give me a favor. thanks

It seems like a question caused by HID_QUIRK_NO_INIT_REPORTS. I found the article:
https://patchwork.kernel.org/patch/9498779/. Though the patch didn’t work, but I think it get the point.

drivers/hid/hid-ids.h
#define USB_VENDOR_ID_SIGMA_MICRO	0x1c4f
#define USB_DEVICE_ID_SIGMA_MICRO_KEYBOARD	0x0002

drivers/hid/usbhid/hid-quirks.c
{ USB_VENDOR_ID_SIGMA_MICRO, USB_DEVICE_ID_SIGMA_MICRO_KEYBOARD, HID_QUIRK_NO_INIT_REPORTS },

Hi szrjustdoit,

We have known issue about SC7 system suspend/resume may have intermittent resume failures in r32.2 release.
Sorry for inconvenience.

You can check from L4T release note:
https://developer.nvidia.com/embedded/dlc/Tegra_Linux_Driver_Package_Release_Notes_R32.2.0_GA.pdf

Hi carolyuu,

Thank you, Hope to resolve it in the next release.