From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: [PATCH v2 1/5] OMAP4: hwmod: Add names for DMIC memory address space
Date: Thu, 24 Nov 2011 22:24:06 +0000 [thread overview]
Message-ID: <20111124222406.GB21244@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1322142889-12017-2-git-send-email-peter.ujfalusi@ti.com>
On Thu, Nov 24, 2011 at 03:54:45PM +0200, Peter Ujfalusi wrote:
> To be able to get the memory resources by name from
> the DMIC driver (for MPU and for DMA).
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
There doesn't appear to be any direct dependency between the arch/arm
side and the ASoC side here so the OMAP stuff should just go in via OMAP
(assuming there's no problems, it looks good to me).
next prev parent reply other threads:[~2011-11-24 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 13:54 [PATCH v2 0/5] Support for OMAP4 Digital Microphone interface Peter Ujfalusi
2011-11-24 13:54 ` [PATCH v2 1/5] OMAP4: hwmod: Add names for DMIC memory address space Peter Ujfalusi
2011-11-24 22:24 ` Mark Brown [this message]
2011-11-24 13:54 ` [PATCH v2 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC Peter Ujfalusi
2011-11-24 17:10 ` Mark Brown
2011-11-25 9:31 ` Péter Ujfalusi
2011-11-24 13:54 ` [PATCH v2 3/5] OMAP4: devices: Register OMAP4 DMIC platform device Peter Ujfalusi
2011-11-24 13:54 ` [PATCH v2 4/5] OMAP4: board-4430sdp: Register platform device for digimic codec Peter Ujfalusi
2011-11-24 13:54 ` [PATCH v2 5/5] ASoC: sdp4430: Add support for digital microphones Peter Ujfalusi
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=20111124222406.GB21244@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.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).