[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72961010-c82a-7d2c-5e43-2c3bb301b3d2@gmail.com>
Date: Mon, 7 Jan 2019 19:54:18 +0100
From: Heiner Kallweit <hkallweit1@...il.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Lukas Wunner <lukas@...ner.de>, Sinan Kaya <okaya@...eaurora.org>,
Keith Busch <keith.busch@...el.com>,
Oza Pawandeep <poza@...eaurora.org>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] PCI: Fix runtime PME generation from D3hot
On 07.01.2019 15:39, Mika Westerberg wrote:
> 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.
>
> [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 | 10 ++++++++--
> drivers/pci/pcie/pme.c | 27 ---------------------------
> 2 files changed, 8 insertions(+), 29 deletions(-)
>
Works for me. But that's not a miracle because on my system
CONFIG_HOTPLUG_PCI isn't set and therefore effectively just the
runtime ops are removed again. And we tested before that this
fixes the issue for me. Thanks for the analysis and the fix!
So for the runtime PM PME generation:
Tested-by: Heiner Kallweit <hkallweit1@...il.com>
Powered by blists - more mailing lists