Re: [PATCH 0/2] DMA: PL330: Clock and runtime cleanup

2012-09-17 Thread Vinod Koul
On Fri, 2012-09-07 at 12:14 +0530, Inderpal Singh wrote: > The controller clock is being managed at AMBA bus level probe/remove and > pm_runtime/suspend functions. The existing driver does the clock > enable/disable > again in the same code paths, which unneccessarily increments the usage count >

Re: [PATCH 0/2] DMA: PL330: Clock and runtime cleanup

2012-09-14 Thread Chander Kashyap
On 14 September 2012 08:45, Vinod Koul wrote: > On Fri, 2012-09-07 at 12:14 +0530, Inderpal Singh wrote: >> The controller clock is being managed at AMBA bus level probe/remove and >> pm_runtime/suspend functions. The existing driver does the clock >> enable/disable >> again in the same code path

Re: [PATCH 0/2] DMA: PL330: Clock and runtime cleanup

2012-09-13 Thread Vinod Koul
On Fri, 2012-09-07 at 12:14 +0530, Inderpal Singh wrote: > The controller clock is being managed at AMBA bus level probe/remove and > pm_runtime/suspend functions. The existing driver does the clock > enable/disable > again in the same code paths, which unneccessarily increments the usage count >

[PATCH 0/2] DMA: PL330: Clock and runtime cleanup

2012-09-06 Thread Inderpal Singh
The controller clock is being managed at AMBA bus level probe/remove and pm_runtime/suspend functions. The existing driver does the clock enable/disable again in the same code paths, which unneccessarily increments the usage count of the clock for the same device. The following patches remove the