linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: mturquette@baylibre.com, robh+dt@kernel.org,
	mark.rutland@arm.com, lgirdwood@gmail.com, broonie@kernel.org,
	mazziesaccount@gmail.com, arnd@arndb.de,
	dmitry.torokhov@gmail.com, sre@kernel.org, chenjh@rock-chips.com,
	andrew.smirnov@gmail.com, linus.walleij@linaro.org,
	kstewart@linuxfoundation.org, heiko@sntech.de,
	gregkh@linuxfoundation.org, eballetbo@gmail.com,
	sboyd@kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com,
	heikki.haikola@fi.rohmeurope.com
Subject: Re: [PATCH v9 2/2] mfd: bd71837: Devicetree bindings for ROHM BD71837 PMIC
Date: Thu, 5 Jul 2018 13:39:19 +0300	[thread overview]
Message-ID: <20180705103919.GB8426@localhost.localdomain> (raw)
In-Reply-To: <20180705092444.GL496@dell>

And thanks again Lee!

On Thu, Jul 05, 2018 at 10:24:44AM +0100, Lee Jones wrote:
> On Thu, 05 Jul 2018, Matti Vaittinen wrote:
> 
> > Document devicetree bindings for ROHM BD71837 PMIC MFD.
> > 
> > Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> > Reviewed-by: Rob Herring <robh@kernel.org>
> > ---
> >  .../devicetree/bindings/mfd/rohm,bd71837-pmic.txt  | 67 ++++++++++++++++++++++
> >  1 file changed, 67 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
> > 
> > diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
> > new file mode 100644
> > index 000000000000..67f2616288d9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
> > @@ -0,0 +1,67 @@
> > +* ROHM BD71837 Power Management Integrated Circuit bindings
> > +
> > +BD71837MWV is a programmable Power Management IC for powering single-core,
> > +dual-core, and quad-core SoC’s such as NXP-i.MX 8M. It is optimized for
> 
> Nit: s/SOC's/SOCs/

I'll change this.

> > +low BOM cost and compact solution footprint. It integrates 8 Buck
> > +egulators and 7 LDO’s to provide all the power rails required by the SoC and
> 
> Nit: s/LDO's/LDOs/

I'll change this.

> > +the commonly used peripherals.
> > +
> > +Datasheet for PMIC is available at:
> > +https://www.rohm.com/datasheet/BD71837MWV/bd71837mwv-e
> > +
> > +Required properties:
> > + - compatible		: Should be "rohm,bd71837".
> > + - reg			: I2C slave address.
> > + - interrupt-parent	: Phandle to the parent interrupt controller.
> > + - interrupts		: The interrupt line the device is connected to.
> > + - clocks		: The parent clock connected to PMIC. If this is missng
> 
> s/missng/missing/

I'll change this.

> > +			  32768 KHz clock is assumed.
> > + - #clock-cells		: Should be 0
> > + - regulators:		: List of child nodes that specify the regulators
> 
> By your convention, the bottom two entries are missing '.'s.

I'll change this.

> > +			  Please see ../regulator/rohm,bd71837-regulator.txt
> > +
> > +Optional properties:
> > +- clock-output-names	: Should contain name for output clock.
> > +
> > +Example:
> > +
> > +	/* external oscillator node */
> 
> Uppercase character to start a sentence.

I'll change this.

> > +	osc: oscillator {
> > +		compatible = "fixed-clock";
> > +		#clock-cells = <1>;
> > +		clock-frequency  = <32768>;
> > +		clock-output-names = "osc";
> > +	};
> > +
> > +	/* PMIC node */
> 
> Is this comment really necessary?  The node is called "pmic".

I'll remove this.

> > +	pmic: pmic@4b {
> > +		compatible = "rohm,bd71837";
> > +		reg = <0x4b>;
> > +		interrupt-parent = <&gpio1>;
> > +		interrupts = <29 GPIO_ACTIVE_LOW>;
> > +		interrupt-names = "irq";
> > +		#clock-cells = <0>;
> > +		clocks = <&osc 0>;
> > +		clock-output-names = "bd71837-32k-out";
> > +
> > +		regulators {
> > +			buck1: BUCK1 {
> > +				regulator-name = "buck1";
> > +				regulator-min-microvolt = <700000>;
> > +				regulator-max-microvolt = <1300000>;
> > +				regulator-boot-on;
> > +				regulator-ramp-delay = <1250>;
> > +			};
> > +			/* ... */
> > +		};
> > +	};
> > +
> > +	/* Clock consumer node */
> > +
> > +	foo@0 {
> > +		compatible = "bar,foo";
> > +		/* ... */
> 
> No need for this line.  Additional properties are always expected.

I'll remove this.

> > +		clock-names = "my-clock";
> > +		clocks = <&pmic>;
> > +	};
> 
> Do you have a real example to give?

For clock consumer? Sorry, no I don't.

Br,
	Matti Vaittinen

> -- 
> Lee Jones [李琼斯]
> Linaro Services Technical Lead
> Linaro.org │ Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2018-07-05 10:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  7:45 [PATCH v9 0/2] mfd/regulator/clk/input: bd71837: ROHM BD71837 PMIC driver Matti Vaittinen
2018-07-05  7:46 ` [PATCH v9 1/2] mfd: bd71837: mfd driver for ROHM BD71837 PMIC Matti Vaittinen
2018-07-05  8:04   ` Enric Balletbo Serra
2018-07-05  9:18   ` Lee Jones
2018-07-05 10:34     ` Matti Vaittinen
2018-07-05 11:17       ` Lee Jones
2018-07-05 12:29         ` Matti Vaittinen
2018-07-05 12:51           ` Lee Jones
2018-07-05  7:48 ` [PATCH v9 2/2] mfd: bd71837: Devicetree bindings " Matti Vaittinen
2018-07-05  9:24   ` Lee Jones
2018-07-05 10:39     ` Matti Vaittinen [this message]
2018-07-05 10:49       ` Lee Jones
2018-07-05 11:51         ` Matti Vaittinen
2018-07-05 12:44           ` 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=20180705103919.GB8426@localhost.localdomain \
    --to=matti.vaittinen@fi.rohmeurope.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=chenjh@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eballetbo@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.haikola@fi.rohmeurope.com \
    --cc=heiko@sntech.de \
    --cc=kstewart@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mikko.mutanen@fi.rohmeurope.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sre@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).