From: Lucas Stach l.st...@pengutronix.de
Date: Mon, 3 Aug 2015 17:50:11 +0200
The clocks are initially active and thus the device is marked active.
This still keeps the PM refcount at 0, the pm_runtime_put_autosuspend()
call at the end of probe then leaves us with an invalid refcount of -1,
On Tue, 4 Aug 2015, Lucas Stach wrote:
Am Montag, den 03.08.2015, 14:28 -0400 schrieb Alan Stern:
On Mon, 3 Aug 2015, Uwe [iso-8859-1] Kleine-Knig wrote:
Hello,
I have no clue about runtime-pm, but I added a few people to Cc: who
should know better ...
Best regards
Am Montag, den 03.08.2015, 14:28 -0400 schrieb Alan Stern:
On Mon, 3 Aug 2015, Uwe [iso-8859-1] Kleine-Knig wrote:
Hello,
I have no clue about runtime-pm, but I added a few people to Cc: who
should know better ...
Best regards
Uwe
On Mon, Aug 03, 2015 at 06:15:54PM +0200,
Am Montag, den 03.08.2015, 18:15 +0200 schrieb Andrew Lunn:
On Mon, Aug 03, 2015 at 05:50:11PM +0200, Lucas Stach wrote:
The clocks are initially active and thus the device is marked active.
This still keeps the PM refcount at 0, the pm_runtime_put_autosuspend()
call at the end of probe
Hello,
On Tue, Aug 04, 2015 at 10:20:55AM -0400, Alan Stern wrote:
In that case, adding a call pm_runtime_get_noresume() is the right
thing to do.
Is this an ack for Lucas' patch?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König|
Industrial Linux
Hello Lucas,
On Mon, Aug 03, 2015 at 05:50:11PM +0200, Lucas Stach wrote:
The clocks are initially active and thus the device is marked active.
This still keeps the PM refcount at 0, the pm_runtime_put_autosuspend()
call at the end of probe then leaves us with an invalid refcount of -1,
which
On Tue, 4 Aug 2015, Uwe [iso-8859-1] Kleine-K�nig wrote:
Hello,
On Tue, Aug 04, 2015 at 10:20:55AM -0400, Alan Stern wrote:
In that case, adding a call pm_runtime_get_noresume() is the right
thing to do.
Is this an ack for Lucas' patch?
Yes:
Acked-by: Alan Stern
The clocks are initially active and thus the device is marked active.
This still keeps the PM refcount at 0, the pm_runtime_put_autosuspend()
call at the end of probe then leaves us with an invalid refcount of -1,
which in turn leads to the device staying in suspended state even though
netdev open
On Mon, Aug 03, 2015 at 05:50:11PM +0200, Lucas Stach wrote:
The clocks are initially active and thus the device is marked active.
This still keeps the PM refcount at 0, the pm_runtime_put_autosuspend()
call at the end of probe then leaves us with an invalid refcount of -1,
which in turn leads
From: Lucas Stach l.st...@pengutronix.de
Date: Mon, 3 Aug 2015 17:50:11 +0200
The clocks are initially active and thus the device is marked active.
This still keeps the PM refcount at 0, the pm_runtime_put_autosuspend()
call at the end of probe then leaves us with an invalid refcount of -1,
On Mon, 3 Aug 2015, Uwe [iso-8859-1] Kleine-K�nig wrote:
Hello,
I have no clue about runtime-pm, but I added a few people to Cc: who
should know better ...
Best regards
Uwe
On Mon, Aug 03, 2015 at 06:15:54PM +0200, Andrew Lunn wrote:
On Mon, Aug 03, 2015 at 05:50:11PM +0200, Lucas
Hello,
I have no clue about runtime-pm, but I added a few people to Cc: who
should know better ...
Best regards
Uwe
On Mon, Aug 03, 2015 at 06:15:54PM +0200, Andrew Lunn wrote:
On Mon, Aug 03, 2015 at 05:50:11PM +0200, Lucas Stach wrote:
The clocks are initially active and thus the device is
12 matches
Mail list logo
