diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-06-24 02:56:13 +0300 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-06-28 02:52:38 +0300 |
commit | 8370c2dc4c7b91be7e1231130f0ae08b5aebecf4 (patch) | |
tree | ee4c1a4d35ef7ed39107e61a8846f1db2405425f /drivers/amba | |
parent | 4d183d04195318c8ee8bce048f3f9a89c0e2056d (diff) | |
download | linux-8370c2dc4c7b91be7e1231130f0ae08b5aebecf4.tar.xz |
PCI / PM: Drop pme_interrupt flag from struct pci_dev
The pme_interrupt flag in struct pci_dev is set when PMEs generated
by the device are going to be signaled via root port PME interrupts.
Ironically enough, that information is only used by the code setting
up device wakeup through ACPI which returns as soon as it sees the
pme_interrupt flag set while setting up "remote runtime wakeup".
That is questionable, however, because in theory there may be PCIe
devices using out-of-band PME signaling under root ports handled
by the native PME code or devices requiring wakeup power setup to be
carried out by AML. For such devices, ACPI wakeup should be invoked
regardless of whether or not native PME signaling is used in general.
For this reason, drop the pme_interrupt flag and rework the code
using it which then allows the ACPI-based device wakeup handling
in PCI to be consolidated to use one code path for both "runtime
remote wakeup" and system wakeup (from sleep states).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'drivers/amba')
0 files changed, 0 insertions, 0 deletions