On Tue, Nov 19, 2019 at 06:28:36PM -0600, Bjorn Helgaas wrote:
> On Mon, Oct 14, 2019 at 02:13:55PM +0800, Daniel Drake wrote:
> > On Asus laptops with AMD Ryzen7 3700U and AMD Ryzen5 3500U,
>
> Can you include specific models here in case we revisit this or find a
> generic solution that needs to be tested to make sure we don't regress
> these platforms?
>
> Maybe a bugzilla with complete "lspci -vvnn" and dmesg logs?
>
> > the XHCI controller fails to resume from runtime suspend or s2idle,
> > and USB becomes unusable from that point.
> >
> > xhci_hcd 0000:03:00.4: Refused to change power state, currently in D3
> > xhci_hcd 0000:03:00.4: enabling device (0000 -> 0002)
> > xhci_hcd 0000:03:00.4: WARN: xHC restore state timeout
> > xhci_hcd 0000:03:00.4: PCI post-resume error -110!
> > xhci_hcd 0000:03:00.4: HC died; cleaning up
> >
> > The D3-to-D0 transition is successful if the D3 delay is increased
> > to 20ms. Add an appropriate quirk for the affected hardware.
>
> IIUC, we're doing a D3cold-to-D0 transition in this path:
>
> pci_pm_default_resume_early
> pci_power_up
> platform_pci_set_power_state(PCI_D0) # turn on via ACPI
> pci_raw_set_power_state(PCI_D0)
> pci_read_config_word(dev, dev->pm_cap + PCI_PM_CTRL, &pmcsr)
> # pmcsr says device is in D3hot
> pci_write_config_word(dev, dev->pm_cap + PCI_PM_CTRL, pmcsr)
> # sets to D0
> pci_dev_d3_sleep # <-- need more time here
>
> I would sort of expect that ACPI would be putting the device in D0,
> not leaving it in D3hot, but maybe that's just my ignorance.
I definitely was not understanding this correctly. There is no path
for a D3cold -> D3hot transition. Per spec (PCIe r5.0, sec 5.8), the
only legal exit from D3cold is to D0uninitialized.
I know you tried a debug patch to call pci_dev_wait(), and it didn't
work, but I'm not sure exactly where it was called. I have these
patches on my pci/pm branch for v5.5:
bae26849372b ("PCI/PM: Move pci_dev_wait() definition earlier")
395f121e6199 ("PCI/PM: Wait for device to become ready after power-on")
The latter adds the wait just before we call
pci_raw_set_power_state(). If the device is responding with CRS
status, that should be the point where we'd see it. If you have a
chance to try it, I'd be interested in the results. Here's the
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?h=pci/pm&id=395f121e61994bc135bb669eb35325d5457d669d
