diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2010-02-17 23:40:07 +0100 |
---|---|---|
committer | Jesse Barnes <jbarnes@virtuousgeek.org> | 2010-02-22 16:20:39 -0800 |
commit | c39fae1416d59fd565606793f090cebe3720d50d (patch) | |
tree | f53b3dc3202706c328c2306f168058ec2e9ae859 /drivers/sfi | |
parent | c7f486567c1d0acd2e4166c47069835b9f75e77b (diff) | |
download | kernel_samsung_aries-c39fae1416d59fd565606793f090cebe3720d50d.zip kernel_samsung_aries-c39fae1416d59fd565606793f090cebe3720d50d.tar.gz kernel_samsung_aries-c39fae1416d59fd565606793f090cebe3720d50d.tar.bz2 |
PCI PM: Make it possible to force using INTx for PCIe PME signaling
Apparently, some machines may have problems with PCI run-time power
management if MSIs are used for the native PCIe PME signaling. In
particular, on the MSI Wind U-100 PCIe PME interrupts are not
generated by a PCIe root port after a resume from suspend to RAM, if
the system wake-up was triggered by a PME from the device attached to
this port. [It doesn't help to free the interrupt on suspend and
request it back on resume, even if that is done along with disabling
the MSI and re-enabling it, respectively.] However, if INTx
interrupts are used for this purpose on the same machine, everything
works just fine.
For this reason, add a kernel command line switch allowing one to
request that MSIs be not used for the native PCIe PME signaling,
introduce a DMI table allowing us to blacklist machines that need
this switch to be set by default and put the MSI Wind U-100 into this
table.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'drivers/sfi')
0 files changed, 0 insertions, 0 deletions