ACPI / init: Fix the ordering of acpi_reserve_resources()
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 7 May 2015 19:19:39 +0000 (21:19 +0200)
committerBen Hutchings <ben@decadent.org.uk>
Thu, 6 Aug 2015 23:32:09 +0000 (00:32 +0100)
commitd370a4107e9b9fcbf76e23119e6fb447c42c3f91
treeda43bd04e59dc74a1741a37b9bf3730e66dbca3f
parentbbdef5d38abb4917f4f25bc3f94ccf4ff46ffec5
ACPI / init: Fix the ordering of acpi_reserve_resources()

commit b9a5e5e18fbf223502c0b2264c15024e393da928 upstream.

Since acpi_reserve_resources() is defined as a device_initcall(),
there's no guarantee that it will be executed in the right order
with respect to the rest of the ACPI initialization code.  On some
systems this leads to breakage if, for example, the address range
that should be reserved for the ACPI fixed registers is given to
the PCI host bridge instead if the race is won by the wrong code
path.

Fix this by turning acpi_reserve_resources() into a void function
and calling it directly from within the ACPI initialization sequence.

Reported-and-tested-by: George McCollister <george.mccollister@gmail.com>
Link: http://marc.info/?t=143092384600002&r=1&w=2
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/acpi/osl.c