From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Bensaid, Selma" <selma.bensaid@intel.com>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Benavoli, PatrickX" <patrickx.benavoli@intel.com>
Subject: Re: : Question ASoC driver without Codec driver?
Date: Wed, 23 Feb 2011 20:08:57 +0000 [thread overview]
Message-ID: <20110223200857.GB2534@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <2A84145621092446B6659B8A0F28E26F4703F09682@irsmsx501.ger.corp.intel.com>
On Wed, Feb 23, 2011 at 09:29:41AM +0000, Bensaid, Selma wrote:
> I'm trying to find out if it's possible to implement an ASoC driver
> without a codec driver.
Obviously, platform and CPU drivers have no CODEC dependencies.
> I'm implementing a ASoC driver for BT/FM WL1273, where the FM WL1273 control
> interface is based on V4L2 since since we use the Combined Interface
> Mode (The host controls both the BT and the FM Radio through the BT HCI host interface).
You need to implement a CODEC driver for this but there's no reason for
it to do anything except expose the capabilities of the device - there's
several in tree examples you can look at. Remember that we still need
to know how to configure the other drivers that talk to the chip, even
if the chip itself is unconfigurable.
next prev parent reply other threads:[~2011-02-23 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 9:29 : Question ASoC driver without Codec driver? Bensaid, Selma
2011-02-23 20:08 ` Mark Brown [this message]
2011-02-24 7:39 ` Peter Ujfalusi
2011-02-24 10:46 ` Matti J. Aaltonen
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=20110223200857.GB2534@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=patrickx.benavoli@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).