All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH/RFC 1/3] pinctrl: sh-pfc: support sparse GPIO numbers
Date: Thu, 14 Feb 2013 12:23:53 +0000	[thread overview]
Message-ID: <3026499.H7lrtqOphq@avalon> (raw)
In-Reply-To: <1360684204-12888-2-git-send-email-g.liakhovetski@gmx.de>

Hi Linus,

On Thursday 14 February 2013 13:10:11 Linus Walleij wrote:
> On Wed, Feb 13, 2013 at 5:31 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, Feb 12, 2013 at 04:50:02PM +0100, Guennadi Liakhovetski wrote:
> >> Not on all sh-/r-mobile platfotms all pins are numbered contiguously from
> >> 0
> >> to N-1. On all ARM-based platforms datasheets use simple numbers to
> >> identify them, unlike some SuperH-based SoC, naming pins, using strings,
> >> e.g. A31:A0, B11:B0, C31:C0, etc. So far the sg-pfc pinctrl driver
> >> supported only contiguous pin numbering. This patch adds support for
> >> sparse pin numbers to support sh73a0 and any other similar SoCs.
> > 
> > Applied to a new topic branch, topic/pinmux-sparse.
> 
> Are you taking these patches forward Simon?
> 
> I basically trust you guys so:
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> 
> Though since Laurent wrote the bulk of this I'd prefer that he also ACK it.

Just to clarify the situation, Simon took the patches in his tree to provide a 
central repository where everybody can get them, but I'm still responsible for 
the PFC driver (at least for now). I'm working on a new version of those 
patches that will supersede all Simon's topic/pinmux-* branches. There's thus 
no need for you to handle the patches for now (review is of course welcome 
:-)).

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2013-02-14 12:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 15:50 [PATCH/RFC 1/3] pinctrl: sh-pfc: support sparse GPIO numbers Guennadi Liakhovetski
2013-02-13  4:31 ` Simon Horman
2013-02-14 11:55 ` Paul Mundt
2013-02-14 12:09 ` Laurent Pinchart
2013-02-14 12:10 ` Linus Walleij
2013-02-14 12:23 ` Laurent Pinchart [this message]
2013-02-14 12:38 ` Paul Mundt
2013-02-14 14:23 ` Laurent Pinchart
2013-02-14 15:26 ` Laurent Pinchart

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=3026499.H7lrtqOphq@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --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 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.