summaryrefslogtreecommitdiff
path: root/src/soc/intel/baytrail/Kconfig
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2018-03-02 14:47:11 -0800
committerPatrick Georgi <pgeorgi@google.com>2018-03-06 08:47:59 +0000
commitfd50b7c3d75bd3889cfa1f16e7b93c7ed1a3451c (patch)
treeac3f3de2adc6fd2203adcebb6d5ecb6abd607f61 /src/soc/intel/baytrail/Kconfig
parent3879ef49ea4dd2186614295f4aeb9e43c252b553 (diff)
soc/intel: Fix MCFG end bus number
The ACPI MCFG table is generated with a static end bus number of 255, which expects that the reserved range in E820 is 256MB. However the actual MCFG range is configurable with Kconfig, so these two values may not match when the OS tries to determine the range: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) PCI: MMCONFIG 0000 [bus 00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000) (size reduced!) acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge Instead of forcing the end bus number to be 255 use the Kconfig value to set it based on the current configuration. Tested on a fizz device to ensure that the kernel no longer complains: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000) Change-Id: I999ea9b72b9deba5f27dd692faa0408427a0bf89 Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://review.coreboot.org/24974 Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/soc/intel/baytrail/Kconfig')
0 files changed, 0 insertions, 0 deletions