From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Tony Lindgren <tony@atomide.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-omap@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] OMAP4: Fix CLKR/FSR mux for port with 6 pin mode
Date: Fri, 23 Dec 2011 12:34:43 +0200 [thread overview]
Message-ID: <4EF45943.3020302@bitmer.com> (raw)
In-Reply-To: <1324575106-17172-1-git-send-email-peter.ujfalusi@ti.com>
On 12/22/2011 07:31 PM, Peter Ujfalusi wrote:
> Hello,
>
> This series will fix the CLKR/FSR signal mux configuration for OMAP4 devices.
> McBSP4 has 6 pin configuration on McBSP4 port while OMAP2/3 has the same
> capability on McBSP1 port.
> The API for mux control will be simplified for the mcbsp users (ASoC).
>
> The series depends on earlier series sent for mcbsp:
> OMAP4: McBSP: Fix clock reparenting
>
> I think the ASoC patch can go via linux-omap, since we do not have other changes
> for McBSP coming via sound tree.
>
Looks ok to me and you can have my ack if you plan to resend this after
clock reparenting fix set. (Note small typo in 2/5 subject)
Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
prev parent reply other threads:[~2011-12-23 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 17:31 [PATCH 0/5] OMAP4: Fix CLKR/FSR mux for port with 6 pin mode Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 1/5] OMAP2/3: mcbsp: Check McBSP port number in CLKR/FSR mux callback Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 2/5] OMAP: mcbsp: Signle function for CLKR/FSR source mux configuration Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 3/5] ASoC: omap-mcbsp: Use the new interface for configuring CLKR/FSR mux Peter Ujfalusi
2011-12-22 17:33 ` Mark Brown
2011-12-22 17:31 ` [PATCH 4/5] OMAP: mcbsp: Remove old CLKR/FSR mux functions Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 5/5] OMAP4: mcbsp: Callback function for McBSP4 CLKR/FSR mux selection Peter Ujfalusi
2011-12-23 10:34 ` Jarkko Nikula [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=4EF45943.3020302@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).