From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
dmaengine@vger.kernel.org, linux-pm@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] dmaengine: shdma: Move DMA stop to (runtime) suspend callbacks
Date: Thu, 26 Feb 2015 16:21:06 +0300 [thread overview]
Message-ID: <54EF1DC2.30703@cogentembedded.com> (raw)
In-Reply-To: <1424946394-6784-1-git-send-email-geert+renesas@glider.be>
Hello.
On 02/26/2015 01:26 PM, 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.
> To fix this, move the call to sh_dmae_ctl_stop(), which touches the
> DMAOR register, to the sh_dmae_suspend() and sh_dmae_runtime_suspend()
> callbacks. This makes PM operations more symmetric, as both
> sh_dmae_resume() and sh_dmae_runtime_resume() already call sh_dmae_rst()
> to re-initialize the DMAOR register.
> Remove sh_dmae_shutdown(), as it became empty.
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> This is v3 of "dmaengine: shdma: Runtime-resume device in .shutdown()"
> v3:
> - Move the call to sh_dmae_ctl_stop() to sh_dmae_suspend() and
> sh_dmae_runtime_suspend() instead of runtime-resuming the device in
> .shutdown(),
> v2:
> - Do nothing if we're runtime suspended.
> ---
> drivers/dma/sh/shdmac.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/dma/sh/shdmac.c b/drivers/dma/sh/shdmac.c
> index b2431aa300331270..9f1d4c7dbab83890 100644
> --- a/drivers/dma/sh/shdmac.c
> +++ b/drivers/dma/sh/shdmac.c
[...]
> @@ -929,13 +929,12 @@ static int sh_dmae_remove(struct platform_device *pdev)
> }
>
> static struct platform_driver sh_dmae_driver = {
> - .driver = {
> + .driver = {
Hm, don't understand what was changed on this line...
WBR, Sergei
next prev parent reply other threads:[~2015-02-26 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 10:26 [PATCH] dmaengine: shdma: Move DMA stop to (runtime) suspend callbacks Geert Uytterhoeven
2015-02-26 13:21 ` Sergei Shtylyov [this message]
2015-02-26 13:30 ` Geert Uytterhoeven
2015-03-02 11:56 ` Ulf Hansson
2015-03-02 16:41 ` 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=54EF1DC2.30703@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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 \
--cc=ulf.hansson@linaro.org \
--cc=vinod.koul@intel.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