diff options
| author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-02-08 23:40:37 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <rjw@sisk.pl> | 2011-02-24 19:58:53 +0100 |
| commit | 5190726765b40774c069e187a958e10ccd970e65 (patch) | |
| tree | 6cdfc76171e907232f91e4a094ee8ffbcc8e9797 /drivers/acpi/scan.c | |
| parent | 2aa15890f3c191326678f1bd68af61ec6b8753ec (diff) | |
| download | kernel_goldelico_gta04-5190726765b40774c069e187a958e10ccd970e65.zip kernel_goldelico_gta04-5190726765b40774c069e187a958e10ccd970e65.tar.gz kernel_goldelico_gta04-5190726765b40774c069e187a958e10ccd970e65.tar.bz2 | |
ACPI: Remove the wakeup.run_wake_count device field
The wakeup.run_wake_count ACPI device field is only used by the PCI
runtime PM code to "protect" devices from being prepared for
generating wakeup signals more than once in a row. However, it
really doesn't provide any protection, because (1) all of the
functions it is supposed to protect use their own reference counters
effectively ensuring that the device will be set up for generating
wakeup signals just once and (2) the PCI runtime PM code uses
wakeup.run_wake_count in a racy way, since nothing prevents
acpi_dev_run_wake() from being called concurrently from two different
threads for the same device.
Remove the wakeup.run_wake_count ACPI device field which is
unnecessary, confusing and used in a wrong way.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'drivers/acpi/scan.c')
| -rw-r--r-- | drivers/acpi/scan.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c index b99e624..b136c9c 100644 --- a/drivers/acpi/scan.c +++ b/drivers/acpi/scan.c @@ -797,7 +797,6 @@ static void acpi_bus_set_run_wake_flags(struct acpi_device *device) acpi_status status; acpi_event_status event_status; - device->wakeup.run_wake_count = 0; device->wakeup.flags.notifier_present = 0; /* Power button, Lid switch always enable wakeup */ |