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
Subject: Re: [alsa-devel] [PATCH] mfd: arizona: Call the runtime PM function if the state is runtime resumed
Date: Thu, 17 Sep 2015 09:25:42 +0100 [thread overview]
Message-ID: <20150917082542.GB7694@ck-lbox> (raw)
In-Reply-To: <1442478527-29304-1-git-send-email-ideal.song@samsung.com>
On Thu, Sep 17, 2015 at 05:28:47PM +0900, Inha Song wrote:
> This patch call runtiem PM function manually if the state is runtime resumed
> before enter suspend.
>
> This case has occurred when wake-up by the resume after entering to
> suspend during the playback.
> $ aplay -> runtime_resume() -> suspend() -> resume()
>
> In this case, Can occurred an error when enter suspend.
> --
> [ 82.559234] PM: suspend of devices complete after 57.252 msecs
> [ 82.567978] arizona spi1.0: Failed to read IRQ status: -108
> [ 82.567989] arizona spi1.0: Failed to read main IRQ status: -108
> [ 82.568027] arizona spi1.0: Failed to read IRQ status: -108
> [ 82.568036] arizona spi1.0: Failed to read main IRQ status: -108
Would it be possible to get some more detail on what is happening
here? A full log would be nice with DEBUG enabled in
arizona-core.c, also perhaps put some printk's in the SPI driver
suspend/resume as well.
It looks like what is happening is that the system is attempting
to handle an IRQ before the SPI has been resumed. But that is
exactly what the irq enables/disables in the system PM ops in
Arizona are trying to avoid.
> ....
> So, we should call runtime_suspend() manually when enter suspend
> if the state is runtime resume.
There are many use-cases where we want to leave the CODEC enabled
whilst the system is suspended so we really don't want to be
doing a runtime suspend with every system suspend.
Thanks,
Charles
next prev parent reply other threads:[~2015-09-17 8:25 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 [this message]
2015-09-17 9:05 ` Inha Song
2015-09-17 9:16 ` Charles Keepax
2015-09-18 6:49 ` [alsa-devel] " Inha Song
2015-09-18 8:24 ` Charles Keepax
2015-09-21 2:16 ` [alsa-devel] " Inha Song
2015-09-22 7:46 ` Charles Keepax
2015-09-23 2:04 ` [alsa-devel] " Inha Song
2015-09-23 14:43 ` Charles Keepax
2015-09-24 1:38 ` Inha Song
2015-09-24 7:41 ` Charles Keepax
2015-09-25 7:51 ` [alsa-devel] " 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=20150917082542.GB7694@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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).