On 09/13/2012 09:28 AM, AnilKumar Ch wrote:
Move pm_runtime_enable/disable calls to c_can.c driver. Current
implementation is such that platform driver is doing pm_runtime
enable/disable and core driver is doing put_sync/get_sync.
PM runtime calls should be invoked if there is a valid device
Marc,
On Thu, Sep 13, 2012 at 13:18:07, Marc Kleine-Budde wrote:
On 09/13/2012 09:28 AM, AnilKumar Ch wrote:
Move pm_runtime_enable/disable calls to c_can.c driver. Current
implementation is such that platform driver is doing pm_runtime
enable/disable and core driver is doing
AnilKumar Ch anilku...@ti.com writes:
Move pm_runtime_enable/disable calls to c_can.c driver. Current
implementation is such that platform driver is doing pm_runtime
enable/disable and core driver is doing put_sync/get_sync.
PM runtime calls should be invoked if there is a valid device
On 09/13/2012 04:14 PM, Kevin Hilman wrote:
AnilKumar Ch anilku...@ti.com writes:
Move pm_runtime_enable/disable calls to c_can.c driver. Current
implementation is such that platform driver is doing pm_runtime
enable/disable and core driver is doing put_sync/get_sync.
PM runtime calls
Marc Kleine-Budde m...@pengutronix.de writes:
On 09/13/2012 04:14 PM, Kevin Hilman wrote:
AnilKumar Ch anilku...@ti.com writes:
Move pm_runtime_enable/disable calls to c_can.c driver. Current
implementation is such that platform driver is doing pm_runtime
enable/disable and core driver is