On Thu, Oct 27, 2011 at 02:32:47PM +0200, Oliver Neukum wrote:
> Hi,
>
> I am seeing S3 hanging with a specific chip type (100% reproducible)
> I get the following message:
>
> xhci_hcd 0000:27:00.0: WARN: xHC CMD_CSS timeout
> suspend_common(): xhci_pci_suspend+0x0/0x40 [xhci_hcd] returns -110
> pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -110
> pm_op(): pci_pm_suspend+0x0/0x130 returns -110
> PM: Device 0000:27:00.0 failed to suspend async: error -110
>
> The device is 104c:8241
Hi Oliver,
The CMD_CSS timeout means that the xHCI host controller failed to save
state for suspend within 1000 ms. The host controller shouldn't be
suspended if it can't save state. Perhaps you can increase the delay in
drivers/usb/host/xhci.c xhci_suspend():
/* step 4: set CSS flag */
command = xhci_readl(xhci, &xhci->op_regs->command);
command |= CMD_CSS;
xhci_writel(xhci, command, &xhci->op_regs->command);
if (handshake(xhci, &xhci->op_regs->status, STS_SAVE, 0, 10*100)) {
xhci_warn(xhci, "WARN: xHC CMD_CSS timeout\n");
spin_unlock_irq(&xhci->lock);
return -ETIMEDOUT;
}
Change 10*100 to, say, 5000. If it works, let me know, and we'll add a
quirk for that chipset. If it's a prototype, you might want to contact
a TI rep and see if the host can actually handle xHCI suspend.
Sarah Sharp
--
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
