From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Bensaid, Selma" <selma.bensaid@intel.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: registering multiple cards
Date: Tue, 11 Jan 2011 11:28:24 +0000 [thread overview]
Message-ID: <20110111112824.GB13429@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A44630108443A6D8B@bgsmsx502.gar.corp.intel.com>
On Tue, Jan 11, 2011 at 04:57:14PM +0530, Koul, Vinod wrote:
> Currently snd_soc_register_card is internal soc-core API and is called from
> soc-probe. And probe always assumes it is a single device, so how do we add
> up two cards?
> I saw a note on this that it will exposed so that drivers can register.
> What is that plan to do that, and meanwhile what can be done to solve this?
Just register two soc-audio devices. Calling register_card() directly
will just make the API a bit nicer, it shouldn't add any new features.
next prev parent reply other threads:[~2011-01-11 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 11:27 registering multiple cards Koul, Vinod
2011-01-11 11:28 ` Mark Brown [this message]
2011-01-13 6:45 ` Koul, Vinod
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=20110111112824.GB13429@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=selma.bensaid@intel.com \
--cc=vinod.koul@intel.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