From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Olaya, Margarita" <magi.olaya@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Two Codecs in the machine driver
Date: Tue, 21 Jul 2009 09:42:01 +0100 [thread overview]
Message-ID: <20090721084201.GA13286@sirena.org.uk> (raw)
In-Reply-To: <1889FA7136B567478A67D4B0F85B0CCE4891B081@dlee06.ent.ti.com>
On Mon, Jul 20, 2009 at 08:28:46PM -0500, Olaya, Margarita wrote:
> I have a hardware platform which has two codecs and I want to create a
> SoC machine driver to connect them to the processor, but it's not
> clear to me how to do that. Do you have any suggestions? Is there any
> driver that I can see as an example?
That's not entirely possible at the minute due to DAPM using strings to
identify devices. There is one example of this, though, in the Pandora
which uses a twl4030 together with a simple, no control, DAC.
prev parent reply other threads:[~2009-07-21 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 1:28 Two Codecs in the machine driver Olaya, Margarita
2009-07-21 8:42 ` 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=20090721084201.GA13286@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=magi.olaya@ti.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