Re: [PATCH] i2c: i2c-qcom-geni: Fix suspend clock handling

2018-07-31 Thread Wolfram Sang
On Mon, Jul 09, 2018 at 04:49:37PM -0700, Evan Green wrote: > pm_runtime_suspended can return 0 even if the last runtime power > management function called in the device was a suspend call. This > trips up the i2c-qcom-geni's suspend_noirq accounting, which was > trying to use the function to deter

Re: [PATCH] i2c: i2c-qcom-geni: Fix suspend clock handling

2018-07-13 Thread Evan Green
On Fri, Jul 13, 2018 at 3:21 PM Karthik Ramasubramanian wrote: > > > > On 7/9/2018 5:49 PM, Evan Green wrote: > > pm_runtime_suspended can return 0 even if the last runtime power > > management function called in the device was a suspend call. This > > trips up the i2c-qcom-geni's suspend_noirq ac

Re: [PATCH] i2c: i2c-qcom-geni: Fix suspend clock handling

2018-07-13 Thread Karthik Ramasubramanian
On 7/9/2018 5:49 PM, Evan Green wrote: > pm_runtime_suspended can return 0 even if the last runtime power > management function called in the device was a suspend call. This > trips up the i2c-qcom-geni's suspend_noirq accounting, which was > trying to use the function to determine if it should

Re: [PATCH] i2c: i2c-qcom-geni: Fix suspend clock handling

2018-07-12 Thread Wolfram Sang
On Mon, Jul 09, 2018 at 04:49:37PM -0700, Evan Green wrote: > pm_runtime_suspended can return 0 even if the last runtime power > management function called in the device was a suspend call. This > trips up the i2c-qcom-geni's suspend_noirq accounting, which was > trying to use the function to deter

[PATCH] i2c: i2c-qcom-geni: Fix suspend clock handling

2018-07-09 Thread Evan Green
pm_runtime_suspended can return 0 even if the last runtime power management function called in the device was a suspend call. This trips up the i2c-qcom-geni's suspend_noirq accounting, which was trying to use the function to determine if it should disable clocks or if that had already been done.