[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120511145833.GG3960@opensource.wolfsonmicro.com>
Date: Fri, 11 May 2012 15:58:34 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: grant.likely@...retlab.ca, rob.herring@...xeda.com,
linux@....linux.org.uk, lrg@...com, swarren@...dia.com,
olof@...om.net, devicetree-discuss@...ts.ozlabs.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org
Subject: Re: [PATCH V3 2/4] regulator: tps62360: add dt support
On Fri, May 11, 2012 at 12:08:43PM +0530, Laxman Dewangan wrote:
This looks good overall but I do have a few things with the binding.
> +Optional properties:
> +- ti,enable-force-pwm: Enable force PWM mode. This is boolean value.
Hrm, this is fairly generic - it's REGULATOR_MODE_ACTIVE. But I'm a bit
unsure about how generic exposing it is in bindings since it's often
dynamic in the running system, we've really not got any mainline
examples of something setting a mode. With modern regulators the mode
detection stuff in the hardware is generally good enough that there's no
benefit from doing this, it's suprising to actually see systems that
benefit.
> +- ti,enable-vout-discharge: Enable output discharge. This is boolean value.
This I think we should definitely add a framework feature for this and
make into a generic property, it's a very standard feature and more
normally set unconditionally.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists