Santosh Shilimkar santosh.shilim...@ti.com writes:
On Saturday 09 February 2013 02:49 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
Current CPU PM code code make use of common cpu_suspend() path for all the
CPU power states which is not optimal. In fact
On Tuesday 12 February 2013 08:48 PM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Saturday 09 February 2013 02:49 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
Current CPU PM code code make use of common cpu_suspend() path for all
On Saturday 09 February 2013 02:49 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
Current CPU PM code code make use of common cpu_suspend() path for all the
CPU power states which is not optimal. In fact cpu_suspend() path is needed
only when we put CPU power domain
Current CPU PM code code make use of common cpu_suspend() path for all the
CPU power states which is not optimal. In fact cpu_suspend() path is needed
only when we put CPU power domain to off state where the CPU context is lost.
Update the code accordingly so that the expensive cpu_suspend() path
On Fri, Feb 08, 2013 at 08:41:46PM +0530, Santosh Shilimkar wrote:
Current CPU PM code code make use of common cpu_suspend() path for all the
CPU power states which is not optimal. In fact cpu_suspend() path is needed
only when we put CPU power domain to off state where the CPU context is lost.
On Friday 08 February 2013 08:56 PM, Felipe Balbi wrote:
On Fri, Feb 08, 2013 at 08:41:46PM +0530, Santosh Shilimkar wrote:
Current CPU PM code code make use of common cpu_suspend() path for all the
CPU power states which is not optimal. In fact cpu_suspend() path is needed
only when we put CPU
Santosh Shilimkar santosh.shilim...@ti.com writes:
Current CPU PM code code make use of common cpu_suspend() path for all the
CPU power states which is not optimal. In fact cpu_suspend() path is needed
only when we put CPU power domain to off state where the CPU context is lost.
Update the