From: David Henningsson <david.henningsson@canonical.com>
To: alsa-devel@alsa-project.org
Subject: UCM/DAPM - saving power when idle?
Date: Thu, 01 Nov 2012 11:39:01 +0100 [thread overview]
Message-ID: <50925145.4070706@canonical.com> (raw)
I don't deal much with ASoC, so sorry if I'm missing something obvious
here...
When a certain use case is activated, that would then activate some DAPM
widgets, causing the codec to consume more power. So, we should
essentially avoid this unless we're actually playing back/recording.
But, why isn't there a "disable all use cases" command, or possibly an
"idle" command? (That, essentially, e g pulseaudio should set whenever
playback/recording stops)
Or; the option would be that the codec is actually powered down, but
only activates itself when there is a stream; but this looks like it
could cause problem with loopback paths (e g listening to FM radio,
where there are no streams passing through CPU/main memory).
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next reply other threads:[~2012-11-01 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 10:39 David Henningsson [this message]
2012-11-01 15:26 ` UCM/DAPM - saving power when idle? Liam Girdwood
2012-11-02 14:30 ` Mark Brown
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=50925145.4070706@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
/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