]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing
authorBjorn Helgaas <bhelgaas@google.com>
Tue, 9 Jun 2015 22:31:38 +0000 (17:31 -0500)
committerJiri Slaby <jslaby@suse.cz>
Thu, 30 Jul 2015 12:10:45 +0000 (14:10 +0200)
commit601291ed9d980a016c4a95cbf2d1ef4bf1aed503
tree462aaa6e0a2912686af8a399ab6976530c811591
parent5029d7e0b1f8fc45efdc6fad2dd688801476b505
x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing

commit 3d9fecf6bfb8b12bc2f9a4c7109895a2a2bb9436 upstream.

We enable _CRS on all systems from 2008 and later.  On older systems, we
ignore _CRS and assume the whole physical address space (excluding RAM and
other devices) is available for PCI devices, but on systems that support
physical address spaces larger than 4GB, it's doubtful that the area above
4GB is really available for PCI.

After d56dbf5bab8c ("PCI: Allocate 64-bit BARs above 4G when possible"), we
try to use that space above 4GB *first*, so we're more likely to put a
device there.

On Juan's Toshiba Satellite Pro U200, BIOS left the graphics, sound, 1394,
and card reader devices unassigned (but only after Windows had been
booted).  Only the sound device had a 64-bit BAR, so it was the only device
placed above 4GB, and hence the only device that didn't work.

Keep _CRS enabled even on pre-2008 systems if they support physical address
space larger than 4GB.

Fixes: d56dbf5bab8c ("PCI: Allocate 64-bit BARs above 4G when possible")
Reported-and-tested-by: Juan Dayer <jdayer@outlook.com>
Reported-and-tested-by: Alan Horsfield <alan@hazelgarth.co.uk>
Link: https://bugzilla.kernel.org/show_bug.cgi?id=99221
Link: https://bugzilla.opensuse.org/show_bug.cgi?id=907092
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Jiri Slaby <jslaby@suse.com>
arch/x86/pci/acpi.c