Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757669AbcCaRr5 (ORCPT ); Thu, 31 Mar 2016 13:47:57 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:32824 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757387AbcCaRrz (ORCPT ); Thu, 31 Mar 2016 13:47:55 -0400 Date: Thu, 31 Mar 2016 10:47:41 -0700 From: Mark Brown To: Laxman Dewangan Cc: Bjorn Andersson , Bjorn Andersson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Liam Girdwood , Bjorn Andersson , Stephen Warren , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Gandhar Dighe , Stuart Yates Message-ID: <20160331174741.GO2350@sirena.org.uk> References: <56D65F7E.3090907@nvidia.com> <20160302043506.GC18327@sirena.org.uk> <56E81103.8010903@nvidia.com> <56ED0F58.7060005@nvidia.com> <56FBD4A3.7080208@nvidia.com> <20160330181623.GQ2350@sirena.org.uk> <56FCCC60.3080303@nvidia.com> <20160331165145.GF2350@sirena.org.uk> <56FD5A9F.5050001@nvidia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MCBkylF/aX/f/TlX" Content-Disposition: inline In-Reply-To: <56FD5A9F.5050001@nvidia.com> X-Cookie: If anything can go wrong, it will. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 64.55.107.4 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: 1503 Lines: 40 --MCBkylF/aX/f/TlX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 31, 2016 at 10:43:03PM +0530, Laxman Dewangan wrote: > We need two properties, one what we measured in platform and second one f= or > what we want to program PMIC. This is for the case where vendor advertised > ramp delay is not same as measured due to platform design. What makes you say that we need two properties? =20 > Based on discussion, regulator-ramp-delay is for measured ramp delay in > platform. So we will need another property for configuring PMIC. So as well as delaying in the kernel to cover the ramp time you want to configure something in the PMIC? What are you trying to configure in the PMIC? How will the PMIC driver meaningfully interpret a generic property given that the whole point here is that the PMIC is unable to deliver in spec behaviour? --MCBkylF/aX/f/TlX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW/WK7AAoJECTWi3JdVIfQVsQH/3oftUkvejVMiQz13a1mjFYB 5ehDacey9SE2SIEWNFVs9UNy2yUhz3vuS8z3KpRZcrXcCPbWl+3WWyMge3a8XJKN my72cZyn4qvXbzCcO1VKV79TV5HPX6g7bKVgWn9x0QAY8NEZUJ6/DIrhL5nd37lE WOu/fmqar76RA9hnspsIyZ2UpUBGKO8mReZlzUQ598s4AlB6TuLTwE+yICNFJP8x 8w0aVUdDes5zpVjjKNYYrHbZRQdlzBRLB5DSJT8xO9v2I1bFDRIwd3/YcXYbt7Ha oARAws0VMjfpHbF5ibk2BMMw0r4oIX1OYO0PAYjsluvUu4IP7uTTAAUIhrR7Fsk= =5uvR -----END PGP SIGNATURE----- --MCBkylF/aX/f/TlX--