From: Alan Stern <stern@rowland.harvard.edu>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Kai Heng Feng <kai.heng.feng@canonical.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
<linux-pci@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
<linux-usb@vger.kernel.org>
Subject: Re: [PATCH] PCI / PM: Don't runtime suspend when device only supports wakeup from D0
Date: Wed, 22 May 2019 14:39:56 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1905221433310.1410-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20190522181157.GC79339@google.com>
On Wed, 22 May 2019, Bjorn Helgaas wrote:
> On Wed, May 22, 2019 at 11:46:25PM +0800, Kai Heng Feng wrote:
> > > On May 22, 2019, at 9:48 PM, Bjorn Helgaas <helgaas@kernel.org> wrote:
> > > On Wed, May 22, 2019 at 11:42:14AM +0800, Kai Heng Feng wrote:
> > >> at 6:23 AM, Bjorn Helgaas <helgaas@kernel.org> wrote:
> > >>> On Wed, May 22, 2019 at 12:31:04AM +0800, Kai-Heng Feng wrote:
> > >>>> 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.
>
> > > ...
> > > And I guess this patch basically means we wouldn't call the driver's
> > > suspend callback if we're merely going to stay at D0, so the driver
> > > would have no idea anything happened. That might match
> > > Documentation/power/pci.txt better, because it suggests that the
> > > suspend callback is related to putting a device in a low-power state,
> > > and D0 is not a low-power state.
> >
> > Yes, the patch is to let the device stay at D0 and don’t run driver’s own
> > runtime suspend routine.
> >
> > I guess I’ll just proceed to send a V2 with updated commit message?
>
> Now that I understand what "runtime suspended to D0" means, help me
> understand what's actually wrong.
Kai's point is that the xhci-hcd driver thinks the device is now in
runtime suspend, because the runtime_suspend method has been executed.
But in fact the device is still in D0, and as a result, PME signalling
may not work correctly.
On the other hand, it wasn't clear from the patch description whether
this actually causes a problem on real systems. The description only
said that the problem was theoretical.
> The PCI core apparently *does* enable PME when we "suspend to D0".
> But somehow calling the xHCI runtime suspend callback makes the driver
> unable to notice when the PME is signaled?
According to Kai, PME signalling doesn't work in D0 -- or at least, it
is _documented_ not to work in D0 -- even though it is enabled and the
device claims to support it.
In any case, I don't really see any point in "runtime suspending" a
device while leaving it in D0. We might as well just leave it alone.
Alan Stern
next prev parent reply other threads:[~2019-05-22 18:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 16:31 [PATCH] PCI / PM: Don't runtime suspend when device only supports wakeup from D0 Kai-Heng Feng
2019-05-21 22:23 ` Bjorn Helgaas
2019-05-22 3:42 ` Kai Heng Feng
2019-05-22 13:48 ` Bjorn Helgaas
2019-05-22 15:46 ` Kai Heng Feng
2019-05-22 18:11 ` Bjorn Helgaas
2019-05-22 18:39 ` Alan Stern [this message]
2019-05-22 18:53 ` Lukas Wunner
2019-05-22 19:05 ` Kai Heng Feng
2019-05-22 20:52 ` Bjorn Helgaas
2019-05-23 4:39 ` Kai-Heng Feng
2019-05-27 16:57 ` Bjorn Helgaas
2019-06-05 11:57 ` Bjorn Helgaas
2019-07-05 7:02 ` Kai-Heng Feng
2019-07-05 9:39 ` Rafael J. Wysocki
2019-07-05 13:51 ` Kai-Heng Feng
2019-07-09 13:45 ` Bjorn Helgaas
2019-09-02 13:47 ` Kai-Heng Feng
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=Pine.LNX.4.44L0.1905221433310.1410-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=helgaas@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=rafael.j.wysocki@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).