[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120127111932.GC32008@opensource.wolfsonmicro.com>
Date: Fri, 27 Jan 2012 11:19:33 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Karol Lewandowski <k.lewandowsk@...sung.com>
Cc: Thomas Abraham <thomas.abraham@...aro.org>,
linux-kernel@...r.kernel.org, rpurdie@...ys.net,
rob.herring@...xeda.com, grant.likely@...retlab.ca,
kgene.kim@...sung.com, myungjoo.ham@...sung.com,
kyungmin.park@...sung.com, dg77.kim@...sung.com,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, Rajendra Nayak <rnayak@...com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>
Subject: Re: [PATCH v2 2/2] regulator: add device tree support for max8997
On Fri, Jan 27, 2012 at 10:58:08AM +0100, Karol Lewandowski wrote:
> >>On 25.01.2012 12:22, Mark Brown wrote:
> >I'm sorry, this makes no sense. Setting a value in the constraints is
> >not going to have any impact on the value reported by the driver, it
> >never has.
> ... with the exception of fixed regulator, that is. This is from
> where I got my flawed understanding.
Note also that this only happens for device tree - with platform data
there's separate platform data for the voltage.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists