From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Liam Girdwood <lrg@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: [PATCH v3 0/9] ARM/ASoC: OMAP McBSP device tree support
Date: Fri, 17 Aug 2012 06:10:24 -0700 [thread overview]
Message-ID: <20120817131023.GE11011@atomide.com> (raw)
In-Reply-To: <20120817101838.GB30548@opensource.wolfsonmicro.com>
* Mark Brown <broonie@opensource.wolfsonmicro.com> [120817 03:18]:
> On Thu, Aug 16, 2012 at 04:40:59PM +0300, Peter Ujfalusi wrote:
>
> > in order to be able to add DT support for the McBSP driver which is used on all
> > OMAP platforms (OMAP1/2/3/4/5) I needed to make some cleanups to the stack:
>
> Tony, are you OK with these changes going via ASoC?
Yes, had one 2420 related question about the FIFO, other than that
I've acked the omap related patches.
Tony
prev parent reply other threads:[~2012-08-17 13:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 13:40 [PATCH v3 0/9] ARM/ASoC: OMAP McBSP device tree support Peter Ujfalusi
2012-08-16 13:41 ` [PATCH v3 1/9] ARM/ASoC: omap-mcbsp: Move OMAP2+ clock parenting code to ASoC driver Peter Ujfalusi
2012-08-17 13:06 ` Tony Lindgren
2012-08-22 19:10 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 2/9] ARM: OMAP: mcbsp: Enable FIFO use for OMAP2430 Peter Ujfalusi
2012-08-17 13:07 ` Tony Lindgren
2012-08-17 13:14 ` Jarkko Nikula
2012-08-17 14:03 ` Peter Ujfalusi
2012-08-18 6:08 ` Tony Lindgren
2012-08-18 15:58 ` Ujfalusi, Peter
2012-08-20 6:57 ` Tony Lindgren
2012-08-22 19:11 ` Mark Brown
2012-08-22 21:01 ` Tony Lindgren
2012-08-16 13:41 ` [PATCH v3 3/9] ARM: OMAP: board-am3517evm: Configure McBSP1 CLKR/FSR signal source Peter Ujfalusi
2012-08-17 13:07 ` Tony Lindgren
2012-08-22 19:12 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 4/9] ASoC: am3517evm: Do not configure McBSP1 CLKR/FSR signal muxing Peter Ujfalusi
2012-08-17 13:08 ` Tony Lindgren
2012-08-22 19:13 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 5/9] ARM/ASoC: omap-mcbsp: Remove CLKR/FSR mux configuration code Peter Ujfalusi
2012-08-17 13:08 ` Tony Lindgren
2012-08-22 19:15 ` Mark Brown
2012-08-23 8:12 ` Peter Ujfalusi
2012-08-16 13:41 ` [PATCH v3 6/9] ASoC: omap-mcbsp: Remove unused defines Peter Ujfalusi
2012-08-22 19:15 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 7/9] ASoC: omap-mcbsp: Remove cpu_is_omap* checks from the code Peter Ujfalusi
2012-08-22 19:15 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 8/9] ARM: OMAP2+: McBSP: Do not create legacy devices when booting with DT data Peter Ujfalusi
2012-08-17 13:09 ` Tony Lindgren
2012-08-22 19:16 ` Mark Brown
2012-08-16 13:41 ` [PATCH v3 9/9] ASoC: omap-mcbsp: Add device tree bindings Peter Ujfalusi
2012-08-22 19:16 ` Mark Brown
2012-08-17 10:18 ` [PATCH v3 0/9] ARM/ASoC: OMAP McBSP device tree support Mark Brown
2012-08-17 13:10 ` Tony Lindgren [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=20120817131023.GE11011@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.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).