From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Stephen Warren <swarren@nvidia.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH 0/4] Implement control sharing
Date: Fri, 29 Apr 2011 16:28:42 +0100 [thread overview]
Message-ID: <1304090922.3521.42.camel@odin> (raw)
In-Reply-To: <1304033881-1160-1-git-send-email-swarren@nvidia.com>
On Thu, 2011-04-28 at 17:37 -0600, Stephen Warren wrote:
> Control sharing is enabled when two widgets include pointers to the
> same kcontrol_new in their definition. Specifically:
>
> static const struct snd_kcontrol_new adcinput_mux =
> SOC_DAPM_ENUM("ADC Input", adcinput_enum);
>
> static const struct snd_soc_dapm_widget wm8903_dapm_widgets[] = {
> SND_SOC_DAPM_MUX("Left ADC Input", SND_SOC_NOPM, 0, 0, &adcinput_mux),
> SND_SOC_DAPM_MUX("Right ADC Input", SND_SOC_NOPM, 0, 0, &adcinput_mux),
> };
>
> This is useful when a single register bit or field affects multiple
> muxes at once. The common case is to have separate control bits or
> fields for each mux (channel). An alternative way of looking at this
> is that the mux is a stereo (or even n-channel) mux, rather than
> independant mono muxes.
>
> I have tested this on NVIDIA Tegra Seaboard, specifically with the WM8903
> "ADC Input" control, and a locally-enabled digital mic setup.
>
> I have not compiled nor tested any other platforms.
>
> This patchset does not implement control sharing for dapm_new_mixer() yet.
> I can do so after discussion/review of this patch series, although note that
> I don't have anything to test the actual sharing on for such controls.
>
> Stephen Warren (4):
> ASoC: s/w->kcontrols/w->kcontrol_news/g
> ASoC: Add w->kcontrols, and populate it
> ASoC: Store a list of widgets in a DAPM mux/mixer kcontrol
> ASoC: Implement mux control sharing
>
> include/sound/soc-dapm.h | 75 +++++----
> sound/soc/codecs/88pm860x-codec.c | 2 +-
> sound/soc/soc-dapm.c | 315 ++++++++++++++++++++++++++-----------
> 3 files changed, 266 insertions(+), 126 deletions(-)
>
All
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-04-29 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 23:37 [PATCH 0/4] Implement control sharing Stephen Warren
2011-04-28 23:37 ` [PATCH 1/4] ASoC: s/w->kcontrols/w->kcontrol_news/g Stephen Warren
2011-04-28 23:37 ` [PATCH 2/4] ASoC: Add w->kcontrols, and populate it Stephen Warren
2011-04-28 23:38 ` [PATCH 3/4] ASoC: Store a list of widgets in a DAPM mux/mixer kcontrol Stephen Warren
2011-04-28 23:38 ` [PATCH 4/4] ASoC: Implement mux control sharing Stephen Warren
2011-04-29 15:28 ` Liam Girdwood [this message]
2011-05-03 18:30 ` [PATCH 0/4] Implement " 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=1304090922.3521.42.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=swarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.