From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Taylor Hutt <thutt@google.com>
Cc: alsa-devel@alsa-project.org, Dylan Reid <dgreid@google.com>
Subject: Re: Should codec suspend when no paths are marked to be active across a suspend action?
Date: Fri, 7 Sep 2012 07:56:07 +0800 [thread overview]
Message-ID: <20120906235606.GC4400@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAFM_0b8xAuth0DGzNTMRpBy1VZ5vUJKPNEo2gRO+5Z7G+2CAUQ@mail.gmail.com>
On Thu, Sep 06, 2012 at 12:55:00PM -0700, Taylor Hutt wrote:
> Shouldn't the codec be suspended if there are no paths set to remain
> active across the suspend?
Yes. If you're using an analogue bypass path there's a very recent
commit in -next from me which should help, previously we weren't ever
really suspending bypass paths at all (even before the changes to keep
some paths active) though we might end up doing so by accident. Nobody
noticed since essentially nobody uses analogue bypass any more.
parent reply other threads:[~2012-09-06 23:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAFM_0b8xAuth0DGzNTMRpBy1VZ5vUJKPNEo2gRO+5Z7G+2CAUQ@mail.gmail.com>]
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=20120906235606.GC4400@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dgreid@google.com \
--cc=thutt@google.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).