Revision 9e16721498b0c3d3ebfa0b503c63d35c0a4c0642 authored by Colin Ian King on 27 November 2012, 14:09:40 UTC, committed by Bjorn Helgaas on 14 January 2013, 23:23:42 UTC
Right now using pcie_aspm=force will not enable ASPM if the FADT indicates ASPM is unsupported. However, the semantics of force should probably allow for this, especially as they did before 3c076351c4 ("PCI: Rework ASPM disable code") This patch just skips the clearing of any ASPM setup that the firmware has carried out on this bus if pcie_aspm=force is being used. Reference: http://bugs.launchpad.net/bugs/962038 Signed-off-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> CC: stable@vger.kernel.org
1 parent d712f68
File | Mode | Size |
---|---|---|
.gitignore | -rw-r--r-- | 10 bytes |
Kconfig | -rw-r--r-- | 1.5 KB |
Makefile | -rw-r--r-- | 662 bytes |
eisa-bus.c | -rw-r--r-- | 10.6 KB |
eisa.ids | -rw-r--r-- | 54.4 KB |
pci_eisa.c | -rw-r--r-- | 1.7 KB |
virtual_root.c | -rw-r--r-- | 1.7 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...