All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v2] dmaengine: shdma: Runtime-resume device in .shutdown()
Date: Tue, 3 Feb 2015 18:08:35 -0800	[thread overview]
Message-ID: <20150204020835.GI4489@intel.com> (raw)
In-Reply-To: <CAPDyKFoxfJa2Wq=mA0Khx7B3E6MbY99BYyHtCAoff_7V+9rSaw@mail.gmail.com>

On Mon, Feb 02, 2015 at 10:35:10AM +0100, Ulf Hansson wrote:
> On 5 January 2015 at 11:46, Geert Uytterhoeven <geert+renesas@glider.be> 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, change the driver's .shutdown() callback:
> >   - If the device is runtime suspended, do nothing,
> >   - Else, explicitly runtime-resume the device, to avoid the device from
> >     being suspended while sh_dmae_ctl_stop() is being executed.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> > v2:
> >   - Do nothing if we're runtime suspended.
> > ---
> >  drivers/dma/sh/shdmac.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/dma/sh/shdmac.c b/drivers/dma/sh/shdmac.c
> > index aec8a84784a469d7..2de30e8e7d9290b9 100644
> > --- a/drivers/dma/sh/shdmac.c
> > +++ b/drivers/dma/sh/shdmac.c
> > @@ -585,7 +585,13 @@ 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);
> > +
> > +       if (pm_runtime_suspended(&pdev->dev))
> > +               return;
> > +
> > +       pm_runtime_get_sync(&pdev->dev);
> >         sh_dmae_ctl_stop(shdev);
> 
> I can't find that sh_dmae_ctl_stop() is invoked from the runtime PM
> suspend callback. That means the device will be "removed" differently,
> depending on it's runtime PM status (due to the upper check for
> pm_runtime_suspended() ) . Is that really what you want?
I think the patch description is the key. "During system reboot, the
sh-dma-engine device may be runtime-suspended, causing a crash"

The runtime-suspended device is already idle and has removed its clock.

-- 
~Vinod


WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH v2] dmaengine: shdma: Runtime-resume device in .shutdown()
Date: Wed, 04 Feb 2015 02:08:35 +0000	[thread overview]
Message-ID: <20150204020835.GI4489@intel.com> (raw)
In-Reply-To: <CAPDyKFoxfJa2Wq=mA0Khx7B3E6MbY99BYyHtCAoff_7V+9rSaw@mail.gmail.com>

On Mon, Feb 02, 2015 at 10:35:10AM +0100, Ulf Hansson wrote:
> On 5 January 2015 at 11:46, Geert Uytterhoeven <geert+renesas@glider.be> 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, change the driver's .shutdown() callback:
> >   - If the device is runtime suspended, do nothing,
> >   - Else, explicitly runtime-resume the device, to avoid the device from
> >     being suspended while sh_dmae_ctl_stop() is being executed.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> > v2:
> >   - Do nothing if we're runtime suspended.
> > ---
> >  drivers/dma/sh/shdmac.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/dma/sh/shdmac.c b/drivers/dma/sh/shdmac.c
> > index aec8a84784a469d7..2de30e8e7d9290b9 100644
> > --- a/drivers/dma/sh/shdmac.c
> > +++ b/drivers/dma/sh/shdmac.c
> > @@ -585,7 +585,13 @@ 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);
> > +
> > +       if (pm_runtime_suspended(&pdev->dev))
> > +               return;
> > +
> > +       pm_runtime_get_sync(&pdev->dev);
> >         sh_dmae_ctl_stop(shdev);
> 
> I can't find that sh_dmae_ctl_stop() is invoked from the runtime PM
> suspend callback. That means the device will be "removed" differently,
> depending on it's runtime PM status (due to the upper check for
> pm_runtime_suspended() ) . Is that really what you want?
I think the patch description is the key. "During system reboot, the
sh-dma-engine device may be runtime-suspended, causing a crash"

The runtime-suspended device is already idle and has removed its clock.

-- 
~Vinod


  reply	other threads:[~2015-02-04  2:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 10:46 [PATCH v2] dmaengine: shdma: Runtime-resume device in .shutdown() Geert Uytterhoeven
2015-01-05 10:46 ` Geert Uytterhoeven
2015-01-29 14:46 ` Geert Uytterhoeven
2015-01-29 14:46   ` Geert Uytterhoeven
2015-01-30  9:46 ` Krzysztof Kozlowski
2015-01-30  9:46   ` Krzysztof Kozlowski
2015-01-30 10:04   ` Geert Uytterhoeven
2015-01-30 10:04     ` Geert Uytterhoeven
2015-02-02  9:35 ` Ulf Hansson
2015-02-02  9:35   ` Ulf Hansson
2015-02-04  2:08   ` Vinod Koul [this message]
2015-02-04  2:08     ` Vinod Koul
2015-02-04  9:35     ` Ulf Hansson
2015-02-04  9:35       ` Ulf Hansson
2015-02-04  9:56       ` Geert Uytterhoeven
2015-02-04  9:56         ` Geert Uytterhoeven
2015-02-04 10:56         ` Ulf Hansson
2015-02-04 10:56           ` Ulf Hansson
2015-02-05 20:17         ` Vinod Koul
2015-02-05 20:17           ` 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=20150204020835.GI4489@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 \
    --cc=ulf.hansson@linaro.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 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.