From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: vbarinov <vbarinov@embeddedalley.com>,
Cliff Cai <cliff.cai@analog.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
alsa-devel@alsa-project.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"Candelaria Villareal, Jorge" <jorge.candelaria@ti.com>,
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>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: ASoC - Support for multiple components
Date: Mon, 26 Apr 2010 14:13:31 +0100 [thread overview]
Message-ID: <20100426131331.GA11022@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <o2ked82fe3e1004260505jf33b4456g760b139de341ea@mail.gmail.com>
On Mon, Apr 26, 2010 at 07:05:41AM -0500, Timur Tabi wrote:
> On Mon, Apr 26, 2010 at 5:49 AM, Mark Brown
> > 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").
> How about instead of a string + id, we just have a string, and then
> define a convention for various devices. For instance, the codec
> could be "name@bus-addr", so my cs4270 driver would register something
> like "cs4270@0-004f".
Well, we already have a struct device for the actual chip so we can just
dev_name() away. The problem is presenting the results to userspace in
a useful fashion.
next prev parent reply other threads:[~2010-04-26 13:13 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
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 [this message]
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=20100426131331.GA11022@rakim.wolfsonmicro.main \
--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