From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/04] ARM: shmobile: r8a73a4 SoC support V3
Date: Wed, 27 Mar 2013 20:45:54 +0900 [thread overview]
Message-ID: <20130327114553.GA9420@verge.net.au> (raw)
In-Reply-To: <CANqRtoTp-Bx7EVQioekmJZJs5qUCoq=CX6CtukbEHp22RR_goA@mail.gmail.com>
On Wed, Mar 27, 2013 at 05:19:55PM +0900, Magnus Damm wrote:
> On Wed, Mar 27, 2013 at 12:46 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, Mar 26, 2013 at 11:17:43PM +0900, Magnus Damm wrote:
> >> On Tue, Mar 26, 2013 at 8:48 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> > On Tuesday 26 March 2013, Magnus Damm wrote:
> >> >> ARM: shmobile: r8a73a4 SoC support V3
> >> >> [PATCH 01/04] ARM: shmobile: Initial r8a73a4 SoC support V3
> >> >> [PATCH 02/04] ARM: shmobile: r8a73a4 SCIF support V3
> >> >> [PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support V2
> >> >> [PATCH 04/04] ARM: shmobile: r8a73a4 PFC support
> >> >>
> >> >> This series is V3 of initial support for the r8a73a4 SoC. The SoC
> >> >> is known as r8a73a4 which is built around Cortex-A15 and makes use
> >> >> of SCIF for serial, IRQC interrupt controller for external IRQs and
> >> >> PFC for combined support for pinmux and GPIO.
> >> >>
> >> >
> >> > Acked-by: Arnd Bergmann <arnd@arndb.de>
> >>
> >> Thanks for your help!
> >
> > Indeed.
> >
> > Magnus, please let me know if/when you would like me to queue-up these
> > patches.
>
> Thanks. Since you bring up the topic, I'd like you to queue up this
> patch series more or less right away if possible. =)
Sure, I think it is possible.
> About how to handle the dependencies, I am not sure if you intend to
> keep the SoC bits separate from the PFC and the board code. It is
> possible to split it out by series but if that is needed or not
> depends on how the ARM SoC guys want to be fed.
I would prefer if they were separated out so that I can apply
them to separate branches, in keeping with arm-soc requirements.
The branches can depend on each other which is how any dependencies
can be handled.
At this point I am thinking of merging the soc branch, with this
series added, into the pinmux branch and then applying the r8a73a4 pfc
patches to the result.
> Regardless, this r8a73a4 SoC V3 series depends on the following patch
> to compile:
> [PATCH/RFC] ARM: shmobile: Disallow PINCTRL without GPIOLIB
>
> Laurent seems OK with the patch above, how about you? I am quite OK
> with the above patch as a short term fix. But I believe Linus W and
> Laurent at some point need to decide if it is valid to have PINCTL
> selected without GPIO.
I think I will take it into my tree as this series relies on it.
next prev parent reply other threads:[~2013-03-27 11:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 1:34 [PATCH 00/04] ARM: shmobile: r8a73a4 SoC support V3 Magnus Damm
2013-03-26 1:34 ` [PATCH 01/04] ARM: shmobile: Initial " Magnus Damm
2013-03-26 1:34 ` [PATCH 02/04] ARM: shmobile: r8a73a4 SCIF " Magnus Damm
2013-03-26 1:34 ` [PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support V2 Magnus Damm
2013-03-26 1:34 ` [PATCH 04/04] ARM: shmobile: r8a73a4 PFC support Magnus Damm
2013-03-26 6:17 ` [PATCH 0/1] ARM: shmobile: r8a73a4 thermal support Kuninori Morimoto
2013-03-26 6:18 ` [PATCH] ARM: shmobile: r8a73a4: add thermal driver support Kuninori Morimoto
2013-03-27 5:17 ` Simon Horman
2013-03-27 9:19 ` Magnus Damm
2013-03-27 12:11 ` Simon Horman
2013-03-27 5:21 ` [PATCH 0/1] ARM: shmobile: r8a73a4 thermal support Simon Horman
2013-03-27 7:49 ` Kuninori Morimoto
2013-03-27 9:17 ` Magnus Damm
2013-03-27 12:09 ` Simon Horman
2013-03-27 12:10 ` Simon Horman
2013-03-26 11:48 ` [PATCH 00/04] ARM: shmobile: r8a73a4 SoC support V3 Arnd Bergmann
2013-03-26 14:17 ` Magnus Damm
2013-03-27 3:46 ` Simon Horman
2013-03-27 8:19 ` Magnus Damm
2013-03-27 11:45 ` Simon Horman [this message]
2013-03-27 12:01 ` Simon Horman
2013-03-27 16:37 ` Magnus Damm
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=20130327114553.GA9420@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).