On Fri, Apr 01, 2016 at 01:18:23AM +0530, Laxman Dewangan wrote: > On Friday 01 April 2016 12:52 AM, Mark Brown wrote: > >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. You're saying that the device is so bad at regulating the ramp rate that it's not only failing to keep up with the desired ramp rate and capping at whatever rate but it's also doing even worse if configured for a slower rate? That's not great, it sounds like it's doing the ramp control via some sort of dead reckoning thing rather than by actually ramping the voltage it's trying to regulate like it was asked to. Is the error in the observed values a function of the capacitance that we can calcuate here?
Attachment:
signature.asc
Description: PGP signature
