netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Andrew Lunn" <andrew@lunn.ch>,
	netdev@vger.kernel.org, patchwork-lst@pengutronix.de,
	"David S. Miller" <davem@davemloft.net>,
	kernel@pengutronix.de, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Len Brown" <len.brown@intel.com>, "Pavel Machek" <pavel@ucw.cz>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] net: fec: fix initial runtime PM refcount
Date: Tue, 04 Aug 2015 09:43:36 +0200	[thread overview]
Message-ID: <1438674216.2458.24.camel@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1508031416250.1667-100000@iolanthe.rowland.org>

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, 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 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 had been called.
> > > > 
> > > > Fix this by initializing the refcount to be coherent with the initial
> > > > device status.
> > > > 
> > > > Fixes:
> > > > 8fff755e9f8 (net: fec: Ensure clocks are enabled while using mdio bus)
> > > > 
> > > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > > > ---
> > > > Please apply this as a fix for 4.2
> > > > ---
> > > >  drivers/net/ethernet/freescale/fec_main.c | 1 +
> > > >  1 file changed, 1 insertion(+)
> > > > 
> > > > diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> > > > index 32e3807c650e..271bb5862346 100644
> > > > --- a/drivers/net/ethernet/freescale/fec_main.c
> > > > +++ b/drivers/net/ethernet/freescale/fec_main.c
> > > > @@ -3433,6 +3433,7 @@ fec_probe(struct platform_device *pdev)
> > > >  
> > > >  	pm_runtime_set_autosuspend_delay(&pdev->dev, FEC_MDIO_PM_TIMEOUT);
> > > >  	pm_runtime_use_autosuspend(&pdev->dev);
> > > > +	pm_runtime_get_noresume(&pdev->dev);
> > > >  	pm_runtime_set_active(&pdev->dev);
> > > >  	pm_runtime_enable(&pdev->dev);
> > > 
> > > This might work, but is it the correct fix?
> 
> It looks reasonable to me.  It might also make sense to move all of
> that pm_runtime_* stuff to the end of the probe routine.  Notice that
> they don't get undone if register_netdev() fails.
> 
Unfortunately we can not move RPM enabling to the end of probe, as the
MDIO read/write functions that rely on RPM are already called while we
are still in the middle of the probe function.

I agree that we need better error handling here, but that comment
applies to the whole FEC probe function. I think that this might be
invasive enough to justify a delay to the next merge window, not really
material for the late RCs.

Regards,
Lucas

-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |

  reply	other threads:[~2015-08-04  7:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 15:50 [PATCH] net: fec: fix initial runtime PM refcount Lucas Stach
2015-08-03 16:15 ` Andrew Lunn
2015-08-03 18:05   ` Uwe Kleine-König
2015-08-03 18:28     ` Alan Stern
2015-08-04  7:43       ` Lucas Stach [this message]
2015-08-04 14:20         ` Alan Stern
2015-08-04 14:35           ` Uwe Kleine-König
2015-08-04 15:59             ` Alan Stern
2015-08-04  7:34   ` Lucas Stach
2015-08-04  5:23 ` David Miller
2015-08-04  8:11 ` Uwe Kleine-König
2015-08-05  8:49 ` [PATCH net-master v2] " Uwe Kleine-König
2015-08-07  1:54 ` [PATCH] " David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1438674216.2458.24.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=patchwork-lst@pengutronix.de \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=stern@rowland.harvard.edu \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).