From: Thierry Reding <thierry.reding@avionic-design.de>
To: Rob Herring <robherring2@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linus Walleij <linus.walleij@stericsson.com>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH v2] gpio: Add Avionic Design N-bit GPIO expander support
Date: Thu, 2 Aug 2012 08:18:37 +0200 [thread overview]
Message-ID: <20120802061837.GF12241@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <50185619.5090706@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
On Tue, Jul 31, 2012 at 05:03:05PM -0500, Rob Herring wrote:
> For nr-gpios, I think it is typically not needed. Generally, you will
> know how many gpio lines the h/w has based on the compatible string. If
> this part really is the same part but different packages with different
> numbers of gpio, then this property makes sense.
That's exactly what I need it for. The controller is synthesized in a
CPLD, so technically the part is always the same, but the configured
logic can implement any number of GPIOs.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-02 6:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 11:59 [PATCH v2] gpio: Add Avionic Design N-bit GPIO expander support Thierry Reding
2012-07-29 17:13 ` Linus Walleij
2012-07-29 20:27 ` Arnd Bergmann
2012-07-30 7:47 ` Thierry Reding
2012-07-31 22:03 ` Rob Herring
2012-07-31 23:22 ` Stephen Warren
2012-08-02 6:18 ` Thierry Reding [this message]
2012-08-05 10:50 ` Linus Walleij
2012-08-06 5:11 ` Thierry Reding
2012-08-06 6:39 ` Linus Walleij
2012-08-09 6:27 ` Thierry Reding
2012-08-09 20:20 ` Thierry Reding
2012-08-10 8:19 ` Linus Walleij
2012-08-10 8:35 ` Thierry Reding
2012-08-10 8:41 ` Linus Walleij
2012-08-10 8:48 ` Thierry Reding
2012-08-10 9:15 ` Russell King - ARM Linux
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=20120802061837.GF12241@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=w.sang@pengutronix.de \
/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).