From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
	alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v4 1/5] OMAP4: hwmod: Add names for DMIC memory address space
Date: Mon, 23 Jan 2012 13:52:35 +0200	[thread overview]
Message-ID: <4F1D4A03.3050700@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112191451140.12660@utopia.booyaka.com>
Hi Paul, Tony,
On 12/19/2011 11:51 PM, Paul Walmsley wrote:
> Hi
> 
> On Fri, 16 Dec 2011, Cousson, Benoit wrote:
> 
>> On 12/16/2011 7:28 AM, Paul Walmsley wrote:
>>> On Mon, 28 Nov 2011, Peter Ujfalusi wrote:
>>>
>>>> To be able to get the memory resources by name from
>>>> the DMIC driver (for MPU and for DMA).
>>>
>>> Any comments on this one?  Looks like we'd need to add these names as
>>> hints in the script.
>>
>> Maybe not, in theory we should be able to detect the dual mapping and add the
>> proper name. I did that for some other IP in the ABE domain, so it should be
>> doable for that one too.
>>
>>>> Signed-off-by: Peter Ujfalusi<peter.ujfalusi@ti.com>
>>
>> Acked-by: Benoit Cousson <b-cousson@ti.com>
> 
> Cool.  Queued for when Tony wants to pull it.
This patch seams to be missing from 3.3-rc1. The rest of the series is
there, but because of the missing patch audio does not probe on
4430SDP/Blaze.
Can you queue this as a fix for Linus?
Thanks,
Péter
--
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
next prev parent reply	other threads:[~2012-01-23 11:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 13:45 [PATCH v4 0/5] Support for OMAP4 Digital Microphone interface Peter Ujfalusi
2011-11-28 13:45 ` [PATCH v4 1/5] OMAP4: hwmod: Add names for DMIC memory address space Peter Ujfalusi
2011-12-16  6:28   ` Paul Walmsley
2011-12-16 14:43     ` Cousson, Benoit
2011-12-19 21:51       ` Paul Walmsley
2012-01-23 11:52         ` Peter Ujfalusi [this message]
2012-01-24  8:36           ` Paul Walmsley
2012-01-24 10:01             ` Peter Ujfalusi
2012-01-25 21:23               ` Paul Walmsley
2012-02-01  7:40                 ` Peter Ujfalusi
2012-02-01 19:08                   ` Paul Walmsley
2012-02-02  8:32                     ` Peter Ujfalusi
2011-11-28 13:45 ` [PATCH v4 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC Peter Ujfalusi
2011-11-28 17:21   ` Mark Brown
2011-11-28 13:45 ` [PATCH v4 3/5] OMAP4: devices: Register OMAP4 DMIC platform device Peter Ujfalusi
2011-12-09 21:03   ` Tony Lindgren
2011-11-28 13:45 ` [PATCH v4 4/5] OMAP4: board-4430sdp: Register platform device for digimic codec Peter Ujfalusi
2011-11-28 13:45 ` [PATCH v4 5/5] ASoC: sdp4430: Add support for digital microphones Peter Ujfalusi
2011-11-28 17:22   ` 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=4F1D4A03.3050700@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=b-cousson@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --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).