[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160315144822.GP2566@sirena.org.uk>
Date: Tue, 15 Mar 2016 14:48:22 +0000
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: Bjorn Andersson <bjorn.andersson@...aro.org>, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, lgirdwood@...il.com,
bjorn.andersson@...ymobile.com, swarren@...dotorg.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Gandhar Dighe <gdighe@...dia.com>,
Stuart Yates <syates@...dia.com>
Subject: Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based
on platform behavior
On Tue, Mar 15, 2016 at 07:11:23PM +0530, Laxman Dewangan wrote:
> So here we will need two parameters:
> advertised-ramp-delay for PMIC configurations and
> ramp-delay which is measured one.
> Most of time, advertised-ramp-delay is same as ramp-delay and hence one
> value from DT will be sufficient.
> If there is difference then both value can be provided and
> advertised-ramp-delay will be used for PMIC configuration and rest of
> calculation about delay will be from ramp-delay.
This sounds more like the difference between typical and maximum spec
values than anything else, we are looking for maxima in Linux.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists