From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
linus.walleij@linaro.org, gnurou@gmail.com,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3 3/3] mfd: wm831x: Add device tree binding document
Date: Wed, 15 Mar 2017 15:24:14 +0000 [thread overview]
Message-ID: <20170315152414.GI6986@localhost.localdomain> (raw)
In-Reply-To: <20170314145935.3wy3ximhtuhw3fgc@dell>
On Tue, Mar 14, 2017 at 02:59:35PM +0000, Lee Jones wrote:
> On Mon, 06 Mar 2017, Charles Keepax wrote:
>
> > Add a device tree binding document for the wm831x series of PMICs.
> > Currently only support for the registering the device and the GPIOs are
> > actually implemented in the driver.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> >
> > Changes since v2:
> > - Flesh the binding some more with some additional features of the device,
> > although these are not yet implemented in the code.
> >
> > Documentation/devicetree/bindings/mfd/wm831x.txt | 81 ++++++++++++++++++++++++
> > MAINTAINERS | 1 +
> > 2 files changed, 82 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/mfd/wm831x.txt
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/wm831x.txt b/Documentation/devicetree/bindings/mfd/wm831x.txt
> > new file mode 100644
> > index 0000000..680ac18
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mfd/wm831x.txt
> > @@ -0,0 +1,81 @@
> > +Cirrus Logic/Wolfson Microelectronics wm831x PMICs
> > +
> > +System PMICs with a wide range of additional features.
> > +
> > +Required properties:
> > +
> > + - compatible : One of the following chip-specific strings:
> > + "wlf,wm8310"
> > + "wlf,wm8311"
> > + "wlf,wm8312"
> > + "wlf,wm8320"
> > + "wlf,wm8321"
> > + "wlf,wm8325"
> > + "wlf,wm8326"
> > +
> > + - reg : I2C slave address when connected using I2C, chip select number
> > + when using SPI.
> > +
> > + - gpio-controller : Indicates this device is a GPIO controller.
> > + - #gpio-cells : Must be 2. The first cell is the pin number and the
> > + second cell is used to specify optional parameters (currently unused).
>
> Then why not "must be 1", if the second cell is unused?
>
I believe it is generally advised to use at least 2 cells for
GPIOs and since there is a reasonable chance someone might add
flags later seems better have it in the binding already.
> > + - interrupts : The interrupt line the /IRQ signal for the device is
> > + connected to.
>
> What's with the '/'?
Active low, but will remove.
>
> > + - interrupt-parent : The parent interrupt controller.
> > +
> > + - interrupt-controller : wm831x devices contain interrupt controllers and
> > + may provide interrupt services to other devices.
> > + - #interrupt-cells: Must be 2. The first cell is the IRQ number, and the
> > + second cell is the flags, encoded as the trigger masks from
> > + Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>
> Please use the succinct "../../" format.
Can do.
Thanks,
Charles
next prev parent reply other threads:[~2017-03-15 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 16:46 [PATCH v3 1/3] mfd: wm831x: Add basic device tree binding Charles Keepax
[not found] ` <1488818804-9406-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2017-03-06 16:46 ` [PATCH v3 2/3] gpio: wm831x: Add basic device tree support Charles Keepax
2017-03-15 9:18 ` Linus Walleij
2017-03-15 9:41 ` Charles Keepax
2017-03-06 16:46 ` [PATCH v3 3/3] mfd: wm831x: Add device tree binding document Charles Keepax
2017-03-14 14:59 ` Lee Jones
2017-03-15 15:24 ` Charles Keepax [this message]
2017-03-14 14:56 ` [PATCH v3 1/3] mfd: wm831x: Add basic device tree binding Lee Jones
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=20170315152414.GI6986@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=robh+dt@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).