On Wed, Apr 27, 2022 at 02:21:26PM +0100, Mark Brown wrote:
> On Wed, Apr 27, 2022 at 08:12:56AM -0500, Adam Ford wrote:
> > I found this:
> > static const struct dev_pm_ops wm8962_pm = {
> > + SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume)
> > SET_RUNTIME_PM_OPS(wm8962_runtime_suspend, wm8962_runtime_resume, NULL)
> > };
>
> > I applied this, and it appears to make the issue go away on a 5.15
> > kernel. I haven't tried it on a 5.18 yet. If this fixes the issue,
> > would that be an acceptable solution to push upstream?
>
> Yes, that's fine - it's fixing the thing I was pointing out with only
> having runtime suspend but no system suspend.
:-) Well in that case ignore my email, I don't mind if we want to
go this way too.
Thanks,
Charles
