From: Arun KS <getarunks@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "ext Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
"todd.fischer@ridgerun.com" <todd.fischer@ridgerun.com>,
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 18:18:20 +0530 [thread overview]
Message-ID: <dfeb90390905070548i6c581ce9g3bd10e0a65636aa9@mail.gmail.com> (raw)
In-Reply-To: <200905071424.45431.peter.ujfalusi@nokia.com>
On Thu, May 7, 2009 at 4:54 PM, Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:
> On Thursday 07 May 2009 14:16:12 ext Aggarwal, Anuj wrote:
>> > [Anuj]: What kernel are you using where you have the beep?
>>
>> [Aggarwal, Anuj] 2.6.29-rc3
>
> That version still has the old power up/down code. Since than there were 23
> patches for the twl4030 codec.
> The Headset enable/disable mantra could be still wrong in the latest
> version...
But i tried with latest linux-omap tree(2.6.30-rc4) copying twl4030.*
files from latest linux sound tree.
I can still hear the tuck noise of DAPM on omap3evm board.
Arun
>
> --
> Péter
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2009-05-07 12: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
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 [this message]
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=dfeb90390905070548i6c581ce9g3bd10e0a65636aa9@mail.gmail.com \
--to=getarunks@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--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