linux-toradex.git/drivers/base/power/generic_ops.c, branch v6.19

PM: sleep: Introduce CALL_PM_OP() macro to simplify code

2025-10-20T17:54:25+00:00

Add CALL_PM_OP() macro to eliminate a repetitive code pattern in
power management generic operations.

Replace analogous driver PM callback invocation logic across all
pm_generic_*() functions with a single macro that handles the NULL
pointer checks and function calls.

This reduces code size while maintaining the same functionality and
improving code maintainability.

Signed-off-by: Kaushlendra Kumar 
Reviewed-by: Dhruva Gole 
Link: https://patch.msgid.link/20250919124437.3075016-1-kaushlendra.kumar@intel.com
[ rjw: Subject and changelog edits, adjust white space ]
Signed-off-by: Rafael J. Wysocki

PM: sleep: Remove unused pm_generic_ wrappers

2025-03-12T20:02:50+00:00

pm_generic_thaw_early() has been unused since 2016's
commit 294f47ffd55c ("PM / Domains: Remove redundant system PM callbacks")

pm_generic_freeze_late() has been unused since 2019's
commit 3cd7957e85e6 ("ACPI: PM: Simplify and fix PM domain hibernation
callbacks")

Remove them.

Signed-off-by: Dr. David Alan Gilbert 
Link: https://patch.msgid.link/20250307021750.457600-1-linux@treblig.org
Signed-off-by: Rafael J. Wysocki

drivers: base: power: add proper SPDX identifiers on files that did not have them.

2019-04-04T18:03:40+00:00

There were a few files in the driver core power code that did not have
SPDX identifiers on them, so fix that up.  At the same time, remove the
"free form" text that specified the license of the file, as that is
impossible for any tool to properly parse.

Cc: "Rafael J. Wysocki" 
Signed-off-by: Greg Kroah-Hartman

PM / sleep: Remove pm_complete_with_resume_check()

2017-10-11T13:40:29+00:00

According to recent changes for ACPI, the are longer any users of
pm_complete_with_resume_check(), thus let's drop it.

Signed-off-by: Ulf Hansson 
Signed-off-by: Rafael J. Wysocki

PM / PCI / ACPI: Kick devices that might have been reset by firmware

2015-10-14T00:17:34+00:00

There is a concern that if the platform firmware was involved in
the system resume that's being completed,  some devices might have
been reset by it and if those devices had the power.direct_complete
flag set during the preceding suspend transition, they may stay
in a reset-power-on state indefinitely (until they are runtime-resumed
and then suspended again).  That may not be a big deal from the
individual device's perspective, but if the system is an SoC, it may
be prevented from entering deep SoC-wide low-power states on idle
because of that.

The devices that are most likely to be affected by this issue are
PCI devices and ACPI-enumerated devices using the general ACPI PM
domain, so to prevent it from happening for those devices, force a
runtime resume for them if they have their power.direct_complete
flags set and the platform firmware was involved in the resume
transition currently in progress.

Signed-off-by: Rafael J. Wysocki

PM / sleep: Drop pm_request_idle() from pm_generic_complete()

2015-10-14T00:17:06+00:00

The pm_request_idle() in pm_generic_complete() is pointless as it is
called with the runtime PM usage counter different from zero (bumped
up by the core during the prepare phase of system suspend) and the
core calls pm_runtime_put() for all devices after executing their
complete callbacks, so drop it.

This allows the PCI PM layer to use pm_generic_complete() too.

Signed-off-by: Rafael J. Wysocki 
Reviewed-by: Ulf Hansson

PM / Runtime: Spelling s/competing/completing/

2014-03-26T15:33:53+00:00

Signed-off-by: Geert Uytterhoeven 
Signed-off-by: Rafael J. Wysocki

PM / Runtime: Implement the pm_generic_runtime functions for CONFIG_PM

2013-12-22T00:39:58+00:00

The pm_generic_runtime_suspend|resume functions were implemented within
CONFIG_PM_RUNTIME.

As we also may use runtime PM callbacks during system suspend, to put
devices into low power state, we need to move the implementation of
pm_generic_runtime_suspend|resume to CONFIG_PM.

This change gives a power domain provision to invoke a platform
driver's runtime PM callback from a power domain's system PM callback.
This were earlier prevented by the platform bus, since it uses the
pm_generic_runtime_suspend|resume functions as runtime PM callbacks.

Cc: Kevin Hilman 
Cc: Alan Stern 
Signed-off-by: Ulf Hansson 
Signed-off-by: Rafael J. Wysocki

PM / Runtime: Rework the "runtime idle" helper routine

2013-06-03T19:49:52+00:00

The "runtime idle" helper routine, rpm_idle(), currently ignores
return values from .runtime_idle() callbacks executed by it.
However, it turns out that many subsystems use
pm_generic_runtime_idle() which checks the return value of the
driver's callback and executes pm_runtime_suspend() for the device
unless that value is not 0.  If that logic is moved to rpm_idle()
instead, pm_generic_runtime_idle() can be dropped and its users
will not need any .runtime_idle() callbacks any more.

Moreover, the PCI, SCSI, and SATA subsystems' .runtime_idle()
routines, pci_pm_runtime_idle(), scsi_runtime_idle(), and
ata_port_runtime_idle(), respectively, as well as a few drivers'
ones may be simplified if rpm_idle() calls rpm_suspend() after 0 has
been returned by the .runtime_idle() callback executed by it.

To reduce overall code bloat, make the changes described above.

Tested-by: Mika Westerberg 
Tested-by: Kevin Hilman 
Signed-off-by: Rafael J. Wysocki 
Acked-by: Kevin Hilman 
Reviewed-by: Ulf Hansson 
Acked-by: Alan Stern

PM / Runtime: Asyncronous idle|suspend devices at system resume

2013-04-12T11:34:57+00:00

Use the asyncronous runtime PM API when returning the runtime
reference for the device after the system resume is completed.

By using the asyncronous runtime PM API we don't have to wait
for each an every device to become idle|suspended. Instead we
can move on and handle the next device in queue.

Signed-off-by: Ulf Hansson 
Signed-off-by: Rafael J. Wysocki