From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Inha Song <ideal.song@samsung.com>
Cc: <lee.jones@linaro.org>, <broonie@kernel.org>,
<linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<patches@opensource.wolfsonmicro.com>, <sameo@linux.intel.com>,
<cw00.choi@samsung.com>
Subject: Re: [alsa-devel] [PATCH] mfd: arizona: Call the runtime PM function if the state is runtime resumed
Date: Thu, 24 Sep 2015 08:41:07 +0100 [thread overview]
Message-ID: <20150924074107.GC5432@ck-lbox> (raw)
In-Reply-To: <20150924103809.7be235d1@songinha-Samsung-DeskTop-System>
On Thu, Sep 24, 2015 at 10:38:09AM +0900, Inha Song wrote:
> Hi, Charles,
>
> On Wed, 23 Sep 2015 15:43:12 +0100
> Charles Keepax <ckeepax@opensource.wolfsonmicro.com> wrote:
>
> > On Wed, Sep 23, 2015 at 11:04:04AM +0900, Inha Song wrote:
> > > Hi, Charles,
> > >
> > > I saw the log with LOG_DEVICE in regmap. But, I'm not sure the reason that suspend noirq failed is IRQ occuring.
> > >
> > > Here is my log:
> > > --
> > > root@localhost:~# aplay test.wav
> > > [ 41.049072] s3c64xx_spi_runtime_suspend
> > > [ 41.056043] arizona spi1.0: ASRC underclocked
> > > ....
> > > [ 72.308238] arizona spi1.0: Suspend, disabling IRQ
> > > [ 72.320286] arizona spi1.0: 400 <= 0
> > > [ 72.320310] s3c64xx_spi_runtime_resume
> > > [ 72.336047] arizona spi1.0: 51a <= 0
> > > [ 72.336217] arizona spi1.0: 101 <= 8604
> > > [ 72.336401] arizona spi1.0: 171 <= 3
> > > [ 72.336425] arizona spi1.0: 171 <= 2
> > > [ 72.336731] arizona spi1.0: 171 <= 0
> > > [ 72.336751] arizona spi1.0: SYSCLK cleared
> > > [ 72.338584] arizona spi1.0: SYSCLK cleared
> >
> > This bit looks likely related to your problem, it looks like the
> > FLL is being turned off. My guess here would be that you haven't
> > called snd_soc_dapm_ignore_suspend from your machine driver, you
> > need to call this for all end points that may want to stay
> > powered up during system suspend and also set the ignore_suspend
> > flag on any DAI links you want to remain active during system
> > suspend.
>
> But, We should call the trigger callback with SNDRV_PCM_TRIGGER_SUSPEND and *_RESUME command
> for support senarios what suspend during the playback and resume.
> So, I can't set the "ignore_suspend" in playback DAI.
>
> For this reason, I would have called the runtime_suspend manually in arizona-core when suspend.
>
> Best Reagrds,
> Inha Song.
>
Ah ok so you want the audio to stop during suspend?
Ok in that case can we get a bit more of log, your log finished
up here:
[ 72.308238] arizona spi1.0: Suspend, disabling IRQ
[ 72.320286] arizona spi1.0: 400 <= 0
[ 72.320310] s3c64xx_spi_runtime_resume
[ 72.336047] arizona spi1.0: 51a <= 0
[ 72.336217] arizona spi1.0: 101 <= 8604
[ 72.336401] arizona spi1.0: 171 <= 3
[ 72.336425] arizona spi1.0: 171 <= 2
[ 72.336731] arizona spi1.0: 171 <= 0
[ 72.336751] arizona spi1.0: SYSCLK cleared
[ 72.338584] arizona spi1.0: SYSCLK cleared
[ 72.339123] s3c64xx_spi_suspend
[ 72.355866] arizona spi1.0: Late suspend, reenabling IRQ
[ 72.355893] >>> noirq failed because of spi1
[ 72.355948] arizona spi1.0: Early resume, disabling IRQ
[ 72.416798] PM: noirq suspend of devices failed
Which finished too early as we can't see which IRQ it was that
triggered the wakeup.
Thanks,
Charles
next prev parent reply other threads:[~2015-09-24 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 8:28 [alsa-devel] [PATCH] mfd: arizona: Call the runtime PM function if the state is runtime resumed Inha Song
2015-09-17 8:25 ` Charles Keepax
2015-09-17 9:05 ` Inha Song
2015-09-17 9:16 ` Charles Keepax
2015-09-18 6:49 ` Inha Song
2015-09-18 8:24 ` Charles Keepax
2015-09-21 2:16 ` Inha Song
2015-09-22 7:46 ` Charles Keepax
2015-09-23 2:04 ` Inha Song
2015-09-23 14:43 ` Charles Keepax
2015-09-24 1:38 ` Inha Song
2015-09-24 7:41 ` Charles Keepax [this message]
2015-09-25 7:51 ` Inha Song
2015-09-27 16:06 ` Charles Keepax
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=20150924074107.GC5432@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=ideal.song@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.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;
as well as URLs for NNTP newsgroup(s).