From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 4/5] ASoC: dapm: Add support for autodisable mux controls
Date: Thu, 30 Apr 2015 16:58:58 +0100 [thread overview]
Message-ID: <20150430155858.GA22845@sirena.org.uk> (raw)
In-Reply-To: <55424CC6.7030701@metafoo.de>
[-- Attachment #1.1: Type: text/plain, Size: 569 bytes --]
On Thu, Apr 30, 2015 at 05:39:50PM +0200, Lars-Peter Clausen wrote:
> Hm, right. What I had in mind is to not export the off state to userland,
> but I guess it makes sense to make it possible to select it explicitly since
> it is consistent with the auto-disable switches.
It's not just consistent, you need to be able to do that so that you can
set something to a known unused input when it's not in use, otherwise
you need to worry about making sure that you don't end up causing audio
to flow through the mux unintentionally when you go into some other use
case.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-04-30 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:38 [PATCH 1/5] ASoC: Correct typo in SOC_VALUE_ENUM_SINGLE macro Charles Keepax
2015-04-30 10:38 ` [PATCH 2/5] ASoC: dapm: Remove local OOM error message Charles Keepax
2015-04-30 10:38 ` [PATCH 3/5] ASoC: dapm: Append "Autodisable" to autodisable widget names Charles Keepax
2015-04-30 10:38 ` [PATCH 4/5] ASoC: dapm: Add support for autodisable mux controls Charles Keepax
2015-04-30 12:44 ` Lars-Peter Clausen
2015-04-30 15:00 ` Charles Keepax
2015-04-30 15:39 ` Lars-Peter Clausen
2015-04-30 15:58 ` Mark Brown [this message]
2015-04-30 10:38 ` [PATCH 5/5] ASoC: arizona: Use auto disable muxes for routing Charles Keepax
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=20150430155858.GA22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.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