From: Vinod Koul <vinod.koul@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-pm@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] dmaengine: shdma: Runtime-resume device in .shutdown()
Date: Fri, 5 Dec 2014 23:17:54 +0530 [thread overview]
Message-ID: <20141205174754.GV3411@intel.com> (raw)
In-Reply-To: <1416410146-29652-1-git-send-email-geert+renesas@glider.be>
On Wed, Nov 19, 2014 at 04:15:46PM +0100, Geert Uytterhoeven wrote:
> During system reboot, the sh-dma-engine device may be runtime-suspended,
> causing a crash:
>
> Unhandled fault: imprecise external abort (0x1406) at 0x0002c02c
> Internal error: : 1406 [#1] SMP ARM
> ...
> PC is at sh_dmae_ctl_stop+0x28/0x64
> LR is at sh_dmae_ctl_stop+0x24/0x64
>
> If the sh-dma-engine is runtime-suspended, its module clock is turned
> off, and its registers cannot be accessed. Runtime-resume the device in
> the driver's .shutdown() callback to fix this.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/dma/sh/shdmac.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/dma/sh/shdmac.c b/drivers/dma/sh/shdmac.c
> index b65317c6ea4e722c..a13c6ba7468f12a6 100644
> --- a/drivers/dma/sh/shdmac.c
> +++ b/drivers/dma/sh/shdmac.c
> @@ -585,7 +585,10 @@ static void sh_dmae_chan_remove(struct sh_dmae_device *shdev)
> static void sh_dmae_shutdown(struct platform_device *pdev)
> {
> struct sh_dmae_device *shdev = platform_get_drvdata(pdev);
> +
> + pm_runtime_get_sync(&pdev->dev);
> sh_dmae_ctl_stop(shdev);
> + pm_runtime_put(&pdev->dev);
but if you are runtime_suspended, then why should you even proceed to stop
the clock. Why not just cleanup and return when runtime suspended
--
~Vinod
next prev parent reply other threads:[~2014-12-05 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 15:15 [PATCH] dmaengine: shdma: Runtime-resume device in .shutdown() Geert Uytterhoeven
2014-12-05 17:47 ` Vinod Koul [this message]
2014-12-07 10:35 ` Geert Uytterhoeven
2014-12-07 11:53 ` Vinod Koul
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=20141205174754.GV3411@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/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).