From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk, netdev@vger.kernel.org,
linux-sh@vger.kernel.org, davem@davemloft.net,
sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH v5] sh_eth: ensure pm_runtime cannot suspend the device during init
Date: Fri, 21 Mar 2014 12:59:11 +0000 [thread overview]
Message-ID: <1903013.f9Vl0xMAyg@avalon> (raw)
In-Reply-To: <1395400154-25710-1-git-send-email-ben.dooks@codethink.co.uk>
Hi Ben,
Thank you for the patch.
On Friday 21 March 2014 12:09:14 Ben Dooks wrote:
> The pm_rumtime work queue is causing the device to be suspended during
> initialisation, thus the initialisation may not be able to access registers
> properly. As the code is called from a work queue, it is possible that this
> is not seen from certain configurations/builds due to the asynchronos
> nature of the code.
>
> Another issue has also been found where the network device registration
> calls back into the driver thus causing further pm_runtime calls that
> also caused issues with the MDIO bus code. This has now been checked
> and is the only place the MDIO can be called without the device open.
>
> Use pm_runtime_get_sync() and pm_runtime_put() to ensure that the
> pm system does not suspend it during the probe() call and remove the
> now unnecessary pm_runtime_resume() call. Also add a call in the error
> path to call pm_runtime_disable().
>
> This fixes the external abort that can cause /sbin/init or other such
> init processed to die.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> ---
> Cc: sergei.shtylyov@cogentembedded.com
> Cc: laurent.pinchart+renesas@ideasonboard.com
> cc: netdev@vger.kernel.org
>
> Note, Laurent this should probably be applied before your
> current series as it may require changes to the exit sequence.
>
> Fixes from v1:
> - use pm_runtime_put() over pm_runtime_put_sync() as
> we do not need to guaranteed the device has powered
> off after probe.
>
> Fixed from v2:
> - call pm_runtime_put() in error path
>
> Fixed from v3:
> - call pm_runtime_disable() in error path
>
> Conflicts:
> drivers/net/ethernet/renesas/sh_eth.c
> ---
> drivers/net/ethernet/renesas/sh_eth.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/renesas/sh_eth.c
> b/drivers/net/ethernet/renesas/sh_eth.c index e4bff18..6a9509c 100644
> --- a/drivers/net/ethernet/renesas/sh_eth.c
> +++ b/drivers/net/ethernet/renesas/sh_eth.c
> @@ -2772,6 +2772,9 @@ static int sh_eth_drv_probe(struct platform_device
> *pdev) if (!ndev)
> return -ENOMEM;
>
> + pm_runtime_enable(&pdev->dev);
> + pm_runtime_get_sync(&pdev->dev);
> +
> /* The sh Ether-specific entries in the device structure. */
> ndev->base_addr = res->start;
> devno = pdev->id;
> @@ -2799,8 +2802,6 @@ static int sh_eth_drv_probe(struct platform_device
> *pdev)
>
> spin_lock_init(&mdp->lock);
> mdp->pdev = pdev;
> - pm_runtime_enable(&pdev->dev);
> - pm_runtime_resume(&pdev->dev);
>
> if (pdev->dev.of_node)
> pd = sh_eth_parse_dt(&pdev->dev);
> @@ -2898,6 +2899,7 @@ static int sh_eth_drv_probe(struct platform_device
> *pdev) netdev_info(ndev, "Base address at 0x%x, %pM, IRQ %d.\n",
> (u32)ndev->base_addr, ndev->dev_addr, ndev->irq);
>
> + pm_runtime_put(&pdev->dev);
> platform_set_drvdata(pdev, ndev);
>
> return ret;
> @@ -2911,6 +2913,8 @@ out_release:
> if (ndev)
> free_netdev(ndev);
>
> + pm_runtime_put(&pdev->dev);
> + pm_runtime_disable(&pdev->dev);
> return ret;
> }
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-03-21 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:09 [PATCH v5] sh_eth: ensure pm_runtime cannot suspend the device during init Ben Dooks
2014-03-21 12:14 ` Geert Uytterhoeven
2014-03-21 12:59 ` Laurent Pinchart [this message]
2014-03-28 18:26 ` David Miller
2014-03-28 19:25 ` Ben Dooks
2014-03-28 20:00 ` David Miller
2014-03-28 20:10 ` Sergei Shtylyov
2014-03-28 21:18 ` David Miller
2014-03-29 13:52 ` Sergei Shtylyov
2014-03-29 19:39 ` 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=1903013.f9Vl0xMAyg@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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).