linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] gpio: pxa: fix Documentation of interrupt-names property
Date: Thu, 11 Jul 2013 17:17:54 +0200	[thread overview]
Message-ID: <1373555877-29887-3-git-send-email-zonque@gmail.com> (raw)
In-Reply-To: <1373555877-29887-1-git-send-email-zonque@gmail.com>

The property name to pass names for interrupt resources is called
"interrupt-names", not "interrupt-name". Fix it to avoid further
confusion.

Signed-off-by: Daniel Mack <zonque@gmail.com>
Cc: Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>
---
 Documentation/devicetree/bindings/gpio/mrvl-gpio.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
index 9b3f1d4..6641626 100644
--- a/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
+++ b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
@@ -10,8 +10,9 @@ Required properties:
   There're three gpio interrupts in arch-pxa, and they're gpio0,
   gpio1 and gpio_mux. There're only one gpio interrupt in arch-mmp,
   gpio_mux.
-- interrupt-name : Should be the name of irq resource. Each interrupt
-  binds its interrupt-name.
+- interrupt-names : Should be the names of irq resources. Each interrupt
+  uses its own interrupt name, so there should be as many interrupt names
+  as referenced interrups.
 - interrupt-controller : Identifies the node as an interrupt controller.
 - #interrupt-cells: Specifies the number of cells needed to encode an
   interrupt source.
@@ -24,7 +25,7 @@ Example:
 		compatible = "marvell,mmp-gpio";
 		reg = <0xd4019000 0x1000>;
 		interrupts = <49>;
-		interrupt-name = "gpio_mux";
+		interrupt-names = "gpio_mux";
 		gpio-controller;
 		#gpio-cells = <1>;
 		interrupt-controller;
-- 
1.8.1.4

  parent reply	other threads:[~2013-07-11 15:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 15:17 [PATCH 0/5] Assorted patches for pxa-gpio Daniel Mack
2013-07-11 15:17 ` [PATCH 1/5] gpio: pxa: remove dead code Daniel Mack
2013-07-21 16:15   ` Linus Walleij
2013-07-22  7:14     ` Haojian Zhuang
2013-07-25  9:00       ` Daniel Mack
2013-07-25  9:30         ` Linus Walleij
     [not found]           ` <CAD6h2NRBsRZkeZnQfko0inQ=QKurqibNSq_ZnuipU5MtZW3h=Q@mail.gmail.com>
2013-07-27 14:02             ` Daniel Mack
2013-07-11 15:17 ` Daniel Mack [this message]
2013-07-21 16:16   ` [PATCH 2/5] gpio: pxa: fix Documentation of interrupt-names property Linus Walleij
2013-07-11 15:17 ` [PATCH 3/5] gpio: pxa: Documentation: provide example bindings for PXA3xx Daniel Mack
2013-08-04 14:11   ` Haojian Zhuang
2013-08-04 14:13     ` Daniel Mack
2013-07-11 15:17 ` [PATCH 4/5] ARM: pxa: fix DT auxdata for pxa3xx-gpio Daniel Mack
2013-08-11  9:51   ` Haojian Zhuang
2013-07-11 15:17 ` [PATCH 5/5] ARM: pxa: DTS: override gpio node in pxa3xx.dtsi Daniel Mack
2013-08-11  9:51   ` Haojian Zhuang

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=1373555877-29887-3-git-send-email-zonque@gmail.com \
    --to=zonque@gmail.com \
    --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).