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,
laurent.pinchart+renesas@ideasonboard.com
Subject: Re: [PATCH] [PATCH v2] sh_eth: ensure pm_runtime cannot suspend the device during init
Date: Thu, 20 Mar 2014 11:55:29 +0000 [thread overview]
Message-ID: <1651225.dIHP4GJALN@avalon> (raw)
In-Reply-To: <1395308007-13956-1-git-send-email-ben.dooks@codethink.co.uk>
Hi Ben,
Thank you for the patch.
On Thursday 20 March 2014 10:33:27 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.
>
> 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.
>
> 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>
>
> ---
> 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.
> ---
> drivers/net/ethernet/renesas/sh_eth.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/renesas/sh_eth.c
> b/drivers/net/ethernet/renesas/sh_eth.c index 4f76b5e..955e422 100644
> --- a/drivers/net/ethernet/renesas/sh_eth.c
> +++ b/drivers/net/ethernet/renesas/sh_eth.c
> @@ -2869,7 +2869,7 @@ 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);
> + pm_runtime_get_sync(&pdev->dev);
>
> if (pdev->dev.of_node)
> pd = sh_eth_parse_dt(&pdev->dev);
> @@ -2961,6 +2961,7 @@ static int sh_eth_drv_probe(struct platform_device
> *pdev) pr_info("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;
Don't you also need a pm_runtime_put() call in the error path at the end of
the probe function ? I've had a quick look at the device core and there
doesn't seem to be any automatic runtime PM cleanup performed when probe fails
(I might have missed it though, so please double-check).
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
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,
laurent.pinchart+renesas@ideasonboard.com
Subject: Re: [PATCH] [PATCH v2] sh_eth: ensure pm_runtime cannot suspend the device during init
Date: Thu, 20 Mar 2014 12:55:29 +0100 [thread overview]
Message-ID: <1651225.dIHP4GJALN@avalon> (raw)
In-Reply-To: <1395308007-13956-1-git-send-email-ben.dooks@codethink.co.uk>
Hi Ben,
Thank you for the patch.
On Thursday 20 March 2014 10:33:27 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.
>
> 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.
>
> 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>
>
> ---
> 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.
> ---
> drivers/net/ethernet/renesas/sh_eth.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/renesas/sh_eth.c
> b/drivers/net/ethernet/renesas/sh_eth.c index 4f76b5e..955e422 100644
> --- a/drivers/net/ethernet/renesas/sh_eth.c
> +++ b/drivers/net/ethernet/renesas/sh_eth.c
> @@ -2869,7 +2869,7 @@ 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);
> + pm_runtime_get_sync(&pdev->dev);
>
> if (pdev->dev.of_node)
> pd = sh_eth_parse_dt(&pdev->dev);
> @@ -2961,6 +2961,7 @@ static int sh_eth_drv_probe(struct platform_device
> *pdev) pr_info("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;
Don't you also need a pm_runtime_put() call in the error path at the end of
the probe function ? I've had a quick look at the device core and there
doesn't seem to be any automatic runtime PM cleanup performed when probe fails
(I might have missed it though, so please double-check).
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-03-20 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 9:33 [PATCH] [PATCH v2] sh_eth: ensure pm_runtime cannot suspend the device during init Ben Dooks
2014-03-20 9:33 ` Ben Dooks
2014-03-20 11:55 ` Laurent Pinchart [this message]
2014-03-20 11:55 ` Laurent Pinchart
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=1651225.dIHP4GJALN@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.