Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-21 Thread Jisheng Zhang
On Thu, 21 Apr 2016 10:48:56 +0300 Jarkko Nikula wrote: > Hi > > On 04/21/2016 06:08 AM, Jisheng Zhang wrote: > > Dear Jarkko, > > > > On Wed, 20 Apr 2016 16:53:08 +0300 Jarkko Nikula wrote: > > > >> On 04/14/2016 03:53 PM, Jisheng Zhang wrote: > >>> When

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-21 Thread Jisheng Zhang
On Thu, 21 Apr 2016 10:48:56 +0300 Jarkko Nikula wrote: > Hi > > On 04/21/2016 06:08 AM, Jisheng Zhang wrote: > > Dear Jarkko, > > > > On Wed, 20 Apr 2016 16:53:08 +0300 Jarkko Nikula wrote: > > > >> On 04/14/2016 03:53 PM, Jisheng Zhang wrote: > >>> When pm_runtime_enable() was being

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-21 Thread Jarkko Nikula
Hi On 04/21/2016 06:08 AM, Jisheng Zhang wrote: Dear Jarkko, On Wed, 20 Apr 2016 16:53:08 +0300 Jarkko Nikula wrote: On 04/14/2016 03:53 PM, Jisheng Zhang wrote: When pm_runtime_enable() was being called, the device's usage counter was 0, causing the PM layer to runtime-suspend the device.

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-21 Thread Jarkko Nikula
Hi On 04/21/2016 06:08 AM, Jisheng Zhang wrote: Dear Jarkko, On Wed, 20 Apr 2016 16:53:08 +0300 Jarkko Nikula wrote: On 04/14/2016 03:53 PM, Jisheng Zhang wrote: When pm_runtime_enable() was being called, the device's usage counter was 0, causing the PM layer to runtime-suspend the device.

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-20 Thread Jisheng Zhang
Dear Jarkko, On Wed, 20 Apr 2016 16:53:08 +0300 Jarkko Nikula wrote: > On 04/14/2016 03:53 PM, Jisheng Zhang wrote: > > When pm_runtime_enable() was being called, the device's usage counter > > was 0, causing the PM layer to runtime-suspend the device. We then > > went on to call i2c_dw_probe()

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-20 Thread Jisheng Zhang
Dear Jarkko, On Wed, 20 Apr 2016 16:53:08 +0300 Jarkko Nikula wrote: > On 04/14/2016 03:53 PM, Jisheng Zhang wrote: > > When pm_runtime_enable() was being called, the device's usage counter > > was 0, causing the PM layer to runtime-suspend the device. We then > > went on to call i2c_dw_probe()

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-20 Thread Jarkko Nikula
On 04/14/2016 03:53 PM, Jisheng Zhang wrote: When pm_runtime_enable() was being called, the device's usage counter was 0, causing the PM layer to runtime-suspend the device. We then went on to call i2c_dw_probe() on a suspended device, which could hung. Fix this by incrementing the usage

Re: [PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-20 Thread Jarkko Nikula
On 04/14/2016 03:53 PM, Jisheng Zhang wrote: When pm_runtime_enable() was being called, the device's usage counter was 0, causing the PM layer to runtime-suspend the device. We then went on to call i2c_dw_probe() on a suspended device, which could hung. Fix this by incrementing the usage

[PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-14 Thread Jisheng Zhang
When pm_runtime_enable() was being called, the device's usage counter was 0, causing the PM layer to runtime-suspend the device. We then went on to call i2c_dw_probe() on a suspended device, which could hung. Fix this by incrementing the usage counter before pm_runtime_enable(). Signed-off-by:

[PATCH 1/4] i2c: designware-platdrv: Fix runtime PM initialization

2016-04-14 Thread Jisheng Zhang
When pm_runtime_enable() was being called, the device's usage counter was 0, causing the PM layer to runtime-suspend the device. We then went on to call i2c_dw_probe() on a suspended device, which could hung. Fix this by incrementing the usage counter before pm_runtime_enable(). Signed-off-by: