[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190131170746.7604-1-mika.westerberg@linux.intel.com>
Date: Thu, 31 Jan 2019 20:07:44 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Lukas Wunner <lukas@...ner.de>,
Heiner Kallweit <hkallweit1@...il.com>,
Sinan Kaya <okaya@...eaurora.org>,
Keith Busch <keith.busch@...el.com>,
Oza Pawandeep <poza@...eaurora.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] PCI: Fix runtime PME generation from D3hot
Hi all,
Heiner reported [1] that runtime PME generation of his network card does
not work after commit 0e157e528604 ("PCI/PME: Implement runtime PM
callbacks") that landed in v4.20. Reverting the commit helps but it has
another drawback, which I originally tried to solve with the commit, that
the PCIe hierarchy wakes up immediately after being put into D3cold.
This series of two patches tries to fix both issues so that PME wakes up
from D3hot and that the hierarchy does not wake up immediately from D3cold.
The previous version of the series can be found here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1892241.html
Changes from the previous version:
* Add tags from Heiner and Rafael
* Update changelog to mention relevent PCIe spec sections
* Add comment to pcie_disable_interrupt() explaining why and what is
masked
[1] https://www.spinics.net/lists/linux-pci/msg79051.html
Mika Westerberg (2):
Revert "PCI/PME: Implement runtime PM callbacks"
PCI: pciehp: Disable Data Link Layer State Changed event on suspend
drivers/pci/hotplug/pciehp_hpc.c | 17 +++++++++++++++--
drivers/pci/pcie/pme.c | 27 ---------------------------
2 files changed, 15 insertions(+), 29 deletions(-)
--
2.20.1
Powered by blists - more mailing lists