From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Shiraz Hashim <shiraz.hashim@st.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"spear--sw-devel@lists.codex.cro.st.com"
<spear--sw-devel@lists.codex.cro.st.com>,
Armando VISCONTI <armando.visconti@st.com>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: Not able to restart audio after hibernation
Date: Sun, 8 Jan 2012 21:53:58 -0800 [thread overview]
Message-ID: <20120109055357.GL29065@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120109031645.GA21422@localhost.localdomain>
On Mon, Jan 09, 2012 at 08:46:45AM +0530, Shiraz Hashim wrote:
> On Sat, Jan 07, 2012 at 02:32:05AM +0800, Mark Brown wrote:
> > This suggests that you have a bug in your suspend and resume
> > implementation, possibly outside of this driver.
> The driver works absolutely fine in case of suspend to ram where the
> power domains (which includes the I2S controller) is switched off.
That doesn't mean everything is OK, for example the clock tree or DMA
controller might not be preserving state properly.
> As the soc-core.c misses hibernation call backs of dev_pm_ops, we were
> wondering whether it has been tested before on some other platform.
Not to my knowledge, but I don't see any reason why anything more than
the trivial implementation should really be needed except for the
general pointlessness of resuming after hibernating.
prev parent reply other threads:[~2012-01-09 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 10:47 Not able to restart audio after hibernation Rajeev kumar
2012-01-06 18:32 ` Mark Brown
2012-01-06 20:54 ` Tobin Davis
2012-01-06 23:25 ` Mark Brown
[not found] ` <20120109031645.GA21422@localhost.localdomain>
2012-01-09 5:53 ` 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=20120109055357.GL29065@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=armando.visconti@st.com \
--cc=lrg@ti.com \
--cc=rajeev-dlh.kumar@st.com \
--cc=shiraz.hashim@st.com \
--cc=spear--sw-devel@lists.codex.cro.st.com \
--cc=tiwai@suse.de \
/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.