> On 20 Feb 2018, at 4:24 PM, Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> wrote: > > Hi > > On 19.02.2018 21:06, Kai-Heng Feng wrote: >> When a USB device gets plugged on ASUS PRIME B350M-A's front ports, the >> xHC stops working: >> [ 549.114587] xhci_hcd 0000:02:00.0: WARN: xHC CMD_RUN timeout >> [ 549.114608] suspend_common(): xhci_pci_suspend+0x0/0xc0 returns -110 >> [ 549.114638] xhci_hcd 0000:02:00.0: can't suspend (hcd_pci_runtime_suspend returned -110) > > Is the xhci runtime suspend something that you expected here? > I mean was the plugged device first enumerated normally, driver bound, inactive and runtime suspended > first? I guess this is how it behaves, here’s the log after a device gets plugged: [ 7535.716578] xhci_hcd 0000:02:00.0: // Setting command ring address to 0xff86c001 [ 7535.720107] xhci_hcd 0000:02:00.0: xhci_resume: starting port polling. [ 7535.720114] xhci_hcd 0000:02:00.0: xhci_hub_status_data: stopping port polling. [ 7535.720134] xhci_hcd 0000:02:00.0: xhci_suspend: stopping port polling. [ 7535.720190] xhci_hcd 0000:02:00.0: Port Status Change Event for port 8 [ 7535.720194] xhci_hcd 0000:02:00.0: resume root hub [ 7535.720201] xhci_hcd 0000:02:00.0: handle_port_status: starting port polling. [ 7535.721675] xhci_hcd 0000:02:00.0: // Setting command ring address to 0xff86c001 [ 7535.722106] xhci_hcd 0000:02:00.0: // Setting command ring address to 0xff86c001 [ 7535.725538] xhci_hcd 0000:02:00.0: xhci_resume: starting port polling. So the xHC resumes and suspends, then resume again. [ 7535.725543] xhci_hcd 0000:02:00.0: xhci_hub_status_data: stopping port polling. [ 7535.725587] xhci_hcd 0000:02:00.0: get port status, actual port 0 status = 0x2a0 [ 7535.725590] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725606] xhci_hcd 0000:02:00.0: get port status, actual port 1 status = 0x2a0 [ 7535.725608] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725616] xhci_hcd 0000:02:00.0: get port status, actual port 2 status = 0x2a0 [ 7535.725618] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725625] xhci_hcd 0000:02:00.0: get port status, actual port 3 status = 0x202e1 [ 7535.725627] xhci_hcd 0000:02:00.0: Get port status returned 0x10101 [ 7535.725632] xhci_hcd 0000:02:00.0: Port Status Change Event for port 8 [ 7535.725636] xhci_hcd 0000:02:00.0: handle_port_status: starting port polling. [ 7535.725656] xhci_hcd 0000:02:00.0: clear port connect change, actual port 3 status = 0x2e1 [ 7535.725663] xhci_hcd 0000:02:00.0: get port status, actual port 4 status = 0x2a0 [ 7535.725665] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725672] xhci_hcd 0000:02:00.0: get port status, actual port 5 status = 0x2a0 [ 7535.725674] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725680] xhci_hcd 0000:02:00.0: get port status, actual port 6 status = 0x2a0 [ 7535.725682] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725689] xhci_hcd 0000:02:00.0: get port status, actual port 7 status = 0x2a0 [ 7535.725691] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725698] xhci_hcd 0000:02:00.0: get port status, actual port 8 status = 0x2a0 [ 7535.725699] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.725706] xhci_hcd 0000:02:00.0: get port status, actual port 9 status = 0x2a0 [ 7535.725708] xhci_hcd 0000:02:00.0: Get port status returned 0x100 [ 7535.736165] xhci_hcd 0000:04:00.0: // Setting command ring address to 0xfff58001 [ 7535.740033] xhci_hcd 0000:04:00.0: xhci_resume: starting port polling. [ 7535.740040] xhci_hcd 0000:04:00.0: xhci_hub_status_data: stopping port polling. [ 7535.740047] xhci_hcd 0000:04:00.0: xhci_hub_status_data: stopping port polling. [ 7535.740133] xhci_hcd 0000:04:00.0: xhci_suspend: stopping port polling. [ 7535.740161] xhci_hcd 0000:04:00.0: // Setting command ring address to 0xfff58001 This is the “other” xHC that I mentioned in patch v1. It provides USB 3.1 capabilities to front USB port. [ 7535.776003] xhci_hcd 0000:02:00.0: xhci_hub_status_data: stopping port polling. [ 7535.832028] xhci_hcd 0000:02:00.0: get port status, actual port 3 status = 0x2e1 [ 7535.832031] xhci_hcd 0000:02:00.0: Get port status returned 0x101 [ 7535.832051] xhci_hcd 0000:02:00.0: // Ding dong! [ 7535.832150] xhci_hcd 0000:02:00.0: Slot 3 output ctx = 0xff125000 (dma) [ 7535.832153] xhci_hcd 0000:02:00.0: Slot 3 input ctx = 0xff16c000 (dma) [ 7535.832160] xhci_hcd 0000:02:00.0: Set slot id 3 dcbaa entry 000000000bd2158a to 0xff125000 [ 7535.832189] xhci_hcd 0000:02:00.0: set port reset, actual port 3 status = 0x2e1 [ 7535.835982] xhci_hcd 0000:02:00.0: xhci_hub_status_data: stopping port polling. [ 7535.892049] xhci_hcd 0000:02:00.0: Port Status Change Event for port 8 [ 7535.892056] xhci_hcd 0000:02:00.0: handle_port_status: starting port polling. [ 7535.900058] xhci_hcd 0000:02:00.0: get port status, actual port 3 status = 0x200e03 [ 7535.900061] xhci_hcd 0000:02:00.0: Get port status returned 0x100503 [ 7535.900079] xhci_hcd 0000:02:00.0: clear port reset change, actual port 3 status = 0xe03 [ 7535.959990] usb 1-4: new high-speed USB device number 4 using xhci_hcd > >> Delay before running xHC command CMD_RUN can workaround the issue. >> Use a new quirk to make the delay only targets to the affected xHC. > > Is this some known issue with this chip, or something figured out by trial and error? By trial and error. This might be a more pervasive issue, but I don’t see other bug reports though. > >> Signed-off-by: Kai-Heng Feng <kai.heng.feng@xxxxxxxxxxxxx> > > Thanks, otherwise workaround seems fine, just curious about the two details above Thank you. Kai-Heng > > -Mathias > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
