[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200417151447.GM37466@atomide.com>
Date: Fri, 17 Apr 2020 08:14:47 -0700
From: Tony Lindgren <tony@...mide.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Andreas Kemnade <andreas@...nade.info>,
Evgeniy Polyakov <zbr@...emap.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
Adam Ford <aford173@...il.com>,
"Andrew F . Davis" <afd@...com>, Vignesh R <vigneshr@...com>
Subject: Re: [PATCHv3] w1: omap-hdq: Simplify driver with PM runtime
autosuspend
* Tony Lindgren <tony@...mide.com> [200417 15:08]:
> Maybe the PM runtime usecounts get unbalanced somewhere in the
> driver where we end up with driver permanently in disabled state?
Or it could be that with omap_hdq.c no longer blocking SoC
deeper idle states, omap_hdq.c now loses context if you have
omap3 off mode enabled during idle?
If so, this can easily be fixed by adding a cpu_pm notifier
along the lines of what we already have for few drivers:
$ git grep -e CLUSTER_PM_ENTER -e CLUSTER_PM_EXIT
Regards,
Tony
Powered by blists - more mailing lists