From: Linus Walleij <linus.walleij@linaro.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Magnus Damm <damm@opensource.se>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [RFC/PATCH v2 2/2] gpio-rcar: Add DT support
Date: Fri, 31 May 2013 09:01:44 +0200 [thread overview]
Message-ID: <CACRpkda4rRWcVkdGPcSvJeQq_KaJE5uxD+0P62Ot8=Xuf2-B+A@mail.gmail.com> (raw)
In-Reply-To: <4678059.RuWR6CiQ8n@avalon>
On Fri, May 31, 2013 at 3:20 AM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> I've so far pushed GPIO and pinctrl patches for SH through Simon's tree due to
> the many cross-dependencies between SH arch code and the GPIO and pinctrl
> drivers. As the situation now stabilizes, we could now push the patches
> through their respective subsystem trees.
>
> Simon, Linus, any opinion/preference on that ?
Depends, if they are still large patch sets I'd prefer Simon to
take it, but once the drivers are in place and going to maintenance
mode I'll handle them in pinctrl.
>> The above ranges are part of that document.
>
> What about replacing that with
>
> - gpio-ranges: Range of pins managed by the GPIO controller.
>
> Please refer to gpio.txt in this directory for details of gpio-ranges property
> and the common GPIO bindings used by client devices.
Go for it!
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-05-31 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 11:40 [RFC/PATCH v2 0/2] R-Car GPIO DT bindings Laurent Pinchart
2013-05-21 11:40 ` [RFC/PATCH v2 1/2] gpio-rcar: Make the platform data gpio_base field signed Laurent Pinchart
2013-05-23 1:39 ` Simon Horman
2013-05-21 11:40 ` [RFC/PATCH v2 2/2] gpio-rcar: Add DT support Laurent Pinchart
2013-05-30 17:38 ` Linus Walleij
[not found] ` <CACRpkdb8GYpx3ASzXB7HX5oEpAUBe-yBo0N5Ep9S+DqoE6oCLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-31 1:20 ` Laurent Pinchart
2013-05-31 7:01 ` Linus Walleij [this message]
2013-05-31 7:32 ` Laurent Pinchart
2013-06-12 11:49 ` Grant Likely
2013-06-13 17:08 ` Laurent Pinchart
2013-05-25 1:24 ` [RFC/PATCH v2 0/2] R-Car GPIO DT bindings Simon Horman
2013-06-11 22:14 ` Laurent Pinchart
2013-06-12 1:51 ` Simon Horman
2013-06-12 14:09 ` 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='CACRpkda4rRWcVkdGPcSvJeQq_KaJE5uxD+0P62Ot8=Xuf2-B+A@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=damm@opensource.se \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).