From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-sh@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>,
Magnus Damm <damm@opensource.se>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [RFC/PATCH v2 0/2] R-Car GPIO DT bindings
Date: Wed, 12 Jun 2013 00:14:49 +0200 [thread overview]
Message-ID: <3619797.0aKKBP4JP5@avalon> (raw)
In-Reply-To: <20130525012434.GA24005@verge.net.au>
Hi Simon,
On Saturday 25 May 2013 10:24:34 Simon Horman wrote:
> On Tue, May 21, 2013 at 01:40:04PM +0200, Laurent Pinchart wrote:
> > Hello,
> >
> > Here's the second version of the gpio-rcar driver DT bindings. I've tested
> > the patches on the Marzen board (r8a7779).
> >
> > Once again I'd appreciate feedback on the DT bindings. I'm particularly
> > wondering whether getting the number of lines through the gpio-ranges
> > property instead of using a dedicated #gpio-lines property as in v1 is a
> > good idea.
> >
> > Changes since v1:
> >
> > - Initialize the gpiochip dev field at probe time.
> > - Add the gpio-ranges property.
> > - Remove the #gpio-lines property. The number of lines is now passed
> > through>
> > the gpio-ranges property.
> >
> > Laurent Pinchart (2):
> > gpio-rcar: Make the platform data gpio_base field signed
> > gpio-rcar: Add DT support
> >
> > .../devicetree/bindings/gpio/renesas,gpio-rcar.txt | 52 +++++++++++++++++
> > drivers/gpio/gpio-rcar.c | 66 +++++++++++++----
> > include/linux/platform_data/gpio-rcar.h | 2 +-
> > 3 files changed, 109 insertions(+), 11 deletions(-)
> > create mode 100644
> > Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
>
> Hi Magnus,
>
> could you please review these changes?
I've received Magnus' ack face-to-face last week. I'm not sure whether that's
a proper procedure, but I'm sure he will confirm that if needed.
Could you please take the patch in your tree for v3.11 ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-06-11 22:14 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
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 [this message]
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=3619797.0aKKBP4JP5@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=damm@opensource.se \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--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).