From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH RFC] PCI/PME: fix PME runtime PM handling
Date: Mon, 31 Dec 2018 12:56:46 +0200 [thread overview]
Message-ID: <20181231105646.GD2469@lahna.fi.intel.com> (raw)
In-Reply-To: <2ac489b3-a091-bfce-32f1-b6fc86f3337c@gmail.com>
On Mon, Dec 31, 2018 at 11:37:20AM +0100, Heiner Kallweit wrote:
> After reading again your commit message for adding the PME runtime PM
> callbacks: It seems that you focused on root ports only when adding
> this functionality. Should there be a check whether port is a root port?
This particular PME functionality (native PCIe PME) is present only on
root ports and the pcie_pme driver only binds to those.
next prev parent reply other threads:[~2018-12-31 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 11:06 [PATCH RFC] PCI/PME: fix PME runtime PM handling Heiner Kallweit
2018-12-31 9:32 ` Mika Westerberg
2018-12-31 9:48 ` Heiner Kallweit
2018-12-31 10:37 ` Heiner Kallweit
2018-12-31 10:56 ` Mika Westerberg [this message]
2018-12-31 13:30 ` Heiner Kallweit
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=20181231105646.GD2469@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-pci@vger.kernel.org \
/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