From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Bard Liao <bardliao@realtek.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: Broken headphone and speaker amplifier suppliesforthe rt5640 driver
Date: Mon, 29 Jul 2013 07:45:50 +0100 [thread overview]
Message-ID: <20130729064549.GT9858@sirena.org.uk> (raw)
In-Reply-To: <51F6085B.1080900@metafoo.de>
[-- Attachment #1.1: Type: text/plain, Size: 615 bytes --]
On Mon, Jul 29, 2013 at 08:14:51AM +0200, Lars-Peter Clausen wrote:
> Yea, so the stuff I was working on while I stumbled upon this was more or
> less that. Support for letting DAPM mute controls, which are also exposed to
> userspace, if necessary in order to avoid clicks and pops. Once muted by
> DAPM userspace will only see a cached value of the controls state and once
> DAPM unmutes the control the userspace state will be restored.
Oh, cool. That's not really been an issue with most ground referenced
hardware (at least not normally) but it'd really useful for a large
proportion of VMID based devices.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-07-29 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 15:06 Broken headphone and speaker amplifier supplies for the rt5640 driver Lars-Peter Clausen
2013-07-26 16:57 ` Stephen Warren
2013-07-27 17:35 ` Mark Brown
2013-07-29 3:04 ` Broken headphone and speaker amplifier suppliesforthe " Bard Liao
2013-07-29 6:07 ` Mark Brown
2013-07-29 6:14 ` Lars-Peter Clausen
2013-07-29 6:45 ` Mark Brown [this message]
[not found] ` <201307290148.r6T1mLk1013980@rtits1.realtek.com>
2013-07-29 2:48 ` Bard Liao
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=20130729064549.GT9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=lars@metafoo.de \
--cc=swarren@wwwdotorg.org \
/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