From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] ARM: bcm281xx: Device Tree bindings for GPIO driver
Date: Fri, 26 Jul 2013 17:09:56 -0600 [thread overview]
Message-ID: <51F301C4.4070807@wwwdotorg.org> (raw)
In-Reply-To: <CAPdLdqmU0aw5h_KYcD-E=isC9U3mZF6fzr_GVdjUUAW4_PUD5Q@mail.gmail.com>
On 07/26/2013 04:51 PM, Markus Mayer wrote:
> On 26 July 2013 15:08, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> (CC'ing the DT bindings maintainers hence quoting the binding in full)
>>
>> On 07/26/2013 02:25 PM, Markus Mayer wrote:
>>> diff --git a/Documentation/devicetree/bindings/gpio/gpio-bcm-kona.txt b/Documentation/devicetree/bindings/gpio/gpio-bcm-kona.txt
>>> +Required properties:
>>> + - compatible: "brcm,kona-gpio"
>>> + - reg: Physical base address and length of the controller's registers.
>>> + - interrupts: The interrupt outputs from the controller.
>>
>> How many entries are required? I notice there's more than 1 in the
>> example below.
>
> You only "need" the ones you want to use, i.e. at least one. The board
> supports up to 6. I can mention as much in the description.
Isn't this a property of the SoC's IP block, not of the board?
next prev parent reply other threads:[~2013-07-26 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:25 [PATCH v3 0/3] ARM: bcm281xx: GPIO driver Markus Mayer
2013-07-26 20:25 ` [PATCH v3 1/3] ARM: bcm281xx: Add " Markus Mayer
2013-08-01 18:20 ` Sudeep KarkadaNagesha
2013-08-07 23:52 ` Markus Mayer
2013-07-26 20:25 ` [PATCH v3 2/3] ARM: bcm281xx: Device Tree bindings for " Markus Mayer
2013-07-26 22:08 ` Stephen Warren
2013-07-26 22:51 ` Markus Mayer
2013-07-26 23:09 ` Stephen Warren [this message]
2013-07-26 23:22 ` Markus Mayer
2013-07-27 0:13 ` Tim Kryger
2013-08-16 12:51 ` Linus Walleij
2013-08-19 18:41 ` Markus Mayer
2013-07-26 20:25 ` [PATCH v3 3/3] ARM: bcm281xx: Enable " Markus Mayer
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=51F301C4.4070807@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.