Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp6392571ybp; Tue, 15 Oct 2019 14:20:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqxpEVLeFmhjYDcv7ne6qHMlKjSuxK9zjIs/YUihlmZJwCbGB0n5r+xTdWiD5fmpFS+geKxN X-Received: by 2002:a05:6402:160f:: with SMTP id f15mr35607940edv.142.1571174439150; Tue, 15 Oct 2019 14:20:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571174439; cv=none; d=google.com; s=arc-20160816; b=N9gSq4xiY35+iYaCsPNyn3POYmScKcQ7Ugyi41Iig5cXGtGb1WUKqYNb7k+GbAvHBq kmgZcZbi3oMd7pM3QYVF8TqSz3ruZSJyuZzJgcqErctDP/hPPdV5RNy86R1dj+T3fwD5 PgaR3GlW2SXRykRSYy1h/iOtjf+7O3QuguO8T6YcEqPBDZZAjQ4UU52+Y2LNYTAiYjOL ZhO8aad7xTzqShS522ABYLW8ycmr/NFGrlwO2znO9VY4KS90APBUWwPzIKbbY0g/HcqK 9mLwBhvQ+XCtadJG/IZ9myRVzVaPE8lQOzCJOjcVsMGcDogB260ZzI6cvnU7tr7v9Pez oQzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=6IlyJsV+DsNNwdKN4TaQXxH9yUZHMDIan19OSUGyDWY=; b=YNBwR5JSS/flWr5d6860VLZUQ89js0sbBQGp9y5j90p529QJEdEA7DOcP2b5yjMZ/1 mTMLYxSQnV0lmMSiwrMS/0YtiPesLbnGorL+hN28LZPQrf3jWG8GAHu9+UcG60iC6STo ZNTkFMNNHjBCS/cKcsE80C16d0lNMKTPtGzOK+mEfxz1XLjytEW7sr9GbxHmQ8e0zMmq 6YOjSAfg12JbwnRVJJ6RAUbSewBB4LHcb8eQWxM1LzMSTLRy8bjLfC6Cbk0ZoNPCiBv9 TrQ07gZBgiwCEHvhpr1kMx4GUdzznZvgxzkITrZIoLnHy9kH91ZGnYVCgTqDo0jT29th IbiQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h17si15722538edb.89.2019.10.15.14.20.16; Tue, 15 Oct 2019 14:20:39 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731026AbfJORUE (ORCPT + 99 others); Tue, 15 Oct 2019 13:20:04 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:63884 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728575AbfJORUD (ORCPT ); Tue, 15 Oct 2019 13:20:03 -0400 Received: from 79.184.254.38.ipv4.supernova.orange.pl (79.184.254.38) (HELO kreacher.localnet) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.292) id dda85748e3f31afb; Tue, 15 Oct 2019 19:20:02 +0200 From: "Rafael J. Wysocki" To: Bjorn Helgaas Cc: Dexuan Cui , "Rafael J . Wysocki" , Lorenzo Pieralisi , Michael Kelley , Sasha Levin , Haiyang Zhang , KY Srinivasan , Stephen Hemminger , olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com, vkuznets@redhat.com, marcelo.cerri@canonical.com, jackm@mellanox.com, linux-pci@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, driverdev-devel@linuxdriverproject.org, Bjorn Helgaas Subject: Re: [PATCH 3/7] PCI/PM: Clear PCIe PME Status even for legacy power management Date: Tue, 15 Oct 2019 19:20:01 +0200 Message-ID: <4241660.MG63sYxJne@kreacher> In-Reply-To: <20191014230016.240912-4-helgaas@kernel.org> References: <20191014230016.240912-1-helgaas@kernel.org> <20191014230016.240912-4-helgaas@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, October 15, 2019 1:00:12 AM CEST Bjorn Helgaas wrote: > From: Bjorn Helgaas > > Previously, pci_pm_resume_noirq() cleared the PME Status bit in the Root > Status register only if the device had no driver or the driver did not > implement legacy power management. It should clear PME Status regardless > of what sort of power management the driver supports, so do this before > checking for legacy power management. > > This affects Root Ports and Root Complex Event Collectors, for which the > usual driver is the PCIe portdrv, which implements new power management, so > this change is just on principle, not to fix any actual defects. > > Fixes: a39bd851dccf ("PCI/PM: Clear PCIe PME Status bit in core, not PCIe port driver") > Signed-off-by: Bjorn Helgaas This is a reasonable change in my view, so Reviewed-by: Rafael J. Wysocki > --- > drivers/pci/pci-driver.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c > index d4ac8ce8c1f9..0c3086793e4e 100644 > --- a/drivers/pci/pci-driver.c > +++ b/drivers/pci/pci-driver.c > @@ -941,12 +941,11 @@ static int pci_pm_resume_noirq(struct device *dev) > pci_pm_default_resume_early(pci_dev); > > pci_fixup_device(pci_fixup_resume_early, pci_dev); > + pcie_pme_root_status_cleanup(pci_dev); > > if (pci_has_legacy_pm_support(pci_dev)) > return pci_legacy_resume_early(dev); > > - pcie_pme_root_status_cleanup(pci_dev); > - > if (drv && drv->pm && drv->pm->resume_noirq) > error = drv->pm->resume_noirq(dev); > >