SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/13 v2] sh-pfc: Initial r8a73a4 PFC support
Date: Wed, 27 Mar 2013 04:56:28 +0000	[thread overview]
Message-ID: <20130327045627.GG25431@verge.net.au> (raw)
In-Reply-To: <20130326134939.31366.42030.sendpatchset@w520>

On Tue, Mar 26, 2013 at 10:49:39PM +0900, Magnus Damm wrote:
> sh-pfc: Initial r8a73a4 PFC support (V2)
> 
> [PATCH 01/13] sh-pfc: Add r8a73a4 pinmux support
> [PATCH 02/13] sh-pfc: r8a73a4: Support sparse GPIO numbers
> [PATCH 03/13 v2] sh-pfc: r8a73a4: GPIO IRQ support
> [PATCH 04/13] sh-pfc: r8a73a4: Add bias (pull-up/down) pinconf support
> [PATCH 05/13] sh-pfc: r8a73a4: Add SCIF pin groups and functions
> [PATCH 06/13] sh-pfc: r8a73a4: Add IRQC pin groups and functions
> [PATCH 07/13] sh-pfc: r8a73a4: Remove SCIF function GPIOS
> [PATCH 08/13] sh-pfc: r8a73a4: Remove IRQC function GPIOS
> [PATCH 09/13] ARM: shmobile: r8a73a4: Remove SCIF function GPIOs
> [PATCH 10/13] ARM: shmobile: r8a73a4: Remove IRQC function GPIOs
> [PATCH 11/13] sh-pfc: r8a73a4: Remove function GPIOs
> [PATCH 12/13] ARM: shmobile: r8a73a4: Remove all GPIO enums
> [PATCH 13/13] sh-pfc: r8a73a4: Remove unused GPIO bias data
> 
> This series is V2 of initial PFC support for the r8a73a4 SoC.
> The patches add a regular old-style GPIO function controller
> and makes it partially converted over to PINCTRL for SCIF
> and IRQC that are tied up on the APE6EVM board. The final
> patches remove the GPIO function support, so when new drivers
> for r8a73a4 are added then PINCTRL support has to be included.

Hi Magnus,

I apologise if the information is obvious or available elsewhere,
but could you let me know a bit about the dependencies for this series.

I am assuming it depends on:

[PATCH 00/03 v3] ARM: shmobile: r8a73a4 APE6EVM board support
[PATCH/RFC 00/12] Split PFC and GPIO for R8A7779

Laurent, if/when this series is ready do you want to take it
or should I add it to my tree directly?

  reply	other threads:[~2013-03-27  4:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 13:49 [PATCH 00/13 v2] sh-pfc: Initial r8a73a4 PFC support Magnus Damm
2013-03-27  4:56 ` Simon Horman [this message]
2013-03-27  8:36 ` Laurent Pinchart
2013-03-27  8:48 ` Magnus Damm
2013-03-27 12:15 ` Simon Horman
2013-03-27 12:21 ` Simon Horman
2013-03-27 14:12 ` Laurent Pinchart
2013-03-28  0:54 ` 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=20130327045627.GG25431@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