From: Lukas Wunner <lukas@wunner.de>
To: Rob Herring <robh@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Mathias Duckeck <m.duckeck@kunbus.de>,
Phil Elwell <phil@raspberrypi.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 3/4] dt-bindings: gpio: max3191x: Document new driver
Date: Wed, 4 Oct 2017 21:31:53 +0200 [thread overview]
Message-ID: <20171004193153.GA9195@wunner.de> (raw)
In-Reply-To: <20170905081624.GA15374@wunner.de>
Hi Rob,
gentle ping on this question:
On Tue, Sep 05, 2017 at 10:16:24AM +0200, Lukas Wunner wrote:
> Hi Rob,
>
> sorry to bother you again, one more question popped up regarding the
> MAX3191x DT bindings:
>
> On Tue, Aug 22, 2017 at 07:48:47PM -0500, Rob Herring wrote:
> > On Mon, Aug 21, 2017 at 03:12:00PM +0200, Lukas Wunner wrote:
> > > Add device tree bindings for Maxim MAX3191x industrial serializer.
> [snip]
> > > +Optional properties:
> > > + - maxim,nchips: Number of chips in the daisy-chain (default is 1).
>
> Many I/O chips are daisy-chainable, so I've been wondering if a
> common property should be introduced?
>
> The existing gpio-74x164.c uses "registers-number" to convey the number
> of chips in the daisy chain. (Sans vendor prefix, multiple vendors sell
> compatible versions of this chip.)
>
> gpio-pisosr.c takes a different approach and calculates the number of
> chips in the daisy-chain by taking the common "ngpios" property
> (Documentation/devicetree/bindings/gpio/gpio.txt) and dividing it by 8
> (which assumes that each chip has 8 inputs).
>
> Thanks,
>
> Lukas
prev parent reply other threads:[~2017-10-04 19:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 13:12 [PATCH 0/4] GPIO driver for Maxim MAX3191x Lukas Wunner
2017-08-21 13:12 ` [PATCH 4/4] gpio: Add driver for Maxim MAX3191x industrial serializer Lukas Wunner
[not found] ` <df530ae703fcfdf52d27a1b6d19b6d1a4724b103.1503319573.git.lukas-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-08-23 8:09 ` Linus Walleij
2017-08-21 13:12 ` [PATCH 1/4] bitops: Introduce assign_bit() Lukas Wunner
2017-08-21 16:18 ` Bart Van Assche
2017-08-22 8:30 ` Lukas Wunner
2017-08-22 9:27 ` Peter Zijlstra
2017-08-22 10:04 ` Lukas Wunner
2017-08-23 7:32 ` Linus Walleij
2017-08-23 17:09 ` Bart Van Assche
2017-08-24 19:52 ` Linus Walleij
2017-08-21 13:12 ` [PATCH 2/4] gpio: Introduce ->get_multiple callback Lukas Wunner
2017-08-23 7:38 ` Linus Walleij
2017-08-27 17:34 ` Lukas Wunner
2017-08-31 13:48 ` Linus Walleij
2017-08-31 15:46 ` Lukas Wunner
2017-09-03 14:58 ` Linus Walleij
2017-10-04 20:32 ` Lukas Wunner
2017-10-07 11:23 ` Linus Walleij
2017-10-12 11:15 ` Lukas Wunner
2017-08-21 13:12 ` [PATCH 3/4] dt-bindings: gpio: max3191x: Document new driver Lukas Wunner
2017-08-23 0:48 ` Rob Herring
2017-08-23 9:44 ` Lukas Wunner
[not found] ` <20170823094438.GA12416-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-08-23 13:03 ` Rob Herring
2017-09-05 8:16 ` Lukas Wunner
2017-10-04 19:31 ` Lukas Wunner [this message]
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=20171004193153.GA9195@wunner.de \
--to=lukas@wunner.de \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=m.duckeck@kunbus.de \
--cc=mark.rutland@arm.com \
--cc=phil@raspberrypi.org \
--cc=robh@kernel.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).