From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pci@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Bjorn Helgaas <bhelgaas@google.com>,
gregkh@linuxfoundation.org, USB list <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v2] PCI / PM: Avoid using device_may_wakeup() for runtime PM
Date: Fri, 30 Jun 2017 11:16:48 -0500 [thread overview]
Message-ID: <20170630161648.GY17844@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <2677722.OnHOCzR3UZ@aspire.rjw.lan>
On Fri, Jun 23, 2017 at 02:58:11PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> pci_target_state() calls device_may_wakeup() which checks whether
> or not the device may wake up the system from sleep states, but
> pci_target_state() is used for runtime PM too.
>
> Since runtime PM is expected to always enable remote wakeup if
> possible, modify pci_target_state() to take additional argument
> indicating whether or not it should look for a state from which
> the device can signal wakeup and pass either the return value
> of device_can_wakeup(), or "false" (if the device itself is not
> wakeup-capable) to it from the code related to runtime PM.
>
> While at it, fix the comment in pci_dev_run_wake() which is not
> about sleep states.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Applied with Mika's reviewed-by to pci/pm for v4.13, thanks!
> ---
>
> -> v2:
>
> Passing "true" as the second argument to pci_target_state() for runtime PM
> might trigger suboptimal state choices to be made, so pass the return value
> of device_can_wakeup() to it instead and pass "false" to it in pci_dev_run_wake(),
> because that assumes device_can_wakeup() to return "false" already.
>
> ---
> drivers/pci/pci.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> Index: linux-pm/drivers/pci/pci.c
> ===================================================================
> --- linux-pm.orig/drivers/pci/pci.c
> +++ linux-pm/drivers/pci/pci.c
> @@ -1982,12 +1982,13 @@ EXPORT_SYMBOL(pci_wake_from_d3);
> /**
> * pci_target_state - find an appropriate low power state for a given PCI dev
> * @dev: PCI device
> + * @wakeup: Whether or not wakeup functionality will be enabled for the device.
> *
> * Use underlying platform code to find a supported low power state for @dev.
> * 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)
> +static pci_power_t pci_target_state(struct pci_dev *dev, bool wakeup)
> {
> pci_power_t target_state = PCI_D3hot;
>
> @@ -2024,7 +2025,7 @@ static pci_power_t pci_target_state(stru
> if (dev->current_state == PCI_D3cold)
> target_state = PCI_D3cold;
>
> - if (device_may_wakeup(&dev->dev)) {
> + if (wakeup) {
> /*
> * Find the deepest state from which the device can generate
> * wake-up events, make it the target state and enable device
> @@ -2050,13 +2051,14 @@ static pci_power_t pci_target_state(stru
> */
> int pci_prepare_to_sleep(struct pci_dev *dev)
> {
> - pci_power_t target_state = pci_target_state(dev);
> + bool wakeup = device_may_wakeup(&dev->dev);
> + pci_power_t target_state = pci_target_state(dev, wakeup);
> int error;
>
> if (target_state == PCI_POWER_ERROR)
> return -EIO;
>
> - pci_enable_wake(dev, target_state, device_may_wakeup(&dev->dev));
> + pci_enable_wake(dev, target_state, wakeup);
>
> error = pci_set_power_state(dev, target_state);
>
> @@ -2089,9 +2091,10 @@ EXPORT_SYMBOL(pci_back_from_sleep);
> */
> int pci_finish_runtime_suspend(struct pci_dev *dev)
> {
> - pci_power_t target_state = pci_target_state(dev);
> + pci_power_t target_state;
> int error;
>
> + target_state = pci_target_state(dev, device_can_wakeup(&dev->dev));
> if (target_state == PCI_POWER_ERROR)
> return -EIO;
>
> @@ -2127,8 +2130,8 @@ bool pci_dev_run_wake(struct pci_dev *de
> if (!dev->pme_support)
> return false;
>
> - /* PME-capable in principle, but not from the intended sleep state */
> - if (!pci_pme_capable(dev, pci_target_state(dev)))
> + /* PME-capable in principle, but not from the target power state */
> + if (!pci_pme_capable(dev, pci_target_state(dev, false)))
> return false;
>
> while (bus->parent) {
> @@ -2163,9 +2166,10 @@ EXPORT_SYMBOL_GPL(pci_dev_run_wake);
> bool pci_dev_keep_suspended(struct pci_dev *pci_dev)
> {
> struct device *dev = &pci_dev->dev;
> + bool wakeup = device_may_wakeup(dev);
>
> if (!pm_runtime_suspended(dev)
> - || pci_target_state(pci_dev) != pci_dev->current_state
> + || pci_target_state(pci_dev, wakeup) != pci_dev->current_state
> || platform_pci_need_resume(pci_dev)
> || (pci_dev->dev_flags & PCI_DEV_FLAGS_NEEDS_RESUME))
> return false;
> @@ -2183,7 +2187,7 @@ bool pci_dev_keep_suspended(struct pci_d
> spin_lock_irq(&dev->power.lock);
>
> if (pm_runtime_suspended(dev) && pci_dev->current_state < PCI_D3cold &&
> - !device_may_wakeup(dev))
> + !wakeup)
> __pci_pme_active(pci_dev, false);
>
> spin_unlock_irq(&dev->power.lock);
>
prev parent reply other threads:[~2017-06-30 16:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 7:22 [PATCH] usb: host: ehci: workaround PME bug on AMD EHCI controller Kai-Heng Feng
2017-06-09 14:43 ` Alan Stern
2017-06-12 7:04 ` Kai-Heng Feng
2017-06-12 10:12 ` Kai-Heng Feng
2017-06-12 14:18 ` Alan Stern
2017-06-13 4:21 ` Kai-Heng Feng
2017-06-13 17:28 ` Bjorn Helgaas
2017-06-14 18:55 ` Alan Stern
2017-06-15 7:02 ` Kai-Heng Feng
2017-06-15 13:23 ` Bjorn Helgaas
2017-06-15 6:57 ` Kai-Heng Feng
2017-06-15 14:12 ` Alan Stern
2017-06-16 3:07 ` Kai-Heng Feng
2017-06-16 16:18 ` Kai-Heng Feng
2017-06-16 17:30 ` Alan Stern
2017-06-19 3:30 ` Kai-Heng Feng
2017-06-19 17:45 ` Bjorn Helgaas
2017-06-19 18:32 ` Alan Stern
2017-06-19 22:00 ` Rafael J. Wysocki
2017-06-20 2:36 ` Kai-Heng Feng
2017-06-23 0:48 ` [PATCH] PCI / PM: Avoid using device_may_wakeup() for runtime PM Rafael J. Wysocki
2017-06-23 12:58 ` [PATCH v2] " Rafael J. Wysocki
2017-06-29 22:37 ` Rafael J. Wysocki
2017-06-30 8:44 ` Mika Westerberg
2017-06-30 16:16 ` Bjorn Helgaas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170630161648.GY17844@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®