summaryrefslogtreecommitdiffstats
path: root/drivers/acpi
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-11-07 01:42:17 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-11-07 01:42:17 +0100
commit176a88d79d6b5aebabaff16734e8b3107efcaaad (patch)
treee1596a11b07144b9ccbdd12ebe7d3dd902a3f4ca /drivers/acpi
parentACPI / hotplug: Carry out PCI root eject directly (diff)
downloadlinux-176a88d79d6b5aebabaff16734e8b3107efcaaad.tar.xz
linux-176a88d79d6b5aebabaff16734e8b3107efcaaad.zip
ACPI / hotplug: Do not execute "insert in progress" _OST
According to the ACPI spec (5.0, Section 6.3.5), the "Device insertion in progress (pending)" (0x80) _OST status code is reserved for the "Insertion Processing" (0x200) source event which is "a result of an OSPM action". Specifically, it is not a notification, so that status code should not be used during notification processing, which unfortunately is done by acpi_scan_bus_device_check(). For this reason, drop the ACPI_OST_SC_INSERT_IN_PROGRESS _OST status evaluation from there (it was a mistake to put it in there in the first place). Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Cc: All applicable <stable@vger.kernel.org>
Diffstat (limited to 'drivers/acpi')
-rw-r--r--drivers/acpi/scan.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index c7317fe213bf..5cd7f8c5666a 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -343,8 +343,6 @@ static void acpi_scan_bus_device_check(acpi_handle handle, u32 ost_source)
goto out;
}
}
- acpi_evaluate_hotplug_ost(handle, ost_source,
- ACPI_OST_SC_INSERT_IN_PROGRESS, NULL);
error = acpi_bus_scan(handle);
if (error) {
acpi_handle_warn(handle, "Namespace scan failure\n");