From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: vbarinov <vbarinov@embeddedalley.com>,
Cliff Cai <cliff.cai@analog.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Timur Tabi <timur@freescale.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
"Candelaria Villareal, Jorge" <jorge.candelaria@ti.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
alsa-devel@alsa-project.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
"dg@emlix.com" <dg@emlix.com>,
Grant Likely <grant.likely@secretlab.ca>,
Sedji Gaouaou <sedji.gaouaou@atmel.com>,
"kyungmin.park" <kyungmin.park@samsung.com>,
ben-linux <ben-linux@fluff.org>,
Kuninori Morimoto <morimoto.kuninori@renesas.com>,
"mano@roarinelk.homelinux.net" <mano@roarinelk.homelinux.net>,
"anemo@mba.ocn.ne.jp" <anemo@mba.ocn.ne.jp>
Subject: Re: ASoC - Support for multiple components
Date: Mon, 26 Apr 2010 11:49:39 +0100 [thread overview]
Message-ID: <20100426104939.GC2035@sirena.org.uk> (raw)
In-Reply-To: <1271760367.3234.159.camel@odin>
On Tue, Apr 20, 2010 at 11:46:07AM +0100, Liam Girdwood wrote:
> On Tue, 2010-04-20 at 10:17 +0300, Peter Ujfalusi wrote:
> > How the user will see these in one card?
> A subsequent patch will add an ID qualifier to kcontrol names and DAPM
> widget names. So we can have things like "Master Playback Volume.0" and
> "Master Playback Volume.1" to differentiate the two separate controls.
It occurs to me that we probably want something a bit more flexible
here than just a numeric ID - most of the use cases for having more than
one of the same device are for things like 5.1 or dual speaker amps for
stereo where it'd be much more convenient to have the machine driver be
able to add text based prefixes to the control names (eg, "Left" and
"Right").
next prev parent reply other threads:[~2010-04-26 10:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 14:09 ASoC - Support for multiple components Liam Girdwood
2010-04-19 14:14 ` Timur Tabi
2010-04-19 15:15 ` Grant Likely
2010-04-19 16:25 ` Liam Girdwood
2010-04-19 17:14 ` Mark Brown
2010-04-19 17:23 ` Liam Girdwood
2010-04-19 17:03 ` Mark Brown
2010-04-20 7:17 ` Peter Ujfalusi
2010-04-20 10:46 ` Liam Girdwood
2010-04-21 5:53 ` Peter Ujfalusi
2010-04-21 7:18 ` Liam Girdwood
2010-04-21 17:41 ` Mark Brown
2010-04-26 10:49 ` Mark Brown [this message]
2010-04-26 11:17 ` Liam Girdwood
2010-04-26 14:24 ` Mark Brown
2010-04-26 12:05 ` Timur Tabi
2010-04-26 13:13 ` Mark Brown
2010-04-21 21:07 ` Timur Tabi
2010-04-21 22:13 ` Timur Tabi
2010-04-22 11:27 ` Liam Girdwood
2010-04-22 14:52 ` Timur Tabi
2010-04-22 11:03 ` Liam Girdwood
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=20100426104939.GC2035@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=ben-linux@fluff.org \
--cc=cliff.cai@analog.com \
--cc=dg@emlix.com \
--cc=grant.likely@secretlab.ca \
--cc=haojian.zhuang@gmail.com \
--cc=jorge.candelaria@ti.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lrg@slimlogic.co.uk \
--cc=mano@roarinelk.homelinux.net \
--cc=morimoto.kuninori@renesas.com \
--cc=peter.ujfalusi@nokia.com \
--cc=s.hauer@pengutronix.de \
--cc=sedji.gaouaou@atmel.com \
--cc=timur@freescale.com \
--cc=vbarinov@embeddedalley.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