Messages in this thread | | | Date | Wed, 13 Mar 2024 01:48:21 +0100 | From | Andi Shyti <> | Subject | Re: [PATCH v4 03/18] i2c: omap: wakeup the controller during suspend() callback |
| |
Hi Wolfram,
On Tue, Mar 12, 2024 at 09:03:27AM +0100, Wolfram Sang wrote: > On Fri, Mar 08, 2024 at 10:42:40AM +0200, Tony Lindgren wrote: > > * Thomas Richard <thomas.richard@bootlin.com> [240304 15:36]: > > > 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. > > > > Reviewed-by: Tony Lindgren <tony@atomide.com> > > I fully trust Tony and I assume that this series should go in via some > other tree than I2C. So: > > Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com> > > Andi, do you agree?
Agree... but who is going to take this? Eventually I can just this one.
Andi
| |