From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "todd.fischer@ridgerun.com" <todd.fischer@ridgerun.com>
Cc: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Beep sound in the end of audio file
Date: Thu, 7 May 2009 08:48:25 +0300 [thread overview]
Message-ID: <200905070848.25904.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <1241619589.8928.2038.camel@sax-lx.fischerfamily.org>
On Wednesday 06 May 2009 17:19:49 ext Todd Fischer wrote:
> Hi,
>
> FWIW: while developing a GSTreamer presentation using a BegleBoard (rev C),
> I noticed the same "tuck" sound. It also occurs a second or two after the
> GST application exits. I assumed it was some power management code that
> was disabling the audio codec after it had gone idle, but never looked into
> it. BeagleBoard also uses TWL4030.
>
> GST command: gst-launch audiotestsrc freq=1000 num-buffers=100 ! alsasink
>
> /proc/version: Linux version 2.6.28-omap1 (ddompe@Aleph) (gcc version 4.3.1
> (GCC) ) #2 Thu Mar 5 08:55:58 CST 2009
The "tuck" is coming from the codec, when it is powered down (in the old
twl4030 codec found in omap-2.6.28 branch of linux-omap).
But, it still happens with the latest version, when the codec is muted only.
I can observe the "tuck" on Headset output, but not on the PreDrive...
The Headset enable and disable is implemented according to the TRM, but it
seams that additional tweaking is needed..
--
Péter
next prev parent reply other threads:[~2009-05-07 5:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 17:03 Beep sound in the end of audio file Aggarwal, Anuj
2009-05-06 5:33 ` Peter Ujfalusi
2009-05-06 14:00 ` Aggarwal, Anuj
2009-05-06 14:07 ` [alsa-devel] " Mark Brown
2009-05-07 9:35 ` Arun KS
2009-05-07 9:38 ` [alsa-devel] " Mark Brown
2009-05-07 10:48 ` Arun KS
2009-05-06 14:19 ` Todd Fischer
2009-05-07 5:48 ` Peter Ujfalusi [this message]
2009-05-07 11:08 ` Peter Ujfalusi
2009-05-07 11:16 ` Aggarwal, Anuj
2009-05-07 11:24 ` Peter Ujfalusi
2009-05-07 12:48 ` Arun KS
2009-05-07 14:15 ` Jarkko Nikula
2009-05-06 14:01 ` Jon Smirl
2009-05-06 14:03 ` [alsa-devel] " Jon Smirl
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=200905070848.25904.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=todd.fischer@ridgerun.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