Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior

[Laxman Dewangan]

On Wednesday 02 March 2016 10:05 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Mar 02, 2016 at 09:05:26AM +0530, Laxman Dewangan wrote:
> > On Wednesday 02 March 2016 09:08 AM, Mark Brown wrote:
> > > You're not trying to scale the value here, you're trying to replace the
> > > value because the PMIC is incapable of delivering the advertised ramp
> > > rate.  Trying to express this as a multiple of the advertised ramp rate
> > > is just adding complexity.
> > So should we provide absolute ramp value here for platform specific?
> Yes, otherwise if the PMIC vendor respecifies their ramp rates to
> reflect reality and the driver is updated then your DT will be broken.

Then can we have other member for pmic ramp time register configuration 
via DT.
So measured value on platform will be existing ramp-delay and the value 
which will be configured in PMIC will be via pmic-ramp-delay if provided 
otherwise use ramp-delay.