From: Liam Girdwood <lrg@slimlogic.co.uk>
To: David Lambert <dlambert@ti.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [alsa-devel] [PATCH v2 2/4] ASoC: DMIC codec: Adding a generic DMIC codec
Date: Wed, 12 Jan 2011 00:54:48 +0000 [thread overview]
Message-ID: <1294793688.3338.484.camel@odin> (raw)
In-Reply-To: <1294322439-16305-3-git-send-email-dlambert@ti.com>
On Thu, 2011-01-06 at 08:00 -0600, David Lambert wrote:
> This codec is to be used by the DMIC driver to
> control the DMIC codec. This driver will be used on future
> implementations of the DMIC driver to support codec specific
> features.
>
> At this time, the codec driver just registers the codec DAI.
>
> Signed-off-by: David Lambert <dlambert@ti.com>
> ---
> sound/soc/codecs/Kconfig | 3 ++
> sound/soc/codecs/Makefile | 2 +
> sound/soc/codecs/dmic.c | 81 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 86 insertions(+), 0 deletions(-)
> create mode 100644 sound/soc/codecs/dmic.c
>
Applied.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2011-01-12 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 14:00 [PATCH v2 0/4] Adding OMAP DMIC driver to kernel David Lambert
2011-01-06 14:00 ` [PATCH v2 1/4] ASoC: DMIC: Adding the OMAP DMIC driver David Lambert
2011-01-06 22:20 ` Mark Brown
2011-01-07 16:34 ` Lambert, David
2011-01-07 17:13 ` Mark Brown
2011-01-06 14:00 ` [PATCH v2 2/4] ASoC: DMIC codec: Adding a generic DMIC codec David Lambert
2011-01-12 0:54 ` Liam Girdwood [this message]
2011-01-06 14:00 ` [PATCH v2 3/4] OMAP4: hwmod: add entries for DMIC driver David Lambert
2011-01-06 22:23 ` Mark Brown
2011-01-06 22:39 ` Kevin Hilman
2011-01-06 14:00 ` [PATCH v2 4/4] OMAP4: DMIC: Add DMIC codec platform devices David Lambert
2011-01-06 22:25 ` Mark Brown
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=1294793688.3338.484.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dlambert@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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