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 Tuesday 19 April 2016 04:25 PM, Mark Brown wrote:
* PGP Signed by an unknown key

On Tue, Apr 19, 2016 at 03:31:11PM +0530, Laxman Dewangan wrote:
On Wednesday 13 April 2016 12:23 PM, Mark Brown wrote:
Possibly.  It did also occur to me last night that having a Maxim
specific property which lets you specify a raw register value to
configure in cases where the board goes out of spec (as opposed to a
time which could be left specified as the real value) might solve the
problem without being too terrible from an interface point of view,
though something that's directly obvious from the schematic would be
much better.
You appear to have ignord my suggestion above...


I was too focused on the getting the info from Maxim on this to get something in equation form. There is no way to get the deviation equation and your suggestion is only seems solution for this issue.
Thanks for evaluating/trying at your end and for valuable suggestion.

Now, for property, I will add
 maxim,ramp-delay

This is device specific ramp delay which need to be configure on device register. The platform observed delay must be provided via regulator-ramp-delay.

I will send the patch on this.

Thanks,
Laxman


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