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
of
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
of
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
