Re: [PATCH v2 2/2] dmaengine: tegra210-adma: update system sleep callbacks

2019-03-13 Thread Sameer Pujar
On 3/13/2019 4:19 PM, Jon Hunter wrote: On 13/03/2019 10:40, Sameer Pujar wrote: On 3/13/2019 3:58 PM, Jon Hunter wrote: On 13/03/2019 05:43, Sameer Pujar wrote: If the driver is active till late suspend, where runtime PM cannot run, force suspend is essential in such case to put the device

Re: [PATCH v2 2/2] dmaengine: tegra210-adma: update system sleep callbacks

2019-03-13 Thread Jon Hunter
On 13/03/2019 10:40, Sameer Pujar wrote: > > On 3/13/2019 3:58 PM, Jon Hunter wrote: >> On 13/03/2019 05:43, Sameer Pujar wrote: >>> If the driver is active till late suspend, where runtime PM cannot run, >>> force suspend is essential in such case to put the device in low power >>> state. Thus

Re: [PATCH v2 2/2] dmaengine: tegra210-adma: update system sleep callbacks

2019-03-13 Thread Sameer Pujar
On 3/13/2019 3:58 PM, Jon Hunter wrote: On 13/03/2019 05:43, Sameer Pujar wrote: If the driver is active till late suspend, where runtime PM cannot run, force suspend is essential in such case to put the device in low power state. Thus pm_runtime_force_suspend and pm_runtime_force_resume are u

Re: [PATCH v2 2/2] dmaengine: tegra210-adma: update system sleep callbacks

2019-03-13 Thread Jon Hunter
On 13/03/2019 05:43, Sameer Pujar wrote: > If the driver is active till late suspend, where runtime PM cannot run, > force suspend is essential in such case to put the device in low power > state. Thus pm_runtime_force_suspend and pm_runtime_force_resume are > used as system sleep callbacks durin

[PATCH v2 2/2] dmaengine: tegra210-adma: update system sleep callbacks

2019-03-12 Thread Sameer Pujar
If the driver is active till late suspend, where runtime PM cannot run, force suspend is essential in such case to put the device in low power state. Thus pm_runtime_force_suspend and pm_runtime_force_resume are used as system sleep callbacks during system wide PM transitions. Signed-off-by: Samee