From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Lambert <dlambert@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Paul Walmsley <paul@pwsan.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH v2 3/4] OMAP4: hwmod: add entries for DMIC driver
Date: Thu, 6 Jan 2011 22:23:00 +0000 [thread overview]
Message-ID: <20110106222300.GE8408@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1294322439-16305-4-git-send-email-dlambert@ti.com>
On Thu, Jan 06, 2011 at 08:00:38AM -0600, David Lambert wrote:
> Adds HWMOD entries for the OMAP DMIC driver and creates
> a platform device. The HWMOD entires define the system
> resource requirements for the drvier such as DMA addresses, channels,
> and IRQ's. Placing this information in the HWMOD database allows
> for more generic drivers to be written and having the specific
> implementation details defined in HWMOD.
>
> Signed-off-by: David Lambert <dlambert@ti.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2011-01-06 22:22 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 ` [alsa-devel] " Liam Girdwood
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 [this message]
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=20110106222300.GE8408@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;
as well as URLs for NNTP newsgroup(s).