public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "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 17:15:22 +0300	[thread overview]
Message-ID: <20090507171522.afed1a86.jhnikula@gmail.com> (raw)
In-Reply-To: <200905071408.14629.peter.ujfalusi@nokia.com>

On Thu, 7 May 2009 14:08:14 +0300
Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:

> I need to revisit this...
> After more testing and debugging, it seams that I can not confirm the 
> existence of the "tuck" (with the latest twl4030  codec code).
> As soon as I receive my Beagle board I will test it again (can anyone
> test this with latest ASoC code on Beagle?)...
> 
I can hear somewhat audible (stetson guessed -20 db
from /dev/urandom level) power-up/-down pop with "aplay -f
dat /dev/zero" but no any other beeps or noises.

I cannot hear any difference in pop level am I using head of linux-omap
or when merging sound-2.6/asoc on top of it.

Of cource this pop noise can be codec output & load dependent and also
possible on-board amplifier with proper power sequencing can mask the
noise. For reference, output jack of the Beagle is connected directly
into HSOL and HSOR pins.


-- 
Jarkko

  parent reply	other threads:[~2009-05-07 14:15 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
2009-05-07 14:15           ` Jarkko Nikula [this message]
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=20090507171522.afed1a86.jhnikula@gmail.com \
    --to=jhnikula@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