From: Mark Brown <broonie@sirena.org.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC] SoC WM8940 Driver
Date: Mon, 27 Apr 2009 13:25:50 +0100 [thread overview]
Message-ID: <20090427122550.GF1760@sirena.org.uk> (raw)
In-Reply-To: <49F599BB.9050805@cam.ac.uk>
On Mon, Apr 27, 2009 at 11:40:43AM +0000, Jonathan Cameron wrote:
> As in snd_soc_dapm_add_route only mux, switch and mixer controls can take
> a control element.
You can modify the core, or if you're not keen on doing that just drop
this feature for now - it's relatively rarely used.
> Nearest I can currently come up with is to insert a mux with only one option...
It'd need to be a mixer, at least. A mux with only one option could
never be disabled.
next prev parent reply other threads:[~2009-04-27 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 19:29 [RFC] SoC WM8940 Driver Jonathan Cameron
2009-04-25 10:21 ` Mark Brown
2009-04-25 17:17 ` Jonathan Cameron
2009-04-25 18:03 ` Mark Brown
2009-04-25 19:47 ` Jonathan Cameron
2009-04-27 11:40 ` Jonathan Cameron
2009-04-27 12:25 ` Mark Brown [this message]
2009-04-27 12:35 ` Jonathan Cameron
2009-04-27 13:49 ` [PATCH] " Jonathan Cameron
2009-04-27 19:58 ` 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=20090427122550.GF1760@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=jic23@cam.ac.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