[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160128232817.GH4130@sirena.org.uk>
Date: Fri, 29 Jan 2016 00:28:17 +0100
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
linus.walleij@...aro.org, gnurou@...il.com, lee.jones@...aro.org,
a.zummo@...ertech.it, alexandre.belloni@...e-electrons.com,
lgirdwood@...il.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
rtc-linux@...glegroups.com, swarren@...dia.com, treding@...dia.com,
k.kozlowski@...sung.com
Subject: Re: [PATCH V6 7/8] DT: regulator: add DT binding doc for regulator
of PMIC max77620/max20024
On Thu, Jan 28, 2016 at 07:07:53PM +0530, Laxman Dewangan wrote:
> Maxim Semiconductor's PMIC MAX77620/MAX20024 has multiple
> DCDCs and LDOs.
Please use subject lines matching the style for the subsystem. I'm
fairly sure I've mentioned this before and really if your subject lines
don't visually resemble anything else in the directory that ought to be
a warning sign.
> +- maxim,disable-active-discharge: boolean, Disable active discharge.
That's something I've seen other regulators do, can we make it a
standard property with an op?
> +max77620@3c {
> + regulators {
> + in-ldo0-1-supply = <&max77620_sd2>;
> + in-ldo7-8-supply = <&max77620_sd2>;
I'd expect any supplies for the device to be at the device level,
including supplies used by regulators.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists