diff options
| author | Brian Norris <briannorris@chromium.org> | 2026-09-29 19:49:53 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2026-09-30 14:52:37 +0200 |
| commit | aedc51762a0d3d4a50d1542b59aafcd6060c4b39 (patch) | |
| tree | 7e7dfd6f9ba86f03f187d0767411b20279da2601 /tools/perf/scripts/python | |
| parent | 86122467eea539ac13d40b6938abd1fbb40fb640 (diff) | |
PM: runtime: Clarify ->runtime_idle() callback return value handling
This doc says "Negative error return codes are ignored by the PM core"
for ->runtime_idle(). This is misleading: any non-zero return value
(including negative error codes such as -EBUSY or -EAGAIN) tells the PM
core to abort automatic suspension of the device, which is commonly used
by subsystems to prevent immediate runtime suspend.
Clarify that unlike ->runtime_suspend() and ->runtime_resume(), the PM core
does not treat negative return values from ->runtime_idle() as a fatal
device error, and that any non-zero value stops the PM core from
suspending the device.
Signed-off-by: Brian Norris <briannorris@chromium.org>
Link: https://patch.msgid.link/20260929194956.v3.5.If6e26acac7770c65446dd0b81f891948abb38973@changeid
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
