linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 22 Sep 2015 08:46:18 +0100	[thread overview]
Message-ID: <20150922074618.GA11647@ck-lbox> (raw)
In-Reply-To: <20150921111642.112dc0c2@songinha-Samsung-DeskTop-System>

On Mon, Sep 21, 2015 at 11:16:42AM +0900, Inha Song wrote:
> Hi, Charles,
> 
> I've already tried to change.
> If I change to that, we can't enter the suspen during the playback.
> 
> -
> [   72.538263] arizona spi1.0: Suspend, disabling IRQ
> ...
> [   72.585823] arizona spi1.0: Late suspend, reengabling IRQ
> [   72.585904] arizona spi1.0: Early resume, disabling IRQ
> ...
> [   72.646770] PM: noirq suspend of devices failed
> 		<- because of "spi1.0" pm_wakeup_pending() in suspend_noirq()

Ok this looks more reasonable, suspend should fail because we do
have an IRQ waiting to be handled, so we shouldn't suspend. But
you are saying this happens every time the CODEC goes to suspend,
thus blocking the suspend from suspending?

First step then would be to identify what IRQ is occurring, could
you set LOG_DEVICE at the top of drivers/base/regmap/regmap.c to
"spi1.0" and provide a log, so we can see what IRQ is being
asserted from the CODEC.

Thanks,
Charles


  reply	other threads:[~2015-09-22  8:10 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 [this message]
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
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=20150922074618.GA11647@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).