Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp6392661ybp; Tue, 15 Oct 2019 14:20:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqz0zxYA0+JKwz1FI8WuX9ZkiEJOQjAnqPi8+XxzljXUkNRlBRNVoH68L1IPkZNBUsFoNLOW X-Received: by 2002:a17:906:cc85:: with SMTP id oq5mr35470695ejb.81.1571174443211; Tue, 15 Oct 2019 14:20:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571174443; cv=none; d=google.com; s=arc-20160816; b=ebL7MFWG2elrzdcCDmIANWsuBCOkJTcjsFjH0HggEXmO09BSggtKnvZ03e8vSfvUIn UVNNhfqAkfwN+Zf1Mb3OXy+KaUOIqSGVyk3TlKW5QhyO8bwI9z8G7LrXWrqnsSnr+wqF Tz3eftwH/J4e8j8Wk/W+3cYomGVz04EjdFUdcJZ+kDRlOg/vFPvmhbkki30rNYX29IgF NM+32lAYcNIMiP5o0wTXVN6Y9YWBInzjvkcm896Z14fObUlbitX4AxQgAI5GaT3cEOs6 Fj4H/MFyt4XyxGrKK7cirkP22QENPEkKqo+EEjsv2APB+n3LRXKOxVERQvTBAjHPdAQQ m9cA== 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=7NDS1Hkwkw60X10tDEce62FRBAHXaIiudhXhBXP8588=; b=L0yC6ryxx4CRVLlVd58BTeg1OezQ2f0cudpGRfabIsmoc4ECCv6ID3BQPIenYR/O1j JPIMOcCAhFRfjbJ6ccJhh/Ld48HxxbUKP3yc8pzTOYdgdy3ZUZG31bL7yg4NOHxnJHps ejRTwj+qOXDguqacOeYOUidJdRO+EraMxM8aRh1KOrBmQcrInwBGMVBYYblaucKfNA5S n8zmzHqnAgEr3SLshCdpnd/DWiqCJOlbG8UT5XtKQw87mi8N9i9jV7CpQyAyjM6YNuDF EeeLCcmm3l8hGEKBy4wFLoUjmT4vfuO8KmowK1EdwxvnMKNWgTE6GmqwqqC3B4F2mlwP GQ4g== 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 x47si16065149eda.396.2019.10.15.14.20.19; Tue, 15 Oct 2019 14:20:43 -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 S1729757AbfJORVn (ORCPT + 99 others); Tue, 15 Oct 2019 13:21:43 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:41868 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726525AbfJORVm (ORCPT ); Tue, 15 Oct 2019 13:21:42 -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 b5433f87ced3629d; Tue, 15 Oct 2019 19:21:40 +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 4/7] PCI/PM: Run resume fixups before disabling wakeup events Date: Tue, 15 Oct 2019 19:21:39 +0200 Message-ID: <6808286.qxd3Zai2y5@kreacher> In-Reply-To: <20191014230016.240912-5-helgaas@kernel.org> References: <20191014230016.240912-1-helgaas@kernel.org> <20191014230016.240912-5-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:13 AM CEST Bjorn Helgaas wrote: > From: Bjorn Helgaas > > pci_pm_resume() and pci_pm_restore() call pci_pm_default_resume(), which > runs resume fixups before disabling wakeup events: > > static void pci_pm_default_resume(struct pci_dev *pci_dev) > { > pci_fixup_device(pci_fixup_resume, pci_dev); > pci_enable_wake(pci_dev, PCI_D0, false); > } > > pci_pm_runtime_resume() does both of these, but in the opposite order: > > pci_enable_wake(pci_dev, PCI_D0, false); > pci_fixup_device(pci_fixup_resume, pci_dev); > > We should always use the same ordering unless there's a reason to do > otherwise. Right. > Change pci_pm_runtime_resume() to call pci_pm_default_resume() > instead of open-coding this, so the fixups are always done before disabling > wakeup events. > > Signed-off-by: Bjorn Helgaas No concerns about this change, 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 0c3086793e4e..55acb658273f 100644 > --- a/drivers/pci/pci-driver.c > +++ b/drivers/pci/pci-driver.c > @@ -1345,8 +1345,7 @@ static int pci_pm_runtime_resume(struct device *dev) > return 0; > > pci_fixup_device(pci_fixup_resume_early, pci_dev); > - pci_enable_wake(pci_dev, PCI_D0, false); > - pci_fixup_device(pci_fixup_resume, pci_dev); > + pci_pm_default_resume(pci_dev); > > if (pm && pm->runtime_resume) > rc = pm->runtime_resume(dev); >