From: Grazvydas Ignotas <notasas@gmail.com>
To: Jarkko Nikula <jhnikula@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: Mon, 8 Feb 2010 14:29:17 +0200 [thread overview]
Message-ID: <6ed0b2681002080429m6cdc0bc0u98849ae546c7f6e8@mail.gmail.com> (raw)
In-Reply-To: <20100207110732.9279b77a.jhnikula@gmail.com>
On Sun, Feb 7, 2010 at 11:07 AM, Jarkko Nikula <jhnikula@gmail.com> wrote:
> 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
I was testing with '-f cd' which should also be signed. Actually doing
just 'aplay /dev/zero' makes matters worse, there is some additional
'squeek' noise audible when I turn the volume up.
On Mon, Feb 8, 2010 at 1:39 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> If this goes off too much you might want to tweak the delay ASoC uses to
> defer power down of DAPM widgets after streams stop. There's a command
> line option pmdown_time, it really ought to have a sysfs file to tweak
> but there's not been any demand.
Yes we are already using that (set to 1 minute), and the sysfs file
would be useful for us (we have a hack for that in our tree).
next prev parent reply other threads:[~2010-02-08 12:29 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
2010-02-08 12:29 ` Grazvydas Ignotas [this message]
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=6ed0b2681002080429m6cdc0bc0u98849ae546c7f6e8@mail.gmail.com \
--to=notasas@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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).