From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Liam Girdwood (lrg@ti.com)" <lrg@ti.com>
Subject: Re: I2C controller vs. WM8903 suspend ordering
Date: Wed, 3 Aug 2011 08:46:23 +0900 [thread overview]
Message-ID: <20110802234622.GA30717@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF049EEAB155@HQMAIL01.nvidia.com>
On Tue, Aug 02, 2011 at 11:34:18AM -0700, Stephen Warren wrote:
> We've found that switching the Tegra I2C controller from struct
> platform_driver.{suspend,resume} to .{suspend,resume}_noirq solves this.
> However, this seems like it's more of an accident than registering an
> explicit dependency, especially since most I2C controllers just use
> suspend rather than suspend_noirq.
This is about as good as it gets, actually - I2C controllers should
generally suspend very late and resume early as they're needed for core
system components like the RTC and PMIC.
> Is there a way to explicitly indicate that sound should be suspended before
> the I2C controller? I assume the issue is more that snd_soc_suspend shuts
No, this is a general limitation in the Linux PM model. Everything goes
by the order that devices got registered in. There's nothing doing at
the minute without core work other than bodges like _noirq.
prev parent reply other threads:[~2011-08-03 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 18:34 I2C controller vs. WM8903 suspend ordering Stephen Warren
2011-08-02 21:22 ` Liam Girdwood
2011-08-02 23:46 ` Mark Brown [this message]
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=20110802234622.GA30717@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.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 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.