[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gBpDKpRbhx0tbLWXG1e8Dd4ZPZGDQ5Vq2f8phX2cpFGg@mail.gmail.com>
Date: Tue, 1 Aug 2017 13:51:16 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "Usyskin, Alexander" <alexander.usyskin@...el.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Dominik Brodowski <linux@...inikbrodowski.net>,
"Winkler, Tomas" <tomas.winkler@...el.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: Issue with commit de3ef1eb1cd - PM / core: Drop run_wake flag
from struct dev_pm_info [Was: MEI-related WARN_ON() triggered during
resume-from-sleep on v4.13-rc2+]
Hi,
On Tue, Aug 1, 2017 at 7:25 AM, Usyskin, Alexander
<alexander.usyskin@...el.com> wrote:
> Hi
>
> We using pci_dev_run_wake that changed in mentioned patch to decide
> if to replace usual PM callbacks with domain ones.
> IIRC, the mei device is not remote wakeable on that platform,
> so we should set domain callbacks.
> There was a patch in PM framework that squashes runtime suspend with
> usual suspend for some devices.
> May it be that now pci_dev_run_wake returns true form mei and we are
> not setting domain callbacks?
> In that case we going through PCI device level PM path and may trigger that squash.
> That will explain lack of mei logs on suspend.
>
> Dominik, can you try comment out "if (!pci_dev_run_wake(pdev))"
> at drivers/misc/mei/pci-me.c (around line 223) to set domain callbacks by force
> to see if this is indeed the case?
Why exactly do you need the pci_dev_run_wake(pdev) check?
Thanks,
Rafael
Powered by blists - more mailing lists