From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: utils - Add support for a dummy codec driver.
Date: Tue, 10 Jan 2012 10:53:15 +0000 [thread overview]
Message-ID: <1326192795.3944.1.camel@odin> (raw)
In-Reply-To: <20120110044119.GQ30766@opensource.wolfsonmicro.com>
On Tue, 2012-01-10 at 04:41 +0000, Mark Brown wrote:
> On Mon, Jan 09, 2012 at 12:36:24PM +0000, Liam Girdwood wrote:
> > This is useful to create dummy codec devices where we need to have some
> > DAI links without a real Codec. e.g. could be used to represent dumb FM,
> > MODEM, etc
>
> I've applied this but I think we should move it into the CODECs
> directory - I stubbed the platform out in here mostly because there
> isn't a natural place to put a platform driver that's not associated
> with a particular platform. Does that sound sensible?
yeah, I was 50/50 about this since we do have codecs/ and utils.c. I
don't really mind where it goes.
Liam
prev parent reply other threads:[~2012-01-10 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 12:36 [PATCH] ASoC: utils - Add support for a dummy codec driver Liam Girdwood
2012-01-10 4:41 ` Mark Brown
2012-01-10 10:53 ` Liam Girdwood [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=1326192795.3944.1.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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).