alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH -next] ASoC: pandora: Add DAC regulator support
Date: Sun, 7 Feb 2010 11:07:32 +0200	[thread overview]
Message-ID: <20100207110732.9279b77a.jhnikula@gmail.com> (raw)
In-Reply-To: <6ed0b2681002060933x38009b77r237db131ab172fee@mail.gmail.com>

On Sat, 6 Feb 2010 19:33:08 +0200
Grazvydas Ignotas <notasas@gmail.com> wrote:

> It's on powerdown, there is a faint pop. It appears its the amp (final
> part in the path), I tried to toggle it while playing /dev/zero
> manually and it always pops on powerdown. On powerup there is a small
> sound cutoff too, probably because of amp capacitors charging, but we
> decided to leave it instead of halting every sound playing program
> until the amp gets ready.
> 
My side comment for the /dev/zero test. You may hear pops also
if /dev/zero is played as unsigned 8-bit samples on signed DAC since
then samples gets converted to maximum negative value.

So there is a difference how the /dev/zero is played. First command
below produces a pop because it's playing a pop and second produces a
pop only if HW is producing it.

aplay /dev/zero
aplay -f S16_LE /dev/zero


-- 
Jarkko

  reply	other threads:[~2010-02-07  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 13:13 [PATCH -next] ASoC: pandora: Add DAC regulator support Grazvydas Ignotas
2010-02-05 14:08 ` Liam Girdwood
2010-02-05 14:29   ` Grazvydas Ignotas
2010-02-05 15:16     ` Liam Girdwood
2010-02-05 17:20     ` Mark Brown
2010-02-06 17:33       ` Grazvydas Ignotas
2010-02-07  9:07         ` Jarkko Nikula [this message]
2010-02-08 12:29           ` Grazvydas Ignotas
2010-02-08 11:39         ` 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=20100207110732.9279b77a.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=notasas@gmail.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;
as well as URLs for NNTP newsgroup(s).