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 Friday 01 April 2016 12:52 AM, Mark Brown wrote:
* PGP Signed by an unknown key

On Fri, Apr 01, 2016 at 12:29:05AM +0530, Laxman Dewangan wrote:
On Friday 01 April 2016 12:29 AM, Mark Brown wrote:
But here is the stuff without typo ;-)
Device supports 5mV/us and 100mV/us which is not in observed value.
So why doesn't the device end up configuring 100mV/us when asked for
50mv/us?  That's reasonably expected - the configured ramp rate is a
maximum rate given that this is used to limit inrush current.



We did this to adjust device configuration to nearest higher side but this is not working well on some of cases.

On same device, DCDC (SD) rails support 4 ramp configurations, 13.75mV/us, 27.5mV/us, 55mV/us and 100mV/us.

HW team measured the ramp time at 7.5mV/us when device configured at 27.5mV/uS.

So as per above, it will be adjusted to 13.75mV/us (nearest higher side) for device configuration but this device need to configure for 27.5mV/us.

--
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