From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 00/29] SH pinctrl and pinmux implementation
Date: Wed, 09 Jan 2013 07:08:01 +0000 [thread overview]
Message-ID: <20130109070801.GA14906@verge.net.au> (raw)
In-Reply-To: <1357692769-1432-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Wed, Jan 09, 2013 at 04:06:01PM +0900, Simon Horman wrote:
> On Wed, Jan 09, 2013 at 11:36:38AM +0900, Simon Horman wrote:
> > On Wed, Jan 09, 2013 at 01:52:20AM +0100, Laurent Pinchart wrote:
> > > Hello,
> > >
> > > Here's the second version of the SuperH and SH Mobile pin controllers (PFC)
> > > pinctrl and pinmux support patches. The patches are based on my previous PFC
> > > patch series ("[PATCH v4 00/81] SH pin control and GPIO rework") and are
> > > available from my git tree at
> > >
> > > git://linuxtv.org/pinchartl/fbdev.git pinmux-pinctrl
> > >
> > > The series depends on three patches from Linus Walleij that implement default
> > > pinmux configuration in the device core. This solves the bonito board issue
> > > mentioned in v1. Those patches are included in this set for convenience.
> >
> > Is "ARM: shmobile: bonito: Register pinctrl mappings for LCDC0"
> > the only patch in the series that depends on Linus's patches?
> >
> > > As the two dependencies will go to mainline through separate trees we will
> > > need coordination to push this set. It would probably be easier if it went
> > > through the mach-shmobile tree, in which case Linus' patches should go in
> > > early during the merge window. Linus, would that be fine with you ? Are your
> > > three patches included in this series ready for mainline ? If so, can you
> > > provide a stable branch that you will push ?
> >
> > The first patch "pinctrl: fix comment mistak" seems to be
> > in Linus's tree, post-3.8-rc2.
>
> In the mean time I have applied the first 3 patches to a pinmux
> branch in the renesas tree. This is intended as a temporary solution
> to provide the dependency for the rest of the series. I am happy
> to rebase on v3.8-rc3 when it is released, which should include the
> first patch, and use this as a more permanent solution if Linus is happy
> with it.
>
> I have also applied the remaining patches in the series.
>
> patch 1: pfc3 branch
> patch 2, 4, 5, 8, 8: boards branch
> patch 3, 6: soc2 branch
Sorry, the above should read:
patch 4-21: pfc3
patch 22, 23, 26, 27: boards
patch 23, 28: pfc4
patch 25, 29: soc3
> The next branch is a merge of branch and should include this entire series,
next prev parent reply other threads:[~2013-01-09 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 0:52 [PATCH v2 00/29] SH pinctrl and pinmux implementation Laurent Pinchart
2013-01-09 2:36 ` Simon Horman
2013-01-09 7:06 ` Simon Horman
2013-01-09 7:08 ` Simon Horman [this message]
2013-01-09 9:29 ` Laurent Pinchart
2013-01-09 9:34 ` Laurent Pinchart
2013-01-10 1:30 ` Simon Horman
2013-01-10 1:31 ` Simon Horman
2013-01-13 20:24 ` Linus Walleij
2013-01-15 0:35 ` Simon Horman
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=20130109070801.GA14906@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
/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).