From: Linus Walleij <linus.walleij@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC/PATCH v2 2/2] gpio-rcar: Add DT support
Date: Thu, 30 May 2013 17:38:12 +0000 [thread overview]
Message-ID: <CACRpkdb8GYpx3ASzXB7HX5oEpAUBe-yBo0N5Ep9S+DqoE6oCLw@mail.gmail.com> (raw)
In-Reply-To: <1369136406-23800-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Tue, May 21, 2013 at 1:40 PM, Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> Add DT bindings for the gpio-rcar driver and read the device
> configuration from the DT node at probe time if available.
>
> Cc: devicetree-discuss@lists.ozlabs.org
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
I am assuming this will go through Simon's tree?
Note:
> + - gpio-ranges: Range of pins managed by the GPIO controller as a 4-cells
> + tuple using the following syntax.
> +
> + <[phandle of the pin controller node]
> + 0
> + [index of the first pin]
> + [number of pins]>
> +
> +Please refer to gpio.txt in this directory for details of the common GPIO
> +bindings used by client devices.
The above ranges are part of that document.
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-05-30 17:38 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 [this message]
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
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=CACRpkdb8GYpx3ASzXB7HX5oEpAUBe-yBo0N5Ep9S+DqoE6oCLw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).