Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp1163683ybm; Tue, 21 May 2019 09:33:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqzYNHUeLjvDC5HQ3mvXTYpcjlMy0FyXAMm/Pon4Yj0i9PeKYCyPg6E5rU70+HXYJrIkvQFR X-Received: by 2002:a63:5c1c:: with SMTP id q28mr82609228pgb.45.1558456396463; Tue, 21 May 2019 09:33:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558456396; cv=none; d=google.com; s=arc-20160816; b=wpiL1GizTk6B5rM2egFZzhWcBYweQ7B5C71zFNz/iYzRw9yQiJjyAv75XsuliEz1fH uuHlT049ICC1kYeZmUgCQpied1mV9lebJvNzHiVjEGh6inHk9zB5lJLNGvAtNj9TLl77 +ZWMiDr6u5B4CYePNnU4clVpOnS33N/He4DiyqA+OMHof1GIy2mopfIlGVlGbuPnqUGC +Ca4d/drrxEkYGRjIMblDFSalGSbrpxOUc7FFbHHRSJ1Gw/7vatf75rTeQKiqtjV1Ok2 dkUnc/wVFobU1JEi7izwsMdKcLW6vM7rA+2mnBp6rwZg1ozzrUJRu1LR90BhCr6/PIoF 5P9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=5GubQyxSzjSSqYy3Nt7zfwPM5whU+1py7Fnuf4ddTNg=; b=powaOwId27XY+jBIIzHRGGKN4JhKsugfI6n+VpVLCQeZvv6f6ff9dKSr0Qax54CYvU jLx/Vxd5m/RvkErkymtNERfwrbVQfz3h/BJFrMA2RWOfWisdxArIg5Q7p+K4NYp1mnsU AAgl1LQshbNAjP3EY+wkOn4WhaXfLnLhVX/vmjInBs7Tx+qsuzbmAAQQbzzok9mWBIw/ Q/C4J0EJzWGFYa3BHwhEXqdhF7diwoS+5t1z5z9J3nzKpIIU9xPNHEwyuJMlt3ekfhhn Yt3I+NnMcUpwao1TT5xeoLsbWMVKU+R87Ifet6tkc3i7LDCNk4WAK2vlIdnK5CLQ5Giz NgXw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 129si24314764pfb.270.2019.05.21.09.33.00; Tue, 21 May 2019 09:33:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729057AbfEUQbN (ORCPT + 99 others); Tue, 21 May 2019 12:31:13 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:47383 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728005AbfEUQbM (ORCPT ); Tue, 21 May 2019 12:31:12 -0400 Received: from 61-220-137-37.hinet-ip.hinet.net ([61.220.137.37] helo=localhost) by youngberry.canonical.com with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1hT7fR-00027I-1U; Tue, 21 May 2019 16:31:09 +0000 From: Kai-Heng Feng To: bhelgaas@google.com, rafael.j.wysocki@intel.com Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Kai-Heng Feng Subject: [PATCH] PCI / PM: Don't runtime suspend when device only supports wakeup from D0 Date: Wed, 22 May 2019 00:31:04 +0800 Message-Id: <20190521163104.15759-1-kai.heng.feng@canonical.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There's an xHC device that doesn't wake when a USB device gets plugged to its USB port. The driver's own runtime suspend callback was called, PME signaling was enabled, but it stays at PCI D0. A PCI device can be runtime suspended to D0 when it supports D0 PME and its _S0W reports D0. Theoratically this should work, but as [1] specifies, D0 doesn't have wakeup capability. To avoid this problematic situation, we should avoid runtime suspend if D0 is the only state that can wake up the device. [1] https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/device-working-state-d0 Signed-off-by: Kai-Heng Feng --- drivers/pci/pci-driver.c | 5 +++++ drivers/pci/pci.c | 2 +- include/linux/pci.h | 3 +++ 3 files changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c index cae630fe6387..15a6310c5d7b 100644 --- a/drivers/pci/pci-driver.c +++ b/drivers/pci/pci-driver.c @@ -1251,6 +1251,11 @@ static int pci_pm_runtime_suspend(struct device *dev) return 0; } + if (pci_target_state(pci_dev, device_can_wakeup(dev)) == PCI_D0) { + dev_dbg(dev, "D0 doesn't have wakeup capability\n"); + return -EBUSY; + } + pci_dev->state_saved = false; if (pm && pm->runtime_suspend) { error = pm->runtime_suspend(dev); diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c index 8abc843b1615..ceee6efbbcfe 100644 --- a/drivers/pci/pci.c +++ b/drivers/pci/pci.c @@ -2294,7 +2294,7 @@ EXPORT_SYMBOL(pci_wake_from_d3); * If the platform can't manage @dev, return the deepest state from which it * can generate wake events, based on any available PME info. */ -static pci_power_t pci_target_state(struct pci_dev *dev, bool wakeup) +pci_power_t pci_target_state(struct pci_dev *dev, bool wakeup) { pci_power_t target_state = PCI_D3hot; diff --git a/include/linux/pci.h b/include/linux/pci.h index 4a5a84d7bdd4..91e8dc4d04aa 100644 --- a/include/linux/pci.h +++ b/include/linux/pci.h @@ -1188,6 +1188,7 @@ bool pci_pme_capable(struct pci_dev *dev, pci_power_t state); void pci_pme_active(struct pci_dev *dev, bool enable); int pci_enable_wake(struct pci_dev *dev, pci_power_t state, bool enable); int pci_wake_from_d3(struct pci_dev *dev, bool enable); +pci_power_t pci_target_state(struct pci_dev *dev, bool wakeup); int pci_prepare_to_sleep(struct pci_dev *dev); int pci_back_from_sleep(struct pci_dev *dev); bool pci_dev_run_wake(struct pci_dev *dev); @@ -1672,6 +1673,8 @@ static inline int pci_set_power_state(struct pci_dev *dev, pci_power_t state) { return 0; } static inline int pci_wake_from_d3(struct pci_dev *dev, bool enable) { return 0; } +pci_power_t pci_target_state(struct pci_dev *dev, bool wakeup) +{ return PCI_D0; } static inline pci_power_t pci_choose_state(struct pci_dev *dev, pm_message_t state) { return PCI_D0; } -- 2.17.1