From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC 0/5] OMAP4: mux: Add the OMAP4430 ES1 support
Date: Mon, 18 Oct 2010 16:00:13 -0700 [thread overview]
Message-ID: <20101018230013.GI13341@atomide.com> (raw)
In-Reply-To: <4CBCB35E.9080502@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [101018 13:42]:
> Hi Nishanth,
>
> On 10/18/2010 8:09 PM, Menon, Nishanth wrote:
> >>From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> >>owner@vger.kernel.org] On Behalf Of Benoit Cousson
> >>
> >Ping? Is there a possibility for a v2 non-rfc ES2 support?
>
> And what about a RFC v2? With ES2 support of course :-)
>
> The changes I have done are breaking RX51 support due to the usage
> of low-level API from the mux code.
>
> For the moment I just disabled that code from the RX51, so there is
> no way I send that except in a RFC form :-(
I have some ideas on doing the board specific runtime remuxing.
That should also solve the rx51 emmc remuxing.
Let's plan on merging your patches first after the merge window,
then I'll do my patches on top of yours to avoid rebasing.
Regards,
Tony
next prev parent reply other threads:[~2010-10-18 23:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 9:15 [RFC 0/5] OMAP4: mux: Add the OMAP4430 ES1 support Benoit Cousson
2010-09-24 9:15 ` [RFC 1/5] OMAP: mux: Add support for control module split in several partitions Benoit Cousson
2010-09-25 0:22 ` Tony Lindgren
2010-09-27 15:46 ` Tony Lindgren
2010-09-27 17:24 ` Cousson, Benoit
2010-09-27 17:36 ` Tony Lindgren
2010-09-27 20:03 ` Cousson, Benoit
2010-09-27 20:06 ` Tony Lindgren
2010-09-24 9:15 ` [RFC 2/5] OMAP: mux: Make low level function private Benoit Cousson
2010-09-24 23:09 ` Gadiyar, Anand
2010-09-24 23:50 ` Tim Nordell
2010-09-25 0:07 ` Anand Gadiyar
2010-09-25 6:48 ` Tim Nordell
2010-09-24 9:15 ` [RFC 3/5] OMAP4: mux: Add data for OMAP4430 ES1 Benoit Cousson
2010-09-24 23:18 ` Anand Gadiyar
2010-09-27 9:31 ` Cousson, Benoit
2010-09-24 9:15 ` [RFC 4/5] OMAP4: mux: Select CBL package for SDP4430 with ES1 Benoit Cousson
2010-09-24 23:14 ` Anand Gadiyar
2010-09-27 7:24 ` Cousson, Benoit
2010-09-24 9:15 ` [RFC 5/5] OMAP4: mux: Temporary initial SDP4430 mux settings Benoit Cousson
2010-10-18 18:09 ` [RFC 0/5] OMAP4: mux: Add the OMAP4430 ES1 support Menon, Nishanth
2010-10-18 20:51 ` Cousson, Benoit
2010-10-18 20:53 ` Menon, Nishanth
2010-10-18 20:57 ` Cousson, Benoit
2010-10-18 21:08 ` Menon, Nishanth
2010-10-18 23:00 ` Tony Lindgren [this message]
2010-10-18 23:12 ` Cousson, Benoit
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=20101018230013.GI13341@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@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).