diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2013-11-07 01:42:17 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-11-29 10:42:16 -0800 |
commit | f30d41a69154f0397173666a10d1a9fb072317fd (patch) | |
tree | c6b1962d75f7839fb2730bbc6413b2f794498475 | |
parent | a703296bb152a6cf4b85fb0a673d54ab9d0709e3 (diff) | |
download | kernel-common-f30d41a69154f0397173666a10d1a9fb072317fd.tar.gz kernel-common-f30d41a69154f0397173666a10d1a9fb072317fd.tar.bz2 kernel-common-f30d41a69154f0397173666a10d1a9fb072317fd.zip |
ACPI / hotplug: Do not execute "insert in progress" _OST
commit 176a88d79d6b5aebabaff16734e8b3107efcaaad upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r-- | drivers/acpi/scan.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c index 8a46c924effd..0ebb955bc03a 100644 --- a/drivers/acpi/scan.c +++ b/drivers/acpi/scan.c @@ -359,8 +359,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"); |