From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: soc-dapm: Introduce the new snd_soc_dapm_virt_mux type
Date: Fri, 17 Dec 2010 17:37:12 +0000 [thread overview]
Message-ID: <20101217173712.GA30235@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1292514819-4254-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Thu, Dec 16, 2010 at 03:53:39PM +0000, Dimitris Papastamos wrote:
> This new type is a virtual version of snd_soc_dapm_mux. It is used
> when a backing register value is not necessary for deciding which
> input path to connect. A simple virtual enumeration control e.g.
> SOC_DAPM_ENUM_VIRT() can be exposed to userspace which will be used
> to choose which path to connect.
Applied, thanks.
prev parent reply other threads:[~2010-12-17 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 15:53 [PATCH] ASoC: soc-dapm: Introduce the new snd_soc_dapm_virt_mux type Dimitris Papastamos
2010-12-17 10:43 ` Liam Girdwood
2010-12-17 17:37 ` Mark Brown [this message]
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=20101217173712.GA30235@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--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