Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753105AbcCBDiy (ORCPT ); Tue, 1 Mar 2016 22:38:54 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:51166 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582AbcCBDix (ORCPT ); Tue, 1 Mar 2016 22:38:53 -0500 Date: Wed, 2 Mar 2016 12:38:33 +0900 From: Mark Brown To: Laxman Dewangan Cc: Bjorn Andersson , robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, lgirdwood@gmail.com, bjorn.andersson@sonymobile.com, swarren@wwwdotorg.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Message-ID: <20160302033833.GV18327@sirena.org.uk> References: <1456756829-2277-1-git-send-email-ldewangan@nvidia.com> <20160229174751.GQ21240@tuxbot> <20160301022326.GC18327@sirena.org.uk> <56D5111E.6090606@nvidia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Xzmf5to6u68F9h9L" Content-Disposition: inline In-Reply-To: <56D5111E.6090606@nvidia.com> X-Cookie: Adapt. Enjoy. Survive. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 122.212.32.58 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1533 Lines: 43 --Xzmf5to6u68F9h9L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --Xzmf5to6u68F9h9L Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW1mA4AAoJECTWi3JdVIfQ3D4H/jEdX5YUnyEfNU0AWxRh7XAX 9R4H+hULBvJ1XyIpcqCaZHitrvTRQvlErBaHszPL6RPW9sVOMxzquOyj8q0J+MM2 UszR34/Dr0+vvYBTdX25F2MRnDCjsmLKOqvKMQXug1HaQ91x3cVOl8reqta06bMP 9ChV9uqtXJ4Tf30/y3nglkhzMRSSP3HZN4FaTwjanJQLAzj67XXImt4YbuxqYf+V PrSAU8tA4y4xhArtd1kWI7LsHeX1f0+ILqai8eoq2nfDWi51GIXqqJfIQi/GSVtd f7ZKfYa1OE6ElrOzYHCNaMcmFa7dpmlVcY5+3qY+CI783QRrOBgiTS0Met4RxwE= =FbhF -----END PGP SIGNATURE----- --Xzmf5to6u68F9h9L--