From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Subject: Re: [PATCH 2/7] OMAP: mux: Add support for control module split in several partitions
Date: Tue, 16 Nov 2010 09:37:03 -0800 [thread overview]
Message-ID: <20101116173703.GU9264@atomide.com> (raw)
In-Reply-To: <4CE2B951.2070609@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [101116 08:53]:
> Hi Tony,
>
> On 11/16/2010 5:41 PM, Tony Lindgren wrote:
> >* Cousson, Benoit<b-cousson@ti.com> [101115 13:36]:
> >>Hi Tony,
> >>
> >>On 11/15/2010 9:03 PM, Tony Lindgren wrote:
> >>>* Benoit Cousson<b-cousson@ti.com> [101111 13:26]:
> >>>>Starting on OMAP4, the pin mux configuration is located in two
> >>>>different partitions of the control module (CODE_PAD and WKUP_PAD).
> >>>>The first one is inside the core power domain whereas the second
> >>>>one is inside the wakeup.
> >>>>- Add the capability to add any number of partition during board init
> >>>>time depending of Soc partitioning.
> >>>>- Add some init flags as well in order to avoid explicit Soc version
> >>>>check inside the mux core code.
> >>>>- Add a comment with mux0 mode on top of omap_mux/board/<partition>
> >>>>if the current mux mode is not the default one.
> >>>
> >>>Here's one more patch that I'd like to merge into this patch to avoid
> >>>repeating the partition for each mux entry.
> >>
> >>The memory vendors will not like you ;-)
> >>
> >>>Assuming no more comments, I'll queue these for 2.6.38 merge window.
> >>
> >>I'll update the series and re-post tomorrow.
> >
> >Thanks, no need to post them again, I already have them queued
> >locally, they will hit for-next and linux-omap master today.
>
> OK, but I already did it because there is a checkpatch issue in your
> first patch and I received another patch from Dan to add __func__ in
> the pr_xxx macros.
> I can repost, or you can get the update in my GIT (ctrl-wip/mux-omap4-v4).
OK, if they're changed maybe repost the whole series one more time,
and then I'll merge in your branch assuming no more comments.
> >BTW, next time you do a git branch, please base it on Linus recent
> >-rc tag instead of linux-omap master branch. We don't want the
> >history of linux-omap master branch merged to the mainline tree..
>
> Euh, this is what I already did for this series. Quoting myself:
>
> "The series is based on mainline (2.6.37-rc1) and is available here:
> git://gitorious.org/omap-pm/linux.git ctrl-wip/mux-omap4-v3"
>
> Did I messed up something?
No, mux-omap4-v4 branch looks OK. I guess what I tried pulling
was something older.
Regards,
Tony
next prev parent reply other threads:[~2010-11-16 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 21:35 [PATCH 0/7] OMAP4: mux: Add the OMAP4430 ES1.0 & ES2.x support Benoit Cousson
2010-11-11 21:35 ` [PATCH 1/7] OMAP: mux: Replace printk with pr_xxx macros Benoit Cousson
2010-11-11 21:35 ` [PATCH 2/7] OMAP: mux: Add support for control module split in several partitions Benoit Cousson
2010-11-15 20:03 ` Tony Lindgren
2010-11-15 21:46 ` Cousson, Benoit
2010-11-16 16:41 ` Tony Lindgren
2010-11-16 17:03 ` Cousson, Benoit
2010-11-16 17:37 ` Tony Lindgren [this message]
2010-11-16 18:37 ` Cousson, Benoit
2010-11-11 21:35 ` [PATCH 3/7] OMAP4: mux: Add CBL package data for OMAP4430 ES1 Benoit Cousson
2010-11-11 21:35 ` [PATCH 4/7] OMAP4: sdp4430: Select CBL package for ES1 and initialize mux Benoit Cousson
2010-11-11 21:35 ` [PATCH 5/7] OMAP4: mux: Add CBS package data for OMAP4430 ES2 Benoit Cousson
2010-11-11 21:35 ` [PATCH 6/7] OMAP4: sdp4430: Select CBS package for ES2 Benoit Cousson
2010-11-11 21:35 ` [PATCH 7/7] OMAP4: pandaboard: Select CBL & CBS package and initialize mux Benoit Cousson
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=20101116173703.GU9264@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.