public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Lambert <dlambert@ti.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
	Liam Girdwood <lrg@slimlogic.co.uk>,
	Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 2/5] ASoC: DMIC codec: Adding a generic DMIC codec
Date: Tue, 28 Dec 2010 14:29:09 +0000	[thread overview]
Message-ID: <20101228142909.GB31883@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1293509826-23253-3-git-send-email-dlambert@ti.com>

On Mon, Dec 27, 2010 at 10:17:03PM -0600, David Lambert wrote:

> At this time, the codec driver just registers the codec DAI.

If it's doing more than that it's going to be a separate driver anyway I
expect.

> +static struct snd_soc_dai_driver dmic_dai = {
> +	.name = "dmic-hifi",
> +	.capture = {
> +		.stream_name = "Capture",
> +		.channels_min = 1,
> +		.channels_max = 8,
> +		.rates = SNDRV_PCM_RATE_CONTINUOUS,
> +		.formats = SNDRV_PCM_FMTBIT_S32_LE
> +			| SNDRV_PCM_FMTBIT_S24_LE
> +			| SNDRV_PCM_FMTBIT_S16_LE,

Hrm, so.  DMIC signals are inherantly stereo, though obviously you can
bind multiple DMICs in parallel using the same clock line so from the
CPU side the channel limit makes sense.  Similarly the format here
really makes very little odds on a PDM interface.

What we probably want here is wildcards for both channel and format
limits which we can use to say "this is meaningless, just match
anything" in case the other end needs it (like a CPU PDM interface does
to set up the DMA).

> +static struct platform_driver dmic_driver = {
> +	.driver = {
> +		.name = "dmic-codec",

Just -dmic.

> +MODULE_DESCRIPTION("Generic DMIC driver");
> +MODULE_AUTHOR("Liam Girdwood <lrg@slimlogic.co.uk>");
> +MODULE_LICENSE("GPL");

MODULE_ALIAS().

  reply	other threads:[~2010-12-28 14:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28  4:17 [PATCH 0/5] Adding OMAP DMIC driver to kernel David Lambert
2010-12-28  4:17 ` [PATCH 1/5] ASoC: DMIC: Adding the OMAP DMIC driver David Lambert
2010-12-28 11:14   ` Felipe Balbi
2010-12-29  1:13     ` Lambert, David
2010-12-29  9:47       ` Felipe Balbi
2010-12-29 10:35         ` Liam Girdwood
2010-12-29 10:44           ` Felipe Balbi
2010-12-29 11:52             ` Liam Girdwood
2010-12-29 11:56               ` Mark Brown
2010-12-29 11:59                 ` Felipe Balbi
2010-12-29 12:11                   ` Mark Brown
2010-12-29 12:04               ` Felipe Balbi
2010-12-29 13:00                 ` Liam Girdwood
2010-12-29 13:07                   ` Felipe Balbi
2010-12-28 14:18   ` Mark Brown
2011-01-05 13:56     ` Lambert, David
2011-01-05 14:03       ` Mark Brown
2010-12-28  4:17 ` [PATCH 2/5] ASoC: DMIC codec: Adding a generic DMIC codec David Lambert
2010-12-28 14:29   ` Mark Brown [this message]
2010-12-28  4:17 ` [PATCH 3/5] ASoC: DMIC: Adding OMAP DMIC driver to build David Lambert
2010-12-28 11:40   ` Mark Brown
2010-12-29  2:21     ` Lambert, David
2010-12-28  4:17 ` [PATCH 4/5] OMAP4: hwmod: add entries for DMIC driver David Lambert
2010-12-28  4:17 ` [PATCH 5/5] MAP4: DMIC: Add DMIC codec platform devices David Lambert
2010-12-28 11:23   ` Felipe Balbi

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=20101228142909.GB31883@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dlambert@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --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