diff options
| author |   Thomas Richard <thomas.richard@bootlin.com> | 2024-06-13 15:13:28 +0200 |
|---|---|---|
| committer |   Andi Shyti <andi.shyti@kernel.org> | 2024-07-09 00:46:07 +0200 |
| commit | 7da7fd7e66ac9b0d4287aefba516795145f3c722 (patch) | |
| tree | 78b10527339df2fe00b67fb2b74193834a3880b2 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | i2c: omap: switch to NOIRQ_SYSTEM_SLEEP_PM_OPS() and RUNTIME_PM_OPS() (diff) | |
| download | wireguard-linux-7da7fd7e66ac9b0d4287aefba516795145f3c722.tar.xz wireguard-linux-7da7fd7e66ac9b0d4287aefba516795145f3c722.zip | |
i2c: omap: wakeup the controller during suspend() callback
A device may need the controller up during suspend_noirq() or
resume_noirq().
But if the controller is autosuspended, there is no way to wakeup it during
suspend_noirq() or resume_noirq() because runtime pm is disabled at this
time.
The suspend() callback wakes up the controller, so it is available until
its suspend_noirq() callback (pm_runtime_force_suspend()).
During the resume, it's restored by resume_noirq() callback
(pm_runtime_force_resume()). Then resume() callback enables autosuspend.
So the controller is up during a little time slot in suspend and resume
sequences even if it's not used.
Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions