From: Stephen Warren <swarren@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: linus.walleij@linaro.org, grant.likely@linaro.org,
rob.herring@calxeda.com, rob@landley.net,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
kishon@ti.com, j-keerthy@ti.com, gg@slimlogic.co.uk
Subject: Re: [PATCH V3] gpio: palmas: add dt support
Date: Mon, 22 Jul 2013 14:58:34 -0700 [thread overview]
Message-ID: <51EDAB0A.8080601@nvidia.com> (raw)
In-Reply-To: <1374469977-8805-1-git-send-email-ldewangan@nvidia.com>
On 07/21/2013 10:12 PM, Laxman Dewangan wrote:
> Add of_device_id table for Palma GPIO to be enable the
> driver from DT file.
>
> The driver can be registered from DT file as:
> palmas: tps65913@58 {
> :::::::::::
> palmas_gpio: palmas_gpio {
> compatible = "ti,palmas-gpio";
> gpio-controller;
> #gpio-cells = <2>;
> };
> };
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-palmas.txt b/Documentation/devicetree/bindings/gpio/gpio-palmas.txt
> +- #gpio-cells : Should be two.
> + - first cell is the gpio pin number
> + - second cell is used to specify optional parameters (unused)
Shouldn't the second cell contain the standard GPIO-related flags such
as bit 0 == active-low?
Aside from that, this binding and indeed the rest of the patch looks
fine to me.
next prev parent reply other threads:[~2013-07-22 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 5:12 [PATCH V3] gpio: palmas: add dt support Laxman Dewangan
2013-07-22 5:12 ` Laxman Dewangan
2013-07-22 21:58 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-05 13:26 Laxman Dewangan
2013-07-21 15:28 ` Linus Walleij
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=51EDAB0A.8080601@nvidia.com \
--to=swarren@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@linaro.org \
--cc=j-keerthy@ti.com \
--cc=kishon@ti.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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.