linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vijay Kumar <vijaykumar@zilogic.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: linux-gpio@vger.kernel.org
Subject: [PATCH] Fix no. of gpio cells in the pxa gpio binding doucmentation
Date: Mon, 05 Sep 2016 11:50:40 +0530	[thread overview]
Message-ID: <57CD0EB8.1030500@zilogic.com> (raw)

Fix the no. of gpio cells in pxa gpio binding documentation.

The no. of gpio cells for the pxa gpio is actually 2. But is
incorrectly specified as 1, in the binding documentation. From the
driver code, the second cell specifies the standard flags as described
in gpio.txt.

Signed-off-by: Vijay Kumar B. <vijaykumar@zilogic.com>

Index: linux-4.7.1/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
===================================================================
--- linux-4.7.1.orig/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
+++ linux-4.7.1/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
@@ -17,7 +17,9 @@ Required properties:
  - #interrupt-cells: Specifies the number of cells needed to encode an
    interrupt source.
  - gpio-controller : Marks the device node as a gpio controller.
-- #gpio-cells : Should be one.  It is the pin number.
+- #gpio-cells : Should be two.  The first cell is the pin number and
+  the second cell is used to specify flags. See gpio.txt for possible
+  values.
  
  Example for a MMP platform:
  
@@ -27,7 +29,7 @@ Example for a MMP platform:
  		interrupts = <49>;
  		interrupt-names = "gpio_mux";
  		gpio-controller;
-		#gpio-cells = <1>;
+		#gpio-cells = <2>;
  		interrupt-controller;
  		#interrupt-cells = <1>;
        };

             reply	other threads:[~2016-09-05  6:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  6:20 Vijay Kumar [this message]
2016-09-18 17:23 ` [PATCH] Fix no. of gpio cells in the pxa gpio binding doucmentation Robert Jarzmik

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=57CD0EB8.1030500@zilogic.com \
    --to=vijaykumar@zilogic.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=robert.jarzmik@free.fr \
    /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).