From: Lee Jones <lee.jones@linaro.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Mark Brown <broonie@kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Documentation: tps65086: Add DT bindings for the TPS65086 PMIC
Date: Tue, 20 Oct 2015 12:31:28 +0100 [thread overview]
Message-ID: <20151020113128.GN31804@x1> (raw)
In-Reply-To: <56250AF9.3030907@ti.com>
On Mon, 19 Oct 2015, Andrew F. Davis wrote:
> On 10/19/2015 10:21 AM, Lee Jones wrote:
> >On Mon, 19 Oct 2015, Andrew F. Davis wrote:
> >
> >>On 10/19/2015 04:13 AM, Lee Jones wrote:
> >>>On Fri, 16 Oct 2015, Andrew F. Davis wrote:
> >>>
> >>>>The TPS65086 PMIC contains several regulators and a GPO controller.
> >>>>Add bindings for the TPS65086 PMIC.
> >>>>
> >>>>Signed-off-by: Andrew F. Davis <afd@ti.com>
> >>>>---
> >>>> .../devicetree/bindings/gpio/gpio-tps65086.txt | 17 ++++++++
> >>>> Documentation/devicetree/bindings/mfd/tps65086.txt | 46 ++++++++++++++++++++++
> >>>> .../bindings/regulator/tps65086-regulator.txt | 36 +++++++++++++++++
> >>>
> >>>Please split these up into separate patches.
> >>>
> >>>There is no functional reason to bundle them up.
> >>>
> >>
> >>ACK
> >>
> >>>> 3 files changed, 99 insertions(+)
> >>>> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-tps65086.txt
> >>>> create mode 100644 Documentation/devicetree/bindings/mfd/tps65086.txt
> >>>> create mode 100644 Documentation/devicetree/bindings/regulator/tps65086-regulator.txt
> >>>
> >>>[...]
> >>>
> >>>>diff --git a/Documentation/devicetree/bindings/mfd/tps65086.txt b/Documentation/devicetree/bindings/mfd/tps65086.txt
> >>>>new file mode 100644
> >>>>index 0000000..4b6aeb4
> >>>>--- /dev/null
> >>>>+++ b/Documentation/devicetree/bindings/mfd/tps65086.txt
> >>>>@@ -0,0 +1,46 @@
> >>>>+* TPS65086 Power Management Integrated Circuit bindings
> >>>>+
> >>>>+Required properties:
> >>>>+ - compatible : Should be "ti,tps65086".
> >>>
> >>>Any indication that it's a PMIC?
> >>>
> >>
> >>In the compatible string?
> >
> >Ya.
> >
>
> Not sure what you mean then?, no one else seems to be doing that,
> "xx,xxxxxxx-pmic" is usually used for matching the regulator node,
> not the device itself.
Either the driver is MFD is the PMIC or it's not.
If it is, the compatible should reflect that, if isn't not then the
description in the header comment and the one above is not correct.
IMO, 'pmic' should not be used in the regulator compatible strings, as
it's a general description of the overall device. The regulators are
just a component of that device.
> >>>>+ - reg : Slave address.
> >>>
> >>>I2C/SPI?
> >>>
> >>
> >>ACK
> >>
> >>>>+ - interrupt-parent : The parent interrupt controller.
> >>>
> >>>Phandled to ...
> >>>
> >>
> >>ACK
> >>
> >>>>+ - interrupts : The interrupt line the device is connected to.
> >>>>+ - interrupt-controller : Marks the device node as an interrupt controller.
> >>>>+ - #interrupt-cells : The number of cells to describe an IRQ, this
> >>>>+ should be 2. The first cell is the IRQ number.
> >>>>+ The second cell is the flags, encoded as the trigger
> >>>>+ masks from ../interrupt-controller/interrupts.txt.
> >>>
> >>>Masks? What masks?
> >>>
> >>>Best to make a link to the header where the flags are defined here.
> >>>
> >>
> >>ACK
> >>
> >>>>+Additional nodes defined in:
> >>>>+ - Regulators : ../regulator/tps65086-regulator.txt.
> >>>>+ - GPIO : ../gpio/gpio-tps65086.txt.
> >>>
> >>>I'd suggest removing the full stops from all of the lines above.
> >>>
> >>>Just treat them as bullet points like we normally do.
> >>>
> >>
> >>ACK
> >>
> >>>>+Example:
> >>>>+
> >>>>+ pmic: tps65086@5e {
> >>>>+ compatible = "ti,tps65086";
> >>>>+ reg = <0x5e>;
> >>>>+ interrupt-parent = <&gpio1>;
> >>>>+ interrupts = <28 IRQ_TYPE_LEVEL_LOW>;
> >>>>+ interrupt-controller;
> >>>>+ #interrupt-cells = <2>;
> >>>>+
> >>>>+ regulators {
> >>>>+ compatible = "ti,tps65086-regulator";
> >>>>+
> >>>>+ buck1 {
> >>>>+ regulator-name = "vcc1";
> >>>>+ regulator-min-microvolt = <1600000>;
> >>>>+ regulator-max-microvolt = <1600000>;
> >>>>+ regulator-boot-on;
> >>>>+ ti,regulator-decay;
> >>>>+ ti,regulator-step-size-25mv;
> >>>>+ };
> >>>>+ };
> >>>>+
> >>>>+ gpio4: tps65086_gpio {
> >>>>+ compatible = "ti,tps65086-gpio";
> >>>>+ gpio-controller;
> >>>>+ #gpio-cells = <2>;
> >>>>+ };
> >>>>+ };
> >>>
> >>>[...]
> >>>
> >>
> >
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-10-20 11:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 16:59 [PATCH 0/4] Add support for the TI TPS65086 PMIC Andrew F. Davis
2015-10-16 16:59 ` [PATCH 1/4] Documentation: tps65086: Add DT bindings for the " Andrew F. Davis
2015-10-19 9:13 ` Lee Jones
2015-10-19 15:16 ` Andrew F. Davis
2015-10-19 15:21 ` Lee Jones
2015-10-19 15:23 ` Andrew F. Davis
2015-10-20 11:31 ` Lee Jones [this message]
2015-10-20 14:02 ` Andrew F. Davis
2015-10-21 8:46 ` Lee Jones
2015-10-21 10:29 ` Mark Brown
2015-10-21 11:18 ` Lee Jones
2015-10-21 12:14 ` Mark Brown
2015-10-21 15:26 ` Lee Jones
2015-10-21 16:13 ` Mark Brown
2015-10-16 16:59 ` [PATCH 2/4] mfd: tps65086: Add driver " Andrew F. Davis
[not found] ` <1445014753-15450-3-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-10-19 9:23 ` Lee Jones
2015-10-19 16:03 ` Andrew F. Davis
2015-10-20 10:02 ` Lee Jones
2015-10-20 14:58 ` Andrew F. Davis
2015-10-21 8:43 ` Lee Jones
2015-10-21 16:28 ` Andrew F. Davis
[not found] ` <5627BD11.1000704-l0cyMroinI0@public.gmane.org>
2015-10-21 19:24 ` Lee Jones
2015-10-16 16:59 ` [PATCH 3/4] regulator: tps65086: Add regulator " Andrew F. Davis
2015-10-16 16:59 ` [PATCH 4/4] gpio: tps65086: Add GPIO " Andrew F. Davis
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=20151020113128.GN31804@x1 \
--to=lee.jones@linaro.org \
--cc=afd@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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).