From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Rob Herring <robherring2@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Alexandre Courbot <acourbot@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: gpio: fix bindings document
Date: Fri, 16 Jan 2015 10:20:56 +0900 [thread overview]
Message-ID: <20150116102056.F108.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <2479604.mfbgZIQjOA@avalon>
Hi Laurent, Rob,
On Thu, 15 Jan 2015 16:10:54 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> Hi Rob,
>
> On Thursday 15 January 2015 08:07:18 Rob Herring wrote:
> > On Thu, Jan 15, 2015 at 2:52 AM, Masahiro Yamada
> >
> > <yamada.m@jp.panasonic.com> wrote:
> > > Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> >
> > Perhaps some explanation. You can't just remove properties. Please
> > explain to what extent the old/wrong name is used. This patch is only
> > okay if there are no users of gpio-phandle.
>
> As far as I understand the patch just fixes a typo. There has never been a
> gpio-phandle for GPIO controllers, only for GPIO consumers.
Yes, this patch just fixes typos.
I thought I could be lazy here...
> > > ---
> > >
> > > Documentation/devicetree/bindings/gpio/gpio.txt | 5 +++--
> > > 1 file changed, 3 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt
> > > b/Documentation/devicetree/bindings/gpio/gpio.txt index b9bd1d6..f7a158d
> > > 100644
> > > --- a/Documentation/devicetree/bindings/gpio/gpio.txt
> > > +++ b/Documentation/devicetree/bindings/gpio/gpio.txt
> > > @@ -69,7 +69,8 @@ GPIO pin number, and GPIO flags as accepted by the
> > > "qe_pio_e" gpio-controller.>
> > > ----------------------------------
> > >
> > > A gpio-specifier should contain a flag indicating the GPIO polarity;
> > > active->
> > > -high or active-low. If it does, the follow best practices should be
> > > followed: +high or active-low. If it does, the following best practices
> > > should be>
> > > +followed:
> > > The gpio-specifier's polarity flag should represent the physical level at
> > > the GPIO controller that achieves (or represents, for inputs) a
> > > logically asserted>
> > > @@ -147,7 +148,7 @@ contains information structures as follows:
> > > numeric-gpio-range ::=
> > >
> > > <pinctrl-phandle> <gpio-base> <pinctrl-base>
> > > <count>
> > >
> > > named-gpio-range ::= <pinctrl-phandle> <gpio-base> '<0 0>'
> > >
> > > - gpio-phandle : phandle to pin controller node.
> > > + pinctrl-phandle : phandle to pin controller node
> > >
> > > gpio-base : Base GPIO ID in the GPIO controller
> > > pinctrl-base : Base pinctrl pin ID in the pin controller
> > > count : The number of GPIOs/pins in this range
>
> --
> Regards,
>
> Laurent Pinchart
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-01-16 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 8:52 [PATCH] Documentation: gpio: fix bindings document Masahiro Yamada
2015-01-15 14:00 ` Laurent Pinchart
2015-01-15 14:07 ` Rob Herring
2015-01-15 14:10 ` Laurent Pinchart
2015-01-16 1:20 ` Masahiro Yamada [this message]
2015-01-19 10:34 ` 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=20150116102056.F108.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=swarren@nvidia.com \
/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