Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755731AbcCOOtQ (ORCPT ); Tue, 15 Mar 2016 10:49:16 -0400 Received: from [106.187.55.193] ([106.187.55.193]:33886 "EHLO mezzanine.sirena.org.uk" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753891AbcCOOtN (ORCPT ); Tue, 15 Mar 2016 10:49:13 -0400 Date: Tue, 15 Mar 2016 14:48:22 +0000 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, Gandhar Dighe , Stuart Yates Message-ID: <20160315144822.GP2566@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> <20160302033833.GV18327@sirena.org.uk> <56D65F7E.3090907@nvidia.com> <20160302043506.GC18327@sirena.org.uk> <56E81103.8010903@nvidia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zxEKvxCKojqA/Afl" Content-Disposition: inline In-Reply-To: <56E81103.8010903@nvidia.com> X-Cookie: Walk softly and carry a megawatt laser. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 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: 1293 Lines: 36 --zxEKvxCKojqA/Afl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 15, 2016 at 07:11:23PM +0530, Laxman Dewangan wrote: > So here we will need two parameters: > advertised-ramp-delay for PMIC configurations and > ramp-delay which is measured one. > Most of time, advertised-ramp-delay is same as ramp-delay and hence one > value from DT will be sufficient. > If there is difference then both value can be provided and > advertised-ramp-delay will be used for PMIC configuration and rest of > calculation about delay will be from ramp-delay. This sounds more like the difference between typical and maximum spec values than anything else, we are looking for maxima in Linux. --zxEKvxCKojqA/Afl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW6CCvAAoJECTWi3JdVIfQiKQH/iex503K7e4ns+oVkx9uHqSJ 8be13i2grpX3DD0zfhEbLOp6xg9xkxgvHz56Z+V9NNL3F4tmA2y4dxNMzkFo1VVv nyapz1XZ7Y6lwaLiLS3l3rMc2FUwgPXxq2P4lvQvPy6A31fBthFLVl0PHwO+vRc9 8J76npZZ0Qx7jsXeltnrceTsPsa/ruNmVR9w1ri8y+mlJlENJAy2f9GpeA5EkPDI YyejMQ9j1tF8fuPeopZwU2wiL6MIXulsISqjBEAz0/PGLyE1NugAOZ2A6bItI4ye rE2S+TxJ4MWOAwjQEuc+xO4458ArCv0RH263fOiXMBuqs/emSQe5ozdMmL5HHfI= =PDmT -----END PGP SIGNATURE----- --zxEKvxCKojqA/Afl--