All of lore.kernel.org
 help / color / mirror / Atom feed
From: "G, Manjunath Kondaiah" <manjugk@ti.com>
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>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH v3 0/4] Adding OMAP DMIC driver to kernel
Date: Wed, 26 Jan 2011 06:52:36 +0530	[thread overview]
Message-ID: <20110126012236.GB8524@manju-desktop> (raw)
In-Reply-To: <1295992862-6154-1-git-send-email-dlambert@ti.com>

On Tue, Jan 25, 2011 at 04:00:58PM -0600, David Lambert wrote:
> This is a patch series to add the OMAP Digital Microphone
> driver for OMAP4.
> 
> It includes the driver, a generic DMIC codec, platform devices,
> as well as HWMOD entries for OMAP44xx chipsets.
> 
> Note: The DMIC codec driver was removed from this series as it was
> accepted for and merged for the 2.6.38 kernel.

You have not mentioned the baseline for this patch series. I tried to apply
first patch of this series on linux omap master branch, patch applies cleanly
but the changes are not getting compiled eventhough it is enabled in Makefile
if I use omap2plus_defconfig. Am I missing anything?

-Manjunath

> 
> Benoit Cousson (1):
>   OMAP4: hwmod: add entries for DMIC driver
> 
> David Lambert (3):
>   ASoC: DMIC: Adding the OMAP DMIC driver
>   OMAP4: DMIC: initializes the DMIC driver
>   OMAP4: DMIC: Add DMIC codec platform devices
> 
>  arch/arm/mach-omap2/board-4430sdp.c        |   11 +
>  arch/arm/mach-omap2/omap_hwmod_44xx_data.c |   91 +++++
>  arch/arm/plat-omap/devices.c               |   35 ++
>  arch/arm/plat-omap/include/plat/dmic.h     |   82 +++++
>  sound/soc/omap/Kconfig                     |    3 +
>  sound/soc/omap/Makefile                    |    2 +
>  sound/soc/omap/omap-dmic.c                 |  534 ++++++++++++++++++++++++++++
>  7 files changed, 758 insertions(+), 0 deletions(-)
>  create mode 100644 arch/arm/plat-omap/include/plat/dmic.h
>  create mode 100644 sound/soc/omap/omap-dmic.c
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-01-26  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 22:00 [PATCH v3 0/4] Adding OMAP DMIC driver to kernel David Lambert
2011-01-25 22:00 ` [PATCH v3 1/4] ASoC: DMIC: Adding the OMAP DMIC driver David Lambert
2011-01-28  7:43   ` Varadarajan, Charulatha
2011-01-28  8:45   ` Varadarajan, Charulatha
2011-01-25 22:01 ` [PATCH v3 2/4] OMAP4: hwmod: add entries for " David Lambert
2011-01-25 23:54   ` Paul Walmsley
2011-01-26 12:55     ` Lambert, David
2011-01-26 17:28       ` Paul Walmsley
2011-02-14 15:36   ` Cousson, Benoit
2011-01-25 22:01 ` [PATCH v3 3/4] OMAP4: DMIC: initializes the " David Lambert
2011-01-28  7:46   ` Varadarajan, Charulatha
2011-01-25 22:01 ` [PATCH v3 4/4] OMAP4: DMIC: Add DMIC codec platform devices David Lambert
2011-01-26  1:22 ` G, Manjunath Kondaiah [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=20110126012236.GB8524@manju-desktop \
    --to=manjugk@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.