On 06/07/2013 11:51 PM, Kevin Hilman wrote:
Grygorii Strashko grygorii.stras...@ti.com writes:
From: Kevin Hilman khil...@deeprootsystems.com
Currently, runtime PM is used to keep the device enabled only during
active transfers and for a configurable runtime PM autosuspend timout
after an
Hi,
On Wed, Jun 19, 2013 at 09:35:38PM +0300, Grygorii Strashko wrote:
On 06/07/2013 11:51 PM, Kevin Hilman wrote:
Grygorii Strashko grygorii.stras...@ti.com writes:
From: Kevin Hilman khil...@deeprootsystems.com
Currently, runtime PM is used to keep the device enabled only during
active
Felipe Balbi ba...@ti.com writes:
[...]
If you have 200 pm_runtime_get() followed by 200 pm_runtime_put() (put
is called only after 200 gets, no put-get ping-pong), your
-runtime_resume() gets called once, your -runtime_suspend() gets
called once but your -runtime_idle() will get called 200
Hi,
On Wed, Jun 19, 2013 at 01:01:28PM -0700, Kevin Hilman wrote:
Felipe Balbi ba...@ti.com writes:
[...]
If you have 200 pm_runtime_get() followed by 200 pm_runtime_put() (put
is called only after 200 gets, no put-get ping-pong), your
-runtime_resume() gets called once, your
Grygorii Strashko grygorii.stras...@ti.com writes:
From: Kevin Hilman khil...@deeprootsystems.com
Currently, runtime PM is used to keep the device enabled only during
active transfers and for a configurable runtime PM autosuspend timout
after an xfer.
In addition to idling the device,
