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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Thursday 31 March 2016 10:21 PM, Mark Brown wrote:
* PGP Signed by an unknown key

On Thu, Mar 31, 2016 at 12:36:08PM +0530, Laxman Dewangan wrote:
On Wednesday 30 March 2016 11:46 PM, Mark Brown wrote:
Like to add property as "regulator-device-ramp-delay" which will be used for
PMIC configuration and regulator-ramp-delay will be used for delay
calculation. This is case when advertised ramp delay does not match with the
platform measured ramp delay.
Why -device?
This is device specific and just to differentiate with regulator-ramp-delay
which is the platform specific.
May be there is some other good name. I can think of other name as
regulator-typical-ramp-delay, regulator-advertised-ramp-delay etc.
So there's already a property you want to set, why are you not trying to
set that property?

We need two properties, one what we measured in platform and second one for what we want to program PMIC. This is for the case where vendor advertised ramp delay is not same as measured due to platform design. Based on discussion, regulator-ramp-delay is for measured ramp delay in platform. So we will need another property for configuring PMIC.


--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux