https://bugzilla.kernel.org/show_bug.cgi?id=216822 Bug ID: 216822 Summary: Thunderbolt USB Controller (Maple Ridge) and its upstream pcie port fail to runtime resume Product: Drivers Version: 2.5 Kernel Version: kernel 6.0 and later Hardware: Intel OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: USB Assignee: drivers_usb@xxxxxxxxxxxxxxxxxxxxxx Reporter: chris.chiu@xxxxxxxxxxxxx Regression: No Created attachment 303426 --> https://bugzilla.kernel.org/attachment.cgi?id=303426&action=edit output of lspci -vt The xHCI host controller(8086:1138) of the TBT4 add-on card fail to detect any USB-C devices after boot. After forcing the runtime resume by `echo 'on' > '/sys/bus/usb/devices/usb4/power/control`, the connected usb-c device can be detected. After turn on PCI_DEBUG and DEBUG of the usbcode/xhci_hcd, there seems no problem when the usb port go into runtime suspend ``` [ 579.488151] xhci_hcd 0000:13:00.0: set port remote wake mask, actual port 4-1 status = 0xe0002a0 [ 579.488221] xhci_hcd 0000:13:00.0: set port remote wake mask, actual port 4-2 status = 0xe0002a0 [ 579.488239] hub 4-0:1.0: hub_suspend [ 579.488260] usb usb4: bus auto-suspend, wakeup 1 [ 579.488283] xhci_hcd 0000:13:00.0: xhci_hub_status_data: stopping usb4 port polling [ 579.488306] xhci_hcd 0000:13:00.0: config port 4-1 wake bits, portsc: 0xa0002a0, write: 0xa0202a0 [ 579.488316] xhci_hcd 0000:13:00.0: config port 4-2 wake bits, portsc: 0xa0002a0, write: 0xa0202a0 [ 579.488323] xhci_hcd 0000:13:00.0: config port 3-1 wake bits, portsc: 0xa0002a0, write: 0xa0202a0 [ 579.488328] xhci_hcd 0000:13:00.0: config port 3-2 wake bits, portsc: 0xa0002a0, write: 0xa0202a0 [ 579.488333] xhci_hcd 0000:13:00.0: xhci_suspend: stopping usb3 port polling. [ 579.488359] xhci_hcd 0000:13:00.0: // Setting command ring address to 0x11aa08001 [ 579.488536] xhci_hcd 0000:13:00.0: hcd_pci_runtime_suspend: 0 ``` but no messages in kernel after plug in a usb device. I expect to see the runtime resume first on the upstream port pcieport 0000:00:1d.0, and then the xhci_hcd 0000:13:00.0 but nothing. Please refer to the attached lspci output for the device information and suggest what we should do next to find out the cause. Thanks -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
