From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0925BC4360C for ; Fri, 27 Sep 2019 09:02:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CD0B52146E for ; Fri, 27 Sep 2019 09:02:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=endlessm-com.20150623.gappssmtp.com header.i=@endlessm-com.20150623.gappssmtp.com header.b="eA4FJinr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726061AbfI0JCI (ORCPT ); Fri, 27 Sep 2019 05:02:08 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:41978 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725890AbfI0JCI (ORCPT ); Fri, 27 Sep 2019 05:02:08 -0400 Received: by mail-pg1-f195.google.com with SMTP id s1so3122233pgv.8 for ; Fri, 27 Sep 2019 02:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=endlessm-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=5yncGVIGcBUU0Qx4YQav5kcxHlI5UC4QRgpeQu8kNhA=; b=eA4FJinrODv+48zRVhxibGLLHEOxlVFW/vZ/iQUCgt9D7z+xhJ0mKf9Y/yweQGb6Gi 9b3/F5nVfRNRhGrk7XW6ZpOQQfXbrKkW9MzUWT4mWbywdtMSW1cf5e0yvTKJ4RLE/NSe r6PySpwAEP+1c00R3YQWlElA25Ffak4X+Gg7oFDgxH1OplXQ1fAHOmeEOfQNJ5uqk4kU 733VWHlCdU2j8YlEVSof1mqvANu4eqFMoFakCIkXALHk5OAL2FK+KMh12UbJAtLPfgJJ i/vWtAmPC/GWP4hnG/JsWFYgsczScO3V6kFbUVmNdWYRs1cv5lsToJ6yiirjH1bgXPlJ qRqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=5yncGVIGcBUU0Qx4YQav5kcxHlI5UC4QRgpeQu8kNhA=; b=r/i4g8oi1CJq0OtKASXiKel0Kfduv9MEuOExd5Re8MK80MvKLJNzqp3PPg8to/PQeS NoNXIFWJGcyNwD6Ovg10CnuOJWZ4+2sI5ITTYCMRS2lIDlhuyVTsZFVjtWRnu8BwEj/b IPI4nhAR56gfM8pQkDh8Cq1spIRcYXj3S3qarWsg+4Rq64Rj0L2N9xeoIvj4Ey26AZPA wNCkU/UITnSXmaGYVrYhvGwEwzExYm27waSYA28azPABSNDxp20pQroZFU895riRg0qH nbe4vSbWBc794aD87H/ebakoZDRaYP3TOBNhkQSqyRMSrTAL+rgVSqOju18uI4xf1gx/ rQ6A== X-Gm-Message-State: APjAAAXwcgBfdFsx7/L1BWNsYY+F2ii9i77lrzEbUhtwoiUNR5LWWGHT w+jm6QGRsg/vJpW0lUnEsQaFC9yAHv4= X-Google-Smtp-Source: APXvYqykU4OEAfFMMqT32a+dnqKs0fu/V96QsUOui8jICh8HwHMQ95/vS+ZuCIIq2kdfNGoIPguIfg== X-Received: by 2002:aa7:874c:: with SMTP id g12mr2828560pfo.170.1569574927095; Fri, 27 Sep 2019 02:02:07 -0700 (PDT) Received: from limbo.local (123-204-46-122.static.seed.net.tw. [123.204.46.122]) by smtp.gmail.com with ESMTPSA id f62sm2178673pfg.74.2019.09.27.02.02.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 27 Sep 2019 02:02:06 -0700 (PDT) From: Daniel Drake To: rafael@kernel.org, bhelgaas@google.com Cc: mathias.nyman@linux.intel.com, linux@endlessm.com, linux-pm@vger.kernel.org, linux-pci@vger.kernel.org Subject: [PATCH] PCI: also apply D3 delay when leaving D3cold Date: Fri, 27 Sep 2019 17:02:02 +0800 Message-Id: <20190927090202.1468-1-drake@endlessm.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org This delay is needed to fix resume from s2idle of the XHCI controller on AMD Ryzen SoCs, where a 20ms delay is required (this will be quirked in a followup patch), to avoid this failure: xhci_hcd 0000:03:00.4: WARN: xHC restore state timeout xhci_hcd 0000:03:00.4: PCI post-resume error -110! The D3 delay is already being performed in a runtime resume from D3cold, through the following sequence of events: pci_pm_runtime_resume -> pci_restore_standard_config -> pci_set_power_state(D0) -> __pci_start_power_transition -> pci_platform_power_transition -> pci_update_current_state At this point, the device has been set to D0 at the platform level, so pci_update_current_state() reads pmcsr and updates dev->current_state to D3hot. Now when we reach pci_raw_set_power_state() the D3 delay will be applied. However, the D3cold resume from s2idle path is somewhat different, and we arrive at the same function without hitting pci_update_current_state() along the way: pci_pm_resume_noirq -> pci_pm_default_resume_early -> pci_power_up -> pci_raw_set_power_state As dev->current_state is D3cold, the D3 delay is skipped and the XHCI controllers fail to be powered up. Apply the D3 delay in the s2idle resume case too, in order to fix USB functionality after resume. Link: http://lkml.kernel.org/r/CAD8Lp47Vh69gQjROYG69=waJgL7hs1PwnLonL9+27S_TcRhixA@mail.gmail.com Signed-off-by: Daniel Drake --- drivers/pci/pci.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c index e7982af9a5d8..ab15fa5eda2c 100644 --- a/drivers/pci/pci.c +++ b/drivers/pci/pci.c @@ -883,7 +883,8 @@ static int pci_raw_set_power_state(struct pci_dev *dev, pci_power_t state) * Mandatory power management transition delays; see PCI PM 1.1 * 5.6.1 table 18 */ - if (state == PCI_D3hot || dev->current_state == PCI_D3hot) + if (state == PCI_D3hot || dev->current_state == PCI_D3hot + || dev->current_state == PCI_D3cold) pci_dev_d3_sleep(dev); else if (state == PCI_D2 || dev->current_state == PCI_D2) udelay(PCI_PM_D2_DELAY); -- 2.20.1