| commit | 17653a3e098dc20ae1db7459344a81c386625696 | |
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Tue, 22 Jul 2014 23:01:41 +0000 (23 01:01 +0200) | ||
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Tue, 22 Jul 2014 23:01:41 +0000 (23 01:01 +0200) | ||
| tree | 63c7cd4e92102ac257a9274705c672725c10b3fc | treesnapshot (tar.gz zip) |
| parent | f35cec255557d1037ff0d772edfd6e7b1e92cdc0 | commitdiff |
ACPI / PM: Use ACPI_COMPANION() instead of ACPI_HANDLE()
The ACPI_HANDLE() macro evaluates ACPI_COMPANION() internally to
return the handle of the device's ACPI companion, so it is much
more straightforward and efficient to use ACPI_COMPANION()
directly to obtain the device's ACPI companion object instead of
using ACPI_HANDLE() and acpi_bus_get_device() on the returned
handle for the same thing.
Do that in three places in the ACPI device PM code.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
The ACPI_HANDLE() macro evaluates ACPI_COMPANION() internally to
return the handle of the device's ACPI companion, so it is much
more straightforward and efficient to use ACPI_COMPANION()
directly to obtain the device's ACPI companion object instead of
using ACPI_HANDLE() and acpi_bus_get_device() on the returned
handle for the same thing.
Do that in three places in the ACPI device PM code.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
| drivers/acpi/device_pm.c | diffblobblamehistory |