From mboxrd@z Thu Jan 1 00:00:00 1970 From: Masahiro Yamada Subject: [PATCH] Documentation: gpio: fix bindings document Date: Thu, 15 Jan 2015 17:52:40 +0900 Message-ID: <1421311960-4120-1-git-send-email-yamada.m@jp.panasonic.com> Return-path: Sender: linux-kernel-owner@vger.kernel.org To: devicetree@vger.kernel.org Cc: Linus Walleij , Mika Westerberg , Arnd Bergmann , Alexandre Courbot , Stephen Warren , linux-gpio@vger.kernel.org, Masahiro Yamada , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Laurent Pinchart , linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org Signed-off-by: Masahiro Yamada --- 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 ::= named-gpio-range ::= '<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 -- 1.9.1