All of lore.kernel.org
 help / color / mirror / Atom feed
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] gpio: pxa: Documentation: provide example bindings for PXA3xx
Date: Sun, 04 Aug 2013 16:13:13 +0200	[thread overview]
Message-ID: <51FE6179.5000702@gmail.com> (raw)
In-Reply-To: <CAN1soZxWPqd8c-4+=mg0TMH0-zbGv+ckT5o0Z7Q3KFxni2yd1g@mail.gmail.com>

On 04.08.2013 16:11, Haojian Zhuang wrote:
> On Thu, Jul 11, 2013 at 11:17 PM, Daniel Mack <zonque@gmail.com> wrote:
>> Add another example to describe bindings that work for PXA3xx boards.
>>
>> Signed-off-by: Daniel Mack <zonque@gmail.com>
>> ---
>>  Documentation/devicetree/bindings/gpio/mrvl-gpio.txt | 15 ++++++++++++++-
>>  1 file changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
>> index 6641626..b2afdb2 100644
>> --- a/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
>> +++ b/Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
>> @@ -19,7 +19,7 @@ Required properties:
>>  - gpio-controller : Marks the device node as a gpio controller.
>>  - #gpio-cells : Should be one.  It is the pin number.
>>
>> -Example:
>> +Example for a MMP platform:
>>
>>         gpio: gpio at d4019000 {
>>                 compatible = "marvell,mmp-gpio";
>> @@ -32,6 +32,19 @@ Example:
>>                 #interrupt-cells = <1>;
>>        };
>>
>> +Example for a PXA3xx platform:
>> +
>> +       gpio: gpio at 40e00000 {
>> +               compatible = "intel,pxa3xx-gpio";
>> +               reg = <0x40e00000 0x10000>;
>> +               interrupt-names = "gpio0", "gpio1", "gpio_mux";
>> +               interrupts = <8 9 10>;
>> +               gpio-controller;
>> +               #gpio-cells = <0x2>;
>> +               interrupt-controller;
>> +               #interrupt-cells = <0x2>;
>> +       };
>> +
>>  * Marvell Orion GPIO Controller
>>
>>  Required properties:
>> --
>> 1.8.1.4
>>
>>
> 
> Acked-by: Haojian Zhuang <haojian.zhuang@gmail.com>

Ok, great, thanks Haojian.

Linus W, 4/5 and 5/5 will be picked and merged by Haojian's tree. That
makes more sense as I have more pxa patches coming.


Thanks,
Daniel

  reply	other threads:[~2013-08-04 14:13 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 ` [PATCH 2/5] gpio: pxa: fix Documentation of interrupt-names property Daniel Mack
2013-07-21 16:16   ` 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 [this message]
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=51FE6179.5000702@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 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.