diff options
| author |   Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2025-10-21 19:33:39 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2025-10-27 20:32:13 +0100 |
| commit | f9f5e22b75b87a98e7645cb1f27c7b457c3c7edb (patch) | |
| tree | 9eb4e37863e82c5c7be567e42a1e1be85ed6a783 /tools/testing/selftests/pidfd/git:/ssh:/git@git.zx2c4.com | |
| parent | Linux 6.18-rc3 (diff) | |
| download | linux-rng-f9f5e22b75b87a98e7645cb1f27c7b457c3c7edb.tar.xz linux-rng-f9f5e22b75b87a98e7645cb1f27c7b457c3c7edb.zip | |
ACPI: TAD: Rearrange runtime PM operations in acpi_tad_remove()
It is not necessary to resume the device upfront in acpi_tad_remove()
because both acpi_tad_disable_timer() and acpi_tad_clear_status()
attempt to resume it, but it is better to prevent it from suspending
between these calls by incrementing its runtime PM usage counter.
Accordingly, replace the pm_runtime_get_sync() call in acpi_tad_remove()
with a pm_runtime_get_noresume() one and put the latter right before the
first invocation of acpi_tad_disable_timer().
In addition, use pm_runtime_put_noidle() to drop the device's runtime
PM usage counter after using pm_runtime_get_noresume() to bump it up
to follow a common pattern and use pm_runtime_suspend() for suspending
the device afterward.
No intentional functional impact.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Link: https://patch.msgid.link/5031965.GXAFRqVoOG@rafael.j.wysocki
Diffstat (limited to 'tools/testing/selftests/pidfd/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions