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 Wednesday 02 March 2016 09:08 AM, Mark Brown wrote:
* PGP Signed by an unknown key

On Tue, Mar 01, 2016 at 09:18:46AM +0530, Laxman Dewangan wrote:

HW team characterize the board and its rail and come up with the following
data:
- Configure PMIC to 27mV/us for ramp time.
- With this measured value of ramp on board is 10mV/us and it is safe to
assume 5mv/us to consider the board variations.
So we have now two input from HW team:
1. What should be configure in PMIC.
2. And for calculation, how much ramp need to be consider.
For (1), it is 25mV/us and for (2) which 540% (27 *100/5).
Currently, we can provide the 27mv/us as ramp-delay but do not have option
for scaling it.
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?
Or any other suggestion to handle this situation as this is very common and almost all our boards have this slowness on ramp.

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