From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa device drain power
Date: Fri, 18 Dec 2009 14:28:35 +0100 [thread overview]
Message-ID: <4B2B8383.70806@gandalf.sssup.it> (raw)
In-Reply-To: <20091218125356.GA29829@rakim.wolfsonmicro.main>
Hi,
Mark Brown wrote:
> On Fri, Dec 18, 2009 at 01:20:51PM +0100, Michael Trimarchi wrote:
>
>
>> I don't send any sound to the device so it remains on, it's the
>> correct behavior?
>>
>
> What do you mean by that - what exactly is "send any sound to the
> device" in this context? Do you mean that you aren't playing any audio
> from the CPU?
I don't play any audio file (mp3 ogg) to the device but open it during
boot sequence
using the SpeakerOut profile. The speake audio path is not used.
For design decision Android open the device in
AudioFlinger Theread:
I/AudioHardwareALSA( 867): Initialized ALSA PLAYBACK device
AndroidPlayback_Speaker_normal
D/AudioHardwareALSA( 867): Set PLAYBACK PCM format to S16_LE (Signed 16
bit Little Endian)
D/AudioHardwareALSA( 867): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 867): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 867): Buffer size: 16384
D/AudioHardwareALSA( 867): Latency: 371519
and this remains open. So the the lm is switch on on boot. I think that
the correct behavior
is to have a different profile in asound.conf to avoid power drain and
open a different one when
the system want to use the speaker or just not open the alsa device.
Hope that the now is clear
Best regards
Michael
prev parent reply other threads:[~2009-12-18 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 8:47 alsa device drain power Michael Trimarchi
2009-12-17 11:03 ` Mark Brown
2009-12-18 10:03 ` Michael Trimarchi
2009-12-18 11:32 ` Mark Brown
2009-12-18 12:20 ` Michael Trimarchi
2009-12-18 12:53 ` Mark Brown
2009-12-18 13:28 ` Michael Trimarchi [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=4B2B8383.70806@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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.