[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201209202131.13483.rjw@sisk.pl>
Date: Thu, 20 Sep 2012 21:31:13 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Huang Ying <ying.huang@...el.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org, linux-pm@...r.kernel.org,
Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: [RFC 3/3] PCI/PM: Disable PME poll for PCIe devices
On Monday, September 17, 2012, Huang Ying wrote:
> PME poll is not necessary for PCIe devices, because PCIe devices use
> in-band PME message and IRQ on PCIe port to report PME.
Alas, not all of them as it turns out and even if they do, it doesn't
work for some of them. That's why we've added the PCIe devices polling
(quite recently, for that matter).
If you'd spent some time on some proper research regarding that (like browsing
the changelogs of git commits modifying the relevant part of drivers/pci/pci.c),
you'd have known that already.
And that actually is quite important, because I don't have to remember every
single PM-related change we're making in the PCI layer. I _incidentally_ do
remember this one, but that may not happen next time. Please do the research
_before_ proposing changes of this kind.
Thanks,
Rafael
> PME poll is useful for PCI devices. Because for PCI devices, PME is
> reported via a side-band PME# line and some platform logic, and the
> platform logic is often missing on many systems.
>
> Signed-off-by: Huang Ying <ying.huang@...el.com>
> ---
> drivers/pci/pcie/pme.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/drivers/pci/pcie/pme.c
> +++ b/drivers/pci/pcie/pme.c
> @@ -313,6 +313,7 @@ static int pcie_pme_set_native(struct pc
>
> device_set_run_wake(&dev->dev, true);
> dev->pme_interrupt = true;
> + dev->pme_poll = false;
> return 0;
> }
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists