In the fail1~fail5 failure path, pm_runtime_disable() should
be called to avoid 'Unbalanced pm_runtime_enable' error in
next probe() which may be triggered by defer probe or next
'modprobe musb_hdrc'.
Cc: Sebastian Andrzej Siewior
Cc: Felipe Balbi
Cc: v3.8
Signed-off-by: Ming Lei
---
drivers/
Hi,
On Wed, Nov 28, 2012 at 08:34:25AM +0800, Ming Lei wrote:
> On Wed, Nov 28, 2012 at 1:23 AM, Greg Kroah-Hartman
> wrote:
> > On Tue, Nov 27, 2012 at 11:48:41AM +0800, Ming Lei wrote:
> >> Hi,
> >>
> >> On Thu, Nov 22, 2012 at 10:35 AM, Ming Lei wrote:
> >> > In the fail1~fail5 failure path,
On Wed, Nov 28, 2012 at 1:23 AM, Greg Kroah-Hartman
wrote:
> On Tue, Nov 27, 2012 at 11:48:41AM +0800, Ming Lei wrote:
>> Hi,
>>
>> On Thu, Nov 22, 2012 at 10:35 AM, Ming Lei wrote:
>> > In the fail1~fail5 failure path, pm_runtime_disable() should
>> > be called to avoid 'Unbalanced pm_runtime_en
On Tue, Nov 27, 2012 at 11:48:41AM +0800, Ming Lei wrote:
> Hi,
>
> On Thu, Nov 22, 2012 at 10:35 AM, Ming Lei wrote:
> > In the fail1~fail5 failure path, pm_runtime_disable() should
> > be called to avoid 'Unbalanced pm_runtime_enable' error in
> > next probe() which may be triggered by defer pr
Hi,
On Thu, Nov 22, 2012 at 10:35 AM, Ming Lei wrote:
> In the fail1~fail5 failure path, pm_runtime_disable() should
> be called to avoid 'Unbalanced pm_runtime_enable' error in
> next probe() which may be triggered by defer probe or next
> 'modprobe musb_hdrc'.
Greg/Felipe, could you queue the
In the fail1~fail5 failure path, pm_runtime_disable() should
be called to avoid 'Unbalanced pm_runtime_enable' error in
next probe() which may be triggered by defer probe or next
'modprobe musb_hdrc'.
Cc: Sebastian Andrzej Siewior
Cc: Felipe Balbi
Signed-off-by: Ming Lei
---
drivers/usb/musb/m