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>,
"Harsha, Priya" <priya.harsha@intel.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: asoc device probing and dai question
Date: Thu, 2 Dec 2010 11:47:13 +0000 [thread overview]
Message-ID: <20101202114712.GB28575@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A44630104BEE14118@bgsmsx502.gar.corp.intel.com>
On Thu, Dec 02, 2010 at 05:08:51PM +0530, Koul, Vinod wrote:
> So I am thinking now that since my platform tells me that I have only one audio
> device which is platform device, so should I add my codec device and platform
> device same way as I add the soc-audio from my machine driver. That way I can
> even change codec's based on what I detect on the board.
> And platform and codec driver probe register the dais
> Would that be the right approach?
Ideally your platform would also register the devices separately
(especialy the CODEC which would usually be instantiated by whatever
bus it's on, or the probe of the core driver for the CODEC if it's an
MFD like yours are in silicon) but if you're limited in this way then
it's a good approach.
It may be worth separating out the device registration from the rest of
the machine driver for clarity.
prev parent reply other threads:[~2010-12-02 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 11:01 asoc device probing and dai question Koul, Vinod
2010-12-02 11:07 ` Mark Brown
2010-12-02 11:23 ` Koul, Vinod
2010-12-02 11:25 ` Mark Brown
2010-12-02 11:38 ` Koul, Vinod
2010-12-02 11:47 ` 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=20101202114712.GB28575@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=priya.harsha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.